VirtueMart Forum

VirtueMart 2 + 3 + 4 => Installation, Migration & Upgrade => Topic started by: nik.benz on April 01, 2017, 23:57:29 PM

Title: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: nik.benz on April 01, 2017, 23:57:29 PM
Hi,

After upgrading my shop to 3.0.4 my cart was not displayed, just a blank page with no error message. I then upgraded to 3.0.19 -> same result. Today upgraded to 3.2.1 -> same result, empty page/ no card displayed.
you can try/ see here --> https://www.dominikbenz.fr/le-shop/nos-vins.html

joomla 2.5.19

thanks for your help..
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: jenkinhill on April 02, 2017, 00:17:02 AM
Quote from: nik.benz on April 01, 2017, 23:57:29 PM
joomla 2.5.19

Is seriously old and very insecure. A patch has been provided but you need first to update to J2.5.28  http://virtuemart.net/news/latest-news/478-joomla-security-release-3-6-5-and-patch-for-joomla-2-5-28

Your cart page is completely blank which indicates a 500 error - check the server error logs.  See http://forum.virtuemart.net/index.php?topic=117042.0
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: nik.benz on April 07, 2017, 00:44:27 AM
hi, many thanks for your answer. so i updated to joomla 2.5.28 - no issues. I then applied the fix you mentioned, but the cart still stayed blank to 100%.
Now I'm getting this error when trying to login to back end:

Fatal error: Class 'vmLanguage' not found in /data/web/e35695/html/apps/joomla/administrator/modules/mod_vmmenu/helper.php on line 51

and I can't login to joomla no more.
also the front-end is getting hunderds of "Exception in loadConfig for unserialize ..." messages, while below the content get's displayed.

what happened? how can I gain access to my site?
thank for help..
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: jenkinhill on April 07, 2017, 12:16:39 PM
Looks like you have an old version of the admin VM menu module. Did you install the correct aio component (3.2.1) for your VM version? The current version does include the vmLanguage class.

Displaying exceptions suggests that your error reporting may be set too high.
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: nik.benz on April 08, 2017, 01:03:38 AM
Hi,

Thanks for your answer, unfortunly I can't login to the backend any more, therefore I cant' install or check vm aio components. Any idea how I can login to administration panel again?
Error as mentioned is still:

Fatal error: Class 'vmLanguage' not found in /data/web/e35695/html/apps/joomla/administrator/modules/mod_vmmenu/helper.php on line 51

regards,
Dominik
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: Jörgen on April 08, 2017, 10:42:41 AM
Install a backup would be the obviuos choice or reinstall Joomla

You can try to rename the directories that contains files with trouble. I would start renaming:
apps/joomla/administrator/modules/mod_vmmenu
to
apps/joomla/administrator/modules/mod_vmmenu-old

See if that unlocks it ?

regards

Jörgen @ Kreativ Fotografi
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: nik.benz on April 08, 2017, 22:46:33 PM
thanks!! I can now login again..

So I did re-install joomla 2.5.28 (no errors shown), afterwards I re-installed virtuemart 3.2.1 (file name: com_virtuemart.3.2.1) and got this error:

"Fatal error: Access to undeclared static property: VmConfig::$jDefLang in /data/web/e35695/html/apps/joomla/administrator/components/com_virtuemart/helpers/tableupdater.php on line 70"

on line 70 there is this (last line below):
   /**
    *
    *
    * @author Max Milbers
    * @param unknown_type $config
    */
   public function createLanguageTables($langs=0){

      if(empty($langs)){
         $langs = VmConfig::get('active_languages',array(VmConfig::$jDefLang));

So i assume some problem with language? Any ideas?

thanks
Title: Re: cart not displayed after upgrading to 3.0.19/ 3.2.1 later on
Post by: Milbo on April 11, 2017, 12:48:41 PM
Just install it again. This error is reasoned in your reinstall.