Page 1 of 1

3.2.1 error

Posted: Fri Jan 03, 2014 3:23 pm
by prophotodx
Fatal error: call_user_func_array(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "PlgSystemDebug" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /libraries/joomla/database/driver/mysqli.php on line 207

I am getting this error on an install of j 3.2.1. Thoughts?

PHP Built On Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64
Database Version 5.6.12-log
Database Collation utf8_general_ci
PHP Version 5.3.3
Web Server Apache/2.2.15 (CentOS)
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.2.1 Stable [ Ember ] 18-December-2013 14:30 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Firefox/26.0

Re: 3.2.1 error

Posted: Sat Jan 04, 2014 8:40 am
by sepurane
I have the same problem.
I'm installing Joomla 3.2.1 Stable version on Hostgator shared host but I always fail in the second step installation. Register_global => No (Red sign)
When I turn OFF register_global in the php.ini, it's always redirect to the first step installation. Frustrating.
Finally, I use QuickInstall and It's Okay right now. This is not the right solution but I don't have much times to find problem

Re: 3.2.1 error

Posted: Mon Jan 06, 2014 2:27 pm
by prophotodx
BUMP!

Re: 3.2.1 error

Posted: Mon Jan 06, 2014 8:38 pm
by bradm
Hi prophotodx and sepurane,

To confirm, you're getting this error during the installation of Joomla 3.2.1?

I tested the install on an InMotion Hosting server, and I successfully installed Joomla 3.2.1 from scratch.

I attached a screenshot of my configuration / settings before the actual installation (not sure if this will actually help though).

To help troubleshoot, what step of the installation process does this error occur?

Re: 3.2.1 error

Posted: Mon Jan 06, 2014 9:54 pm
by prophotodx
No I see it after upgrading to 3.2.1 from 3.2.

Re: 3.2.1 error

Posted: Tue Jan 07, 2014 3:25 pm
by prophotodx
Sorry to keep bumping this but I need to get this site completed for my client.

Re: 3.2.1 error

Posted: Tue Jan 07, 2014 8:39 pm
by bradm
Hi @prophotodx,

Do you think this is something we can try to replicate? I'm wondering if it is a problem with the Joomla core, or if you're running a 3rd party plugin / module that is causing the conflict.

To confirm, you upgraded from 3.2.0 to 3.2.1 and the problem started to happen? Does the error show on certain pages, or all of them? How we can replicate it?

On a side note, just a shot in the dark, I googled the error message you posted and many of the threads I read were talking about session variables. Personally, I'd try to delete the contents of the _session table to see if it helps. It could be that you have sessions from Joomla 3.2.0 in the database, and those sessions have / don't have settings that are conflicting with data Joomla 3.2.1 is expecting.

Also, if you're using cache, clearing the cache may help too.

Re: 3.2.1 error

Posted: Wed Jan 08, 2014 3:52 pm
by prophotodx
This is a development site so I don't want to lose anything I have already done. I have tried disabling components and plugins that I have installed and still see the error. I just noticed this error this morning on one of my installed components pages, I have a feeling both errors are related.

Warning: mysqli_close(): Couldn't fetch mysqli in /libraries/joomla/database/driver/mysqli.php on line 210

Re: 3.2.1 error

Posted: Wed Jan 08, 2014 5:24 pm
by hoanta
Chrome browser "inspect element" show the error and warnings on my site:

Code: Select all

Uncaught ReferenceError: jQuery is not defined 

Code: Select all

event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 

Re: 3.2.1 error

Posted: Thu Mar 27, 2014 6:52 pm
by prophotodx

Re: 3.2.1 error

Posted: Thu Mar 27, 2014 6:52 pm
by prophotodx
BTW site has been upgraded to 3.2.3 and I still have this error.