Upgrade to 3.2 Fatal error in backend

Need help upgrading your Joomla! website or converting to Joomla! 3.x? Please consider the availability of third-party templates and extensions when deciding which Joomla version to use.

Moderator: General Support Moderators

Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting, this means YOU.
Forum Post Assistant - If you are serious about wanting help, you will use this tool to help you post.
ginageick
Joomla! Intern
Joomla! Intern
Posts: 81
Joined: Thu Apr 06, 2006 8:01 pm

Upgrade to 3.2 Fatal error in backend

Postby ginageick » Thu Nov 07, 2013 2:29 pm

Hi there,
Upgraded to 3.2 this morning... all is well in front end, but after login screen to administrator, I see the following error:

Fatal error: Call to a member function getInt() on a non-object in /home/gawdca/public_html/2014/administrator/components/com_postinstall/models/messages.php

This is after saving global config with 'Send Mail' turned on.

Help please? Anyone else encounter this? Thank you!

ginageick
Joomla! Intern
Joomla! Intern
Posts: 81
Joined: Thu Apr 06, 2006 8:01 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby ginageick » Thu Nov 07, 2013 3:07 pm

Although this isn't a 'fix'.. part of the solution suggested in http://forum.joomla.org/viewtopic.php?f=710&t=825340 worked for me.. at least gaining access to the admin.

I don't see the extension mentioned in above post, but just using the suggested URL got me in.

ginageick
Joomla! Intern
Joomla! Intern
Posts: 81
Joined: Thu Apr 06, 2006 8:01 pm

*UPDATE* Upgrade to 3.2 Fatal error in backend

Postby ginageick » Thu Nov 07, 2013 4:59 pm

Tracked down the error:

[1146] Table 'xxx_yyy.xxx_postinstall_cpanels' doesn't exist SQL=SHOW FULL COLUMNS FROM `xxx_postinstall_cpanels`

Any idea of what the table should look like?

User avatar
mbabker
Joomla! Ace
Joomla! Ace
Posts: 1587
Joined: Sun Feb 28, 2010 8:26 pm
Location: White Bear Lake, MN, USA
Contact:

Re: Upgrade to 3.2 Fatal error in backend

Postby mbabker » Thu Nov 07, 2013 6:18 pm

It should be a postinstall_messages table as defined here - https://github.com/joomla/joomla-cms/bl ... .sql#L1495

I have no idea why yet that some folks are getting an error about a postinstall_cpanels table.
Past: Release Lead, CMS Maintainer
Present: Framework Maintainer, Security Team Member, .org System Administrator, Bug Squad Member

Manually updating Joomla? See https://gist.github.com/mbabker/d7bfb4e1e2fbc6b7815a733607f89281

ginageick
Joomla! Intern
Joomla! Intern
Posts: 81
Joined: Thu Apr 06, 2006 8:01 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby ginageick » Thu Nov 07, 2013 7:06 pm

Hmmm.. thanks for that.. but no go.

I do now have the postinstall_messages table as shown in link (there was one record missing) but still cannot get to Control Panel.

"Fatal error: Call to a member function getInt() on a non-object in /home/gawdca/public_html/2014/administrator/components/com_postinstall/models/messages.php on line 37"

marcocassisa
Joomla! Fledgling
Joomla! Fledgling
Posts: 4
Joined: Thu Nov 07, 2013 7:27 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby marcocassisa » Thu Nov 07, 2013 7:44 pm

Hi

same issue here.
Upgrade from 3.1.5 to 3.2 using the administration side of website.

First, a blank page appeared.
The error was @line 37 of messages.php (administrator/components/com_postinstall/models/messages.php)
I managed to go forward by changing lines 37ff.

Code: Select all

                // Add a forced extension filtering to the list
                $inp = new JInput;
                $eid = $inp->getInt('eid', 700);
//              $eid = $this->input->getInt('eid', 700); //apparently $this->input is undefined...
                $query->where($db->qn('extension_id') . ' = ' . $db->q($eid));

                // Force filter only enabled messages
//              $published = $this->input->getInt('published', 1);
                $published = $inp->getInt('published', 1);


After that the index.php of administration stopped to be blank and instead showed an error of a malformed query (

Code: Select all

SELECT * FROM `jos_postinstall_messages` WHERE `extension_id` = '700' AND `enabled` = '1' ORDER BY `` ASC
) <-order error

The error persisted even if I forced a

Code: Select all

$query->order($db->getQuotes('id'). ' ASC')
the resulting query was

Code: Select all

SELECT * FROM `jos_postinstall_messages` WHERE `extension_id` = '700' AND `enabled` = '1' ORDER BY `` ASC, ASC


which is the message shown in Control Panel

Now when I administer the component postinstall_messages I get a sql error

Code: Select all

SHOW FULL COLUMNS FROM `jos_postinstall_cpanels`

because the table doesn't exist.


====SOME TRUE FACTS====
Current config. GNU/Linux Ubuntu server 64bit
Apache2
Architecture: amd64
Version: 2.2.22-1ubuntu1

mysql
Architecture: all
Source: mysql-5.5
Version: 5.5.22-0ubuntu1

php
Architecture: all
Version: 5.3.10-1ubuntu3.8

The server is running in a Parallel panels environments

gm777
Joomla! Apprentice
Joomla! Apprentice
Posts: 5
Joined: Wed Nov 06, 2013 8:47 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby gm777 » Thu Nov 07, 2013 10:29 pm

Same error after automatic update from 3.1.5 -> 3.2

Front-end works fine.

Back-end shows error on white page instead of Control Panel:

Code: Select all

/administrator/components/com_postinstall/models/messages.php on line 37

The rest of Administrator accessible only via modified url (thanks @pedregon), such as:
http://[your_domain]/administrator/index.php?option=com_config

Extensions > Extension Manager > Database :
Database table structure is up to date.

Database schema version (in #__schemas): 3.2.0.
Update version (in #__extensions): 3.2.0.
Database driver: mysqli.
79 database changes were checked successfully.
130 database changes did not alter table structure and were skipped.


Apache 2.2.25
PHP 5.3.27
MySQL 5.5.32-cll

hat7rick
Joomla! Apprentice
Joomla! Apprentice
Posts: 5
Joined: Thu Nov 07, 2013 4:40 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby hat7rick » Thu Nov 07, 2013 10:43 pm

same issue, more people:

viewtopic.php?f=707&p=3103405#p3103405

rlerner42
Joomla! Fledgling
Joomla! Fledgling
Posts: 3
Joined: Wed Oct 19, 2011 6:28 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby rlerner42 » Fri Nov 08, 2013 10:59 pm

Add me to the list. Exact same problem as described above after upgrade from 3.1 to 3.2 on Nov 8, 2013. Error page reads:

0 - An error has occurred.

SQL=SELECT `jos31_postinstall_messages`.* FROM `jos31_postinstall_messages` WHERE `extension_id` = '700' AND `enabled` = '1' ORDER BY `postinstall_message_id` ASC

Front-end works fine, can log into back end bypassing index page as suggested above. Anyone have a fix?

rlerner42
Joomla! Fledgling
Joomla! Fledgling
Posts: 3
Joined: Wed Oct 19, 2011 6:28 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby rlerner42 » Sat Nov 09, 2013 2:55 am

Getting closer now. Was able to get DB repaired using ../administrator/index.php?option=com_installer&view=database and clicking on fix button (top-left).

Now, everything seems to work except:
Joomla Update still shows unknown version.
When I click on Joomla Update I get: 0 - An error has occurred. <url> malformed

Tried the suggestion of deleting and re-FTPing /libraries/fof, no joy.

Will probably leave things alone at this point and wait for 3.3, will skip 3.2 for our other sites.

marcocassisa
Joomla! Fledgling
Joomla! Fledgling
Posts: 4
Joined: Thu Nov 07, 2013 7:27 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby marcocassisa » Sat Nov 09, 2013 6:29 pm

rlerner42 wrote:Getting closer now. Was able to get DB repaired using ../administrator/index.php?option=com_installer&view=database and clicking on fix button (top-left).
.



To me Database fix didn't work.
A time machine (i.e. a reset to a previous snapshot) saved us.
When will the upgrade scripts upgraded themselves?

gm777
Joomla! Apprentice
Joomla! Apprentice
Posts: 5
Joined: Wed Nov 06, 2013 8:47 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby gm777 » Sat Nov 09, 2013 11:35 pm

Here's the fix. I hope it works for you as well.

    * Rename your /libraries folder, so you can go back to the original, if need be.
    * Replace /libraries with /libraries from the Joomla_3.2.0-Stable-Update_Package

Now you will be able to log in to Administrator AND the "Components > Post-installation messages" error will be gone.

rlerner42
Joomla! Fledgling
Joomla! Fledgling
Posts: 3
Joined: Wed Oct 19, 2011 6:28 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby rlerner42 » Sun Nov 10, 2013 1:01 am

Appreciate the efforts, but no joy. Renamed and reloaded libraries from 3.2 upgrade patch, symptoms remain as follows:

Control panel: "You have post-installation messages..." Click on Review Messages: 404 - An error has occurred. Component not found. The target url was http://www.domain.com/administrator/ind ... ll&eid=700

Joomla Update button reads "Unknown Joomla". Components-> Joomla Update yields: 0 - An error has occurred. <url> malformed. Both menu and cpanel icon point to (absolute) url http://www.domain.com/administrator/ind ... omlaupdate .

Each of the target directories has an index.html which would capture the browser if the helpers missed the request. So I'm thinking the option request went to the intended sub-folder, then the black hole?

Footer indicates 3.2.0 is current version. Front-end appears to be working properly. Using a Rocket Theme template with Gantry 4.

System Info:

PHP Built On Linux domain.com 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:37 EDT 2012 i686
Database Version 5.0.96-community
Database Collation utf8_general_ci
PHP Version 5.4.21
Web Server Apache
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 3.2.0 Stable [ Ember ] 6-November-2013 14:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

Configuration File (excerpts)
editor jce
captcha 0
dbtype mysql
gzip 0
error_reporting default
ftp_enable 0
caching 0
cache_handler file
sef 1
sef_rewrite 0
session_handler database
cookie_domain
cookie_path

PHP Info (5.4.1) too lengthy for this post, but if someone has a thought on it, I'll follow up.

User avatar
Webdongle
Joomla! Master
Joomla! Master
Posts: 31261
Joined: Sat Apr 05, 2008 9:58 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby Webdongle » Sun Nov 10, 2013 2:19 am

Can confirm there is a definite issue

Is there a tracker for this ?

Addendum
controller.php line 38 sows as

Code: Select all

   $this->input->set('view', 'login');


Addendum 2
Login front end produces
error update 02.PNG
You do not have the required permissions to view the files attached to this post.

gm777
Joomla! Apprentice
Joomla! Apprentice
Posts: 5
Joined: Wed Nov 06, 2013 8:47 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby gm777 » Sun Nov 10, 2013 3:06 am

It seems that this 3.2 update breaks websites in many different ways. There are many flavors of errors being reported by users. The one described at the top of this thread seems to be fixed, at least in my case, by updating the /libraries folder.

rlerner42, your error seems to be a little different from the one described by ginageick.

Perhaps it would be best to post each set of errors in their own threads, and also rename the existing threads to be more specific than "Errors upgrading to 3.2".

sovainfo
Joomla! Exemplar
Joomla! Exemplar
Posts: 8258
Joined: Sat Oct 01, 2011 7:06 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby sovainfo » Sun Nov 10, 2013 8:49 am

@marcocassisa

use:

Code: Select all

$query->order($db->qn('postinstall_message_id'). ' ASC')


Did you figure out where the name postinstall_cpanels came from?
Issue with migrating? Include logs/joomla_update.php in your report!
Blank screen? Verify pagesource for HTML code (javascript error)
Installation failing on populating database? Install with set_time_limit(0)
Document your customizations!

marcocassisa
Joomla! Fledgling
Joomla! Fledgling
Posts: 4
Joined: Thu Nov 07, 2013 7:27 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby marcocassisa » Sun Nov 10, 2013 9:11 am

Thanks sovainfo

sovainfo wrote:@marcocassisa

use:

Code: Select all

$query->order($db->qn('postinstall_message_id'). ' ASC')


Did you figure out where the name postinstall_cpanels came from?


Thanks, but I can't follow your suggestion right now (and can't understand where on the earth did that table name come from), because we restored the last backup, so we are at 3.1.5 now, waiting for better joomla update scripts.
In the next days I'll try again on a non-production site, and will let you all know how it is going on
Thanks

User avatar
Webdongle
Joomla! Master
Joomla! Master
Posts: 31261
Joined: Sat Apr 05, 2008 9:58 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby Webdongle » Sun Nov 10, 2013 12:38 pm

I just tried the update/upgrade again ... this time full success

The only reason that I can see for it not working the first time is that I was doing other things on my laptop while it was updating. If that was the reason then some sort of time out could be causing the various errors. That would compound other conflicts such as 3rd party logins not being compatible with 3.2.0

User avatar
Burnardo
Joomla! Apprentice
Joomla! Apprentice
Posts: 13
Joined: Sat Jan 21, 2006 11:48 am
Location: Apeldoorn

Re: Upgrade to 3.2 Fatal error in backend

Postby Burnardo » Sun Nov 10, 2013 3:40 pm

After updating from 3.1.5 to 3.2.0 ended up with the same problem as mentioned above in this thread.

My solution finally was:
In the database manually add a new table: jl_postinstall_messages (possibly change first few letters as is necessary)

Then add 3 items in that table:
1. postinstall_message_id
2. extension_id
3. enabled

After having done this my admin worked properly again. And no error messages appeared.
I do not know why the update did not add these items in the database (or was stopped to perform this task) but this solution worked for me.

Burnardo, hope it helps others...

marcocassisa
Joomla! Fledgling
Joomla! Fledgling
Posts: 4
Joined: Thu Nov 07, 2013 7:27 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby marcocassisa » Sun Nov 10, 2013 5:02 pm

Burnardo wrote:My solution finally was:
In the database manually add a new table: jl_postinstall_messages.


Just to give additional infos to developers, in my case the #__postinstall_messages table was there indeed, and it was populated

Eb992
Joomla! Fledgling
Joomla! Fledgling
Posts: 1
Joined: Mon Nov 11, 2013 1:08 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby Eb992 » Mon Nov 11, 2013 1:10 pm

I've fixed with going in administrator/index.php?option=com_installer&view=database and pressing Fix (on the left) . Worked fine .

JUX Extensions
Joomla! Apprentice
Joomla! Apprentice
Posts: 6
Joined: Wed Oct 10, 2012 1:39 am

Re: Upgrade to 3.2 Fatal error in backend

Postby JUX Extensions » Tue Nov 12, 2013 8:26 am

this is a bypass solution

Code: Select all

public function buildQuery($overrideLimits = false)
   {
      $query = parent::buildQuery(true);

      $db = $this->getDbo();

      // Add a forced extension filtering to the list
      //$eid = $this->input->getInt('eid', 700);
      $eid = 700;
      $query->where($db->qn('extension_id') . ' = ' . $db->q($eid));

      // Force filter only enabled messages
      //$published = $this->input->getInt('published', 1);
      $published = 1;
      $query->where($db->qn('enabled') . ' = ' . $db->q($published));

      return $query;
   }

bigbroantonio
Joomla! Intern
Joomla! Intern
Posts: 93
Joined: Mon Mar 06, 2006 8:46 am

Re: Upgrade to 3.2 Fatal error in backend

Postby bigbroantonio » Thu Nov 14, 2013 1:29 pm

I may have a fix - it worked for me...

Go to Extension Manager > Database > Fix

Everything went back to normal... or so it seems :)

nealb
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Tue Nov 25, 2008 5:26 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby nealb » Thu Nov 14, 2013 5:59 pm

Here's my error:

Fatal error: Call to a member function getInt() on a non-object in /****/administrator/components/com_postinstall/models/messages.php on line 37

Line 37 is this:
$eid = $this->input->getInt('eid', 700);

The *_postinstall_messages table does exist in my database, and there are three entries in the extension_id column with the value of 700.

gerozing
Joomla! Apprentice
Joomla! Apprentice
Posts: 12
Joined: Thu Nov 30, 2006 9:06 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby gerozing » Sat Nov 16, 2013 5:19 pm

Same issue. Obtain following error message
Table 'xxx_postinstall_cpanels' doesn't exist SQL=SHOW FULL COLUMNS FROM `xxx_postinstall_cpanels`

This error message is obtained after checking 'component' 'post-installation-messages'

By jumping over the admin login I can get in the backend!!

Suggestions??

Gerard

User avatar
mbabker
Joomla! Ace
Joomla! Ace
Posts: 1587
Joined: Sun Feb 28, 2010 8:26 pm
Location: White Bear Lake, MN, USA
Contact:

Re: Upgrade to 3.2 Fatal error in backend

Postby mbabker » Sat Nov 16, 2013 5:23 pm

This error exists if you for some reason have an outdated version of FOF installed on your site. If you're using any Akeeba extensions, you should be able to go to /administrator/index.php?option=com_installer and install the latest version, this should clear it up. Otherwise, you'll need to manually delete those legacy files.
Past: Release Lead, CMS Maintainer
Present: Framework Maintainer, Security Team Member, .org System Administrator, Bug Squad Member

Manually updating Joomla? See https://gist.github.com/mbabker/d7bfb4e1e2fbc6b7815a733607f89281

User avatar
nikosdion
Joomla! Explorer
Joomla! Explorer
Posts: 368
Joined: Sun Mar 12, 2006 9:01 pm

Re: Upgrade to 3.2 Fatal error in backend

Postby nikosdion » Sat Nov 16, 2013 5:46 pm

OK, folks, please let me give you exact instructions.

A. If you are going to upgrade to Joomla! 3.2

Update your extensions before updating your site. FOF was distributed with Akeeba extensions, but also with several third party extensions (e.g. Cookie Confirm). The reported problem will occur if you have a severely outdated version of a FOF-powered extension. When I say "severely" I mean well over an entire year (12 months). You should certainly install updates much more often than that! Developers don't publish updates for fun, we do that to fix and prevent issues. You are supposed to install them.

B. If you have already upgraded to Joomla! 3.2

Despite what @mbabker said, installing an Akeeba component on your Joomla! 3.2.0 site will NOT help. No FOF-powered component will replace the version of FOF installed with Joomla! 3.2 in order to prevent us accidentally screwing up your sites. Tough luck. You'll have to do it the manual way.

Using your FTP client go into your site's libraries/fof directory. Ignore the subdirectories. Look at the files. You have several files whose names end in .php. Delete all of them EXCEPT the file named include.php. If you remove that file you'll brick your site. If that happens you will need to replace that file with the one found in the Joomla! installation ZIP file.

Lesson learned:

Always install updates provided by extension developers and Joomla! itself as soon as possible (if you're wondering, the best time to install an update is always yesterday). Never leave your site's extensions not updated for an entire year! Updates are crucial to the correct operation of your site.
Nicholas K. Dionysopoulos
Director, Akeeba Ltd

User avatar
leolam
Joomla! Master
Joomla! Master
Posts: 16457
Joined: Mon Aug 29, 2005 10:17 am
Location: Netherlands/ UK/ S'pore/Jakarta/ North America
Contact:

Re: Upgrade to 3.2 Fatal error in backend

Postby leolam » Sat Nov 16, 2013 5:54 pm

nikosdion wrote:OK, folks, please let me give you exact instructions.
Welcome back from USA. Seems your head is clear again ;-) This will for sure help a lot of people on these forums and I have already pointed several to your post here.... Nice one Nicholas saves a lot of re-posting time and time again!

Leo 8)
-- Joomla Professional Support Services : https://gws-desk.com --
-- Joomla Specialized Hosting Solutions: https://gws-host.com --
-- Joomla Professional Web Development & Design :www.gws-studio.com
-- Member Joomla Bug Squad --

User avatar
Bakual
Joomla! Guru
Joomla! Guru
Posts: 582
Joined: Sun Dec 13, 2009 9:00 pm
Location: Switzerland
Contact:

Re: Upgrade to 3.2 Fatal error in backend

Postby Bakual » Sat Nov 16, 2013 8:49 pm

Try installing the latest AdminTools Core. For me that cleaned up the old FoF files despite what Nicholas says. If it doesn't work, you still can delete the files manually ;)

trusting
Joomla! Enthusiast
Joomla! Enthusiast
Posts: 128
Joined: Tue Feb 10, 2009 4:49 am

Re: Upgrade to 3.2 Fatal error in backend

Postby trusting » Tue Nov 19, 2013 6:18 am

Burnardo wrote:After updating from 3.1.5 to 3.2.0 ended up with the same problem as mentioned above in this thread.

My solution finally was:
In the database manually add a new table: jl_postinstall_messages (possibly change first few letters as is necessary)

Then add 3 items in that table:
1. postinstall_message_id
2. extension_id
3. enabled

After having done this my admin worked properly again. And no error messages appeared.
I do not know why the update did not add these items in the database (or was stopped to perform this task) but this solution worked for me.

Burnardo, hope it helps others...


Burnardo, it did help me - the only thing that restored access to the admin. THANKS! :)

From this point, the admin area was accessible, but not displaying correctly. So I used Extension Manager to install the full 3.2.0 package. That restored MOST of the admin area and front end.

However, there are some database errors and going to Database and clicking "Fix" doesn't fix them. This is the message:

7 Database Problems Found

Database schema version (2.5.16) does not match CMS version (3.2.0).
Table 'u60xx_content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
Table 'u60xx_content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.4-2011-11-23.sql.)
Table 'u60xx_ucm_history' does not exist. (From file 3.2.0.sql.)
Table 'u60xx_users' does not have column 'otpKey'. (From file 3.2.0.sql.)
Table 'u60xx_users' does not have column 'otep'. (From file 3.2.0.sql.)
Table 'u60xx_user_keys' does not exist. (From file 3.2.0.sql.)



I'm also getting an error message for NoNumber Extension Manager (which I disabled earlier, then reinstalled after regaining access to the admin area):
500 JHtmlBehavior::mootools not found.


Progress, but not there yet.


Return to “Migrating and Upgrading to Joomla! 3.x”

Who is online

Users browsing this forum: No registered users and 7 guests