I regret doing a live VirtueMart (VM) upgrade from 2.0.10 to 2.0.24a, because now VM is not working at site.
The site uses Joomla! (J!) 1.5.23 Stable. In hindsight, I wonder if VM 2.0.24a is not compatible with J! 1.5.23 and that is why it might have crashed.
Fatal error: Call to a member function get() on a non-object in /home/public_html/components/com_virtuemart/views/virtuemart/view.html.php on line 141
After clicking upgrade link withing Joomla admin panel, upgrade began to download and abruptly stopped. After that, VirtueMart2 stopped working at site.
What can be done to restore VM 2.0.10 at site? I wonder if VM 2.0.10 is reinstalled, will it delete all products from database?
Any clues appreciate. Thank you.
If you are using VirtueMart 2 on J1.5 then It is advised now to upgrade to Joomla to 2.5, as the VM2 code now (from VM2.0.14) uses Joomla 2.5 specific code and so may not run properly on J1.5
from http://forum.virtuemart.net/index.php?topic=106865.0
guess you can only try a reinstall of 2.0.12 http://dev.virtuemart.net/projects/virtuemart/files (http://dev.virtuemart.net/projects/virtuemart/files) - but all before v2.0.22 are insecure
no back up?
Hello GJC Web Design,
Thank you for sharing your experience with me.
If VM 2.0.10 uninstalled from within J! and then re-installed, will products be automatically deleted during re-install?
Because old VM extensions are still on this PC:
- com_virtuemart.2.0.8c
- com_virtuemart.2.0.8c_ext_aio
- com_virtuemart.2.0.8c_extract_first
After system is "restored" to its previous state, an major overhaul from J! 1.5 to J! 2.5 and VM to 2.0.24a can be done.
Site needs to be up and running ASAP even if temporarily unsecure.
Any clues appreciated.
Do not uninstall - that will probably remove your products etc.
I'd make a working backup of the site and then try to revert the backup copy to an earlier version. That way if it screws the data you have not lost everything. I think there is still a version of Akeeba Backup suitable for use on J1.5 if you don't already use it.
My concern is that the database structure has been modified by the update changes which may or may not affect function with an older version.
Two possible ways to revert. One is to use Joomla's extensions installer to install the main VM component from your chosen version (2.0.10?) followed by the aio component from the same version.
The other possibility is to unpack both components locally and use ftp to overwrite the files on the server.
Not having needed to do something like this I have no idea about possible pitfalls.
You can get the file packages from http://dev.virtuemart.net/projects/virtuemart/files
Not only is your old VM insecure, but if you are using J1.5.23 then that has known security issues, too. The only (thought to be) secure version of the J1.5 series is J1.5.26 with an added security patch. There is a link to that in http://forum.virtuemart.net/index.php?topic=118683.0
The site was restored to a working state with akeeba kickstart.
Joomla version: 1.5.23
Virtuemart version. 2.0.8
PHP Version: 5.2.17
Web Server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Web Server to PHP interface: cgi
Joomla! Version: Joomla! 1.5.23 Stable [ senu takaa ama baji ] 04-March-2011 18:00 GMT
Next step is to upgrade both Joomla and Virtuemart software.
But that is another post.
Thank you guys for your help!! I really appreciate it.
I would use the latest version and try to find the fix for the ACL, which is imho the only thing not working with j1.5. We can add it to 2.0.26D and release an F version, again compatible to j1.5.
The reason is that we are going to remove alll the compatibility stuff for vm2.1