News:

You may pay someone to create your store, or you visit our seminar and become a professional yourself with the silver certification

Main Menu

Cart trouble after update from VM 2.6.7 to 2.9.9.4 and Joomla 2.5.7 to 3.3.6

Started by olarf, November 13, 2014, 19:46:10 PM

Previous topic - Next topic

Milbo

Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/

olarf

What do you mean with non translated option??? I can login to the backend with english or german and then I get everything in english or german. Where can I switch additional to a non translated version of vm. I'm a bit surprised that a thing like TOS which is a main part of a basic shop is making that trouble. However, I'm realy happy for all your tips and ideas and I hope there will be a solution very soon- Can the overrides I use be a problem while they have nothing to do with TOS. I need nothing more then a hook to accept TOS before buying and a way for the customer to read TOS there also if he want to do that.

Milbo

write tos, not TOS.

Just to understand what happened. Which version did you used before? maybe vm2.9.x? That would explain that it got not created. You can also change the function isUpdateToVm3 to return true in script.virtuemart.php (BE/install) folder. then just use the tool "update tables" and the tos should be created.
Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/

olarf

yes I had vm 2.9.x before. So I will try to follow your hint.
Found it and set isUpdateToVm3 to true (admin/components/com_virtuemart/install). Then I set it in line 315 from falst to true and enable the Database tools and update the databse.
Then I got the tos field and the field "agree" was disabled :) Many thanks!!!

Just two last questions on this topic.
Should I set it back to false in the script now or doesnt it matter?
Should I delete the Shopper field "agree" now as it is disabled and function free or should I keep it?

Milbo

Quote from: olarf on December 12, 2014, 23:03:50 PM
Should I set it back to false in the script now or doesnt it matter?
Actually, when you do the next update, that part should be overwritten and so it should not matter, but of course it is more secure to set back the original code.

Quote from: olarf on December 12, 2014, 23:03:50 PM
Should I delete the Shopper field "agree" now as it is disabled and function free or should I keep it?

This is up to you. You can use the "agreed" for registration and the "tos" for shopping. So it is more a legal than technical question.


Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/