storebox 3.9.1 - VM 2.0.22a -> 2.0.22b issue

Hi - I assume you guys are aware that the update from VM 2.0.22a -> VM 2.0.22b already breaks the latest storebox template. Supposingly the update has no real template changes, is refered to as a "security update".

Right now, it looks like a css/template override issue.

The product details layout is ... ? switched ? - aside, which was postioned left, is now on the right side.
It´s falling back to style1 ... even so style3 is choosen in template configuration.
Price is displaying "ask for price" ... when I switch to beez template, price is displayed.

will there be fix for that ? I already modified quiet a lot, a new install would be ... well, hell of a lot of work, but I assume 2.0.22b as a security fix should be mandatory.

thanks

Hi

This was not only a security fix I know becuase I've reported quite a lot of issues with VM and some were resolved within this update. Please downgrade the VM version and when template update will be ready, You will just replace the files which will be mentioned in update informations.

without asking to much ... you have any idea when we can expect an update ? days, weeks, month ? just so I have an idea and can plan accordingly - thanks d.

Hi

Sorry, no idea. I'll ask programmers and will let You know.

Hi

Ok. I've learned something interesting, please read what programmers answered:

Code: Select all



Ok I've downloaded bikestore quickstart. Install it and then Update VM to latest 2.0.22c version and in fact in VM admin settings there is set our template for VirtueMart default one. Looks like they change the way how template is displayed and the solution is set this option to default Joomla! one. The VM is working fine and even VM changelogs all is described as not feature changes but bug fixes (not in layouts). When the settings are set to use default J! template all is working fine and our override views looks properly.

According to VM updates, the core version is 2.0.22 and we usually update VM to main version not to a,b,c,d,e,f like they want to name their component. If you look at VirtueMart update you will see interesting message http://d.pr/i/v6eA that it is not recommended to use different version 2.0.22a for multilanguage websites (this version is latest supported by our templates). So what we should do right now ? Release two different versions of every store template for multilanguage and single language websites ? It is really pointless...

What is more VM Update will NOT change the VirtueMart settings so the only solution right now is to advise users to apply this change in VM configuration - we don't have any way to change this during template upgrade process.


Ok ... can confirm - I actually just did the 2.0.22c update. After that the layout was screwed, changed the settings inside Virtuemart Configuration to use "Joomla Default" and it was back to normal.

Thanks

Hi

Ok. I've learned something interesting, please read what programmers answered:

Code: Select all



Ok I've downloaded bikestore quickstart. Install it and then Update VM to latest 2.0.22c version and in fact in VM admin settings there is set our template for VirtueMart default one. Looks like they change the way how template is displayed and the solution is set this option to default Joomla! one. The VM is working fine and even VM changelogs all is described as not feature changes but bug fixes (not in layouts). When the settings are set to use default J! template all is working fine and our override views looks properly.

According to VM updates, the core version is 2.0.22 and we usually update VM to main version not to a,b,c,d,e,f like they want to name their component. If you look at VirtueMart update you will see interesting message http://d.pr/i/v6eA that it is not recommended to use different version 2.0.22a for multilanguage websites (this version is latest supported by our templates). So what we should do right now ? Release two different versions of every store template for multilanguage and single language websites ? It is really pointless...

What is more VM Update will NOT change the VirtueMart settings so the only solution right now is to advise users to apply this change in VM configuration - we don't have any way to change this during template upgrade process.


Hi

Thank You for confirming. There is a lot of reports of the same problem right now. So I will know that this solution works.