Hi,
How update VM update 3.0.2 to 3.0.3 ??
http://forum.virtuemart.net/index.php?topic=123808
Thanks for your quick reply.
I use Joomla 3.3.6 and VM 3.0.2 (fr)
In VM control panel
I can't find the button to update?
I also tried in Joomla Update control panel.
just download the zip - unzip and install the two packages as you would any other extension
all your settings and content will be untouched
http://dev.virtuemart.net/attachments/download/891/com_virtuemart.3.0.3_extract_first.zip
After the upgrade 3.0.2 to 3.0.3 will not load the back-end of the site. And the title page the following error:
Fatal error: Uncaught exception 'RuntimeException' with message 'Subquery returns more than 1 row SQL=SELECT m.id, m.title, m.alias, m.link, m.parent_id, m.img, e.element FROM `test2_menu` as m LEFT JOIN test2_extensions AS e ON m.component_id = e.extension_id WHERE m.client_id = 1 AND e.enabled = 1 AND m.id > 1 AND e.element = 'com_virtuemart' AND (m.parent_id=1 OR m.parent_id = (SELECT m.id FROM `test2_menu` as m LEFT JOIN test2_extensions AS e ON m.component_id = e.extension_id WHERE m.parent_id=1 AND m.client_id = 1 AND e.enabled = 1 AND m.id > 1 AND e.element = 'com_virtuemart')) ORDER BY m.lft' in ###/libraries/joomla/database/driver/mysqli.php:606 Stack trace: #0 ###/libraries/joomla/database/driver.php(1281): JDatabaseDriverMysqli->execute() #1 ###/administrator/modules/mod_vmmenu/helper.php(46): JDatabaseDriver->loadObjectList() #2 in ###/libraries/joomla/database/driver/mysqli.php on line 606
Can you please tell how to fix it now, without having to reinstall?
the error relates to Joomla's database driver - have done loads of vm3 installs and never seen this
Try to install 3.0.3 again
So in fact the problem is that the train does not load has admin panel!
The menu is displayed only up menu Virtuemart and nothing can be done.
What to do in this case?
Ah .. I see it is related to the vm admin module
unpublish this in extensions->modules->
choose admin modules to find it
Not possible to do the same change - does not work at all, no menus. :-\
think outside the box
either rename /administrator/modules/mod_vmmenu/helper.php to something else or disable the module in the database extensions table
Thank You!
It turned out to recover only by restoring the table ### _ menu from the dump.
did you keep a copy of the corrupt one.. ? this sort of rings a bell ..
I had an upgrade to VM3 that had no VM admin mod links -- in the table were 3 sets - all wrongly attributed to comp number and/or parent id
would be interesting to see what went wrong with yours
Hello,
Quote from: GJC Web Design on January 15, 2015, 20:01:39 PM
just download the zip - unzip and install the two packages as you would any other extension
all your settings and content will be untouched
http://dev.virtuemart.net/attachments/download/891/com_virtuemart.3.0.3_extract_first.zip
Is there a more modern approach?
I created a new site, then installed VM. After installation I got this warning. (http://www.apweb.fr/images/instavm303.PNG)
More modern? ha .. the devs could add a gui, have some nice ajax effects, some draggy droppy stuff, lots of things to click, a popup or two... but why?
You want to put some zipped files on your server, expand them and run an installation script.. and that is exactly what you do...
the message is simply a warning and has been so explained at least 5-6 times in posts on here.. did u search?
Quote from: AS on January 16, 2015, 10:38:06 AM
Thank You!
It turned out to recover only by restoring the table ### _ menu from the dump.
I had exactly the same problem as AS.
Spent hours to restore my db.
Could you explain how you restored yours?
Did you copy from a back-up?
open your sql backup in a good txt editor (notepad++)
find the #__ menu block
copy / paste to a new txt file the CREATE & INSERT to do with #__menu
change all instances of #_ to your table prefix
on the live site rename the #__menu to #__menu_old
copy paste the content of the file you just made into the phpmyadmin Sql query box and run
should work
Great thanks!
It worked!
Now I only have to restore this table if this happend again!
shouldn't - have reported this to the devs so hopefully won't happen again
Quote from: GJC Web Design on January 20, 2015, 15:11:02 PM
shouldn't - have reported this to the devs so hopefully won't happen again
Sadly not. Happend to me on upgrading from 3.0.3 to 3.0.4