News:

Support the VirtueMart project and become a member

Main Menu

module virtuemart latest article show wrong prices

Started by 2cool, October 11, 2018, 18:54:14 PM

Previous topic - Next topic

2cool

Hi,
I added a new module 'virtuemart articles' displayed at menu 'new'
Showing latest 50 products. But I shows prices from b2b shoppergroup !
What could be the problem here, or is this module function not able to use for multiple groups/prices?

Running Joomla! 3.8.13 and VirtueMart 3.2.14

Thanks in advance,
Pas

Jörgen

A live URL would be nice ....

Jörgen @ Kreativ Fotografi
Joomla 3.9.18
Virtuemart 3.4.x
Olympiantheme Hera (customized)
This reflects current status when viewing old post.

Studio 42

Quote from: 2cool on October 11, 2018, 18:54:14 PM
Hi,
I added a new module 'virtuemart articles' displayed at menu 'new'
Showing latest 50 products. But I shows prices from b2b shoppergroup !
What could be the problem here, or is this module function not able to use for multiple groups/prices?

Running Joomla! 3.8.13 and VirtueMart 3.2.14

Thanks in advance,
Pas
Do you use a virtuemart core module or 3rd party module ?
'virtuemart articles' does not exist, but virtuemart products in core

2cool

H Jörgen, can't do because its disables now.

Got a reply this could be fixed by 'disabling cache' in adv options.

It's indeed virtuemart products core module.

Thanks,
Pas

Studio 42

Joomla cache is not working because currency or shopper group are unknown and the cache key is same for Joomla.
The dev team have to create  the right key, so the modules can be cached for all situations else cache set bad results

2cool

There's two cache settings in this module.
In advanced tab this cache option is already disabled.
But in the first tab there's  'virtuemart cache', this is set to yes.
Should all cache options set to 'no'  to fix this problem and show the right price to the right shoppergroup?

Regards,
Pas

Studio 42

If you have any problem then disable cache. As i explained, the cache Key need to have shoppergroup in the key. I think that it's not the case.
You should explain this in the bug reports section of the forum if you want that team implement it.