Hi
In category browse view mode with ajax for category view enabled please test in 3.0.19.2 selecting a child product from the dropdown of a parent and then selecting "choose a variant" seems to break the display.
The "choose a variant" issue happened in one of the first beta's but was solved but noticed it again since 3.0.19.xxx. (latest 2-3 betas)
In beez and protostar selecting childs adds them directly on the category browse view (product appears below the parent and childs gets added below as you switch between them) breaking the display.
Regards
EDIT: Been testing more:
com_virtuemart.3.0.18.9_extract_first_9427.zip is the last package where childs work fine for us without the display issues mentioned.
In 3.0.19.1 and 3.0.19.2 the behaviour changes when selecting childs these appear as added below the parent in the category browse page instead of reloaded in the place of the parent.
Regards
Thank you, a fix for the vmprices of related products broke it. Btw, variants could also work in related product containers now, but dont nail me on it.
http://dev.virtuemart.net/attachments/download/1051/com_virtuemart.3.0.19.3_extract_first.zip
Quote from: Milbo on January 29, 2017, 22:12:57 PM
Thank you, a fix for the vmprices of related products broke it. Btw, variants could also work in related product containers now, but dont nail me on it.
http://dev.virtuemart.net/attachments/download/1051/com_virtuemart.3.0.19.3_extract_first.zip
Thanks! that fixed it.
BTW update between betas works fine but updating from stable 3.0.18 to this latest 3.0.19.3 gives a fatal error:
Error message data:
1 Class 'vmLanguage' not found in file: websitepath/administrator/components/com_virtuemart/views/updatesmigration/tmpl/insfinished.php line: 25
The package gets correctly installed but for users comming from stable version could be confusing. Maybe it happens to me only cause I installed back the stable having installed newest beta's previously.
I think that was the reinstall, I just tested an update from vm3.0.16 and it worked. I also found the general error and the installer uses now the tmp files, not the already installed ones.