Page 3 of 4

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Fri Dec 20, 2013 12:21 am
by bonez
brizola wrote:There is a simple solution, though an adhoc one: just disable the remember me plugin, make the update and enable the plugin again.
This option worked for me. :D
Thanks for the info brizola

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Sat Dec 21, 2013 6:47 pm
by epozz
The remember.php workaround works for me (Update from 3.1 to 3.2)
The only little BUG: the ControlPanle looks messy right now.

The "Last-Articles" are very small and the "logged-In Users" floating wrong.
No 2 collums-View right now.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Sat Dec 21, 2013 9:44 pm
by Webdongle
'Ctrl' + ''Shift' + 'Del' ... clear cache. Make sure you don't select to clear the wrong things.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Fri Dec 27, 2013 8:11 pm
by sbohler
I followed Hazaa's original instructions near the top of this thread, encountered the SQL error some reported, applied the fix for that also found in this thread and was successful. I remained uncomfortable with the upgrade not reporting an actual, successful, complete update. So...

I restored my site files and database to pre-update, disabled the Remember Me plugin and re-installed the update with successful completion as expected. I feel comfortable with this and hope it helps others.

Thanks to everyone for sharing what helped you.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Sun Dec 29, 2013 12:56 am
by mahmoodtakolia
petersw wrote:I had the same problem. I couldn't fix the database. So, if you get the error on the "Fix" database option you should create the table "xxxx_content_types" in your database (mySQL) by the following SQL query:

CREATE TABLE IF NOT EXISTS `xxxx_content_types` (
`id` int(11) NOT NULL,
`content_history_options` varchar(5120) NOT NULL COMMENT 'JSON string for com_contenthistory options'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

where xxxx is your dbprefix in your database, e.g. 'd3hrs_'. You must change xxxx to your dbprefix!!!

After that the "Fix" database option should work!


Hi Thank you for the fix, it solved the problem with getting access to the admin page, however, when I try to edit or add a new category, I get the following error:
0 SQL=SELECT * FROM `jos3_content_types` WHERE `type_alias` IN ('com_content.category')

Please can you help me!!!

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon Jan 06, 2014 8:08 pm
by catalano
I'm having the same problem. I'm able to rename remember.php to rememberBAK.php and get the front end of the site to load. However, when I try to go to /administrator I just get the joomla logo with the copyright line on the bottom. There's no login panel or anything else. How can I get around this?

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Jan 07, 2014 2:01 pm
by kdkrun
Hazzaa wrote:Here is my solution
Rename your file remember.php to rememberBAK.php so it looks like this
/plugins/system/remember/rememberBAK.php
Find a copy of Joomla 3.1.15 and make a copy of the remember.php
FTP the file to your folder
/plugins/system/remember/remember.php
Now access your admin panel
Go to Extensions -> Extension Manage -> Database
Click Fix
Now go to ftp, delete the remember.php that you uploaded and rename the original one to it's correct state

Joomla updates do not update the database and this needs to be done manually.
For not developers, the above method is the simplest and quickest way

Good luck
This is right and I have test it with my system, but when you doing these kind of configurations please back up every thing before you do any changes, and clear your browser cash memory in each step.. and also you can close and open your browser on each step... don't angry with joomla .. this is good product.. and also remember this is world most valuable open source product that we ever see..

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Jan 07, 2014 7:45 pm
by QT7
I am upgrading from Joomla 2.5 to the latest version of Joomla. I am fairly new to Joomla and was following directions on a template site to upgrade to Joomla 3.2, by selecting short term support and upgrading. I didn't realize how crucial it is to back everything up, but that part wasn't included in the tutorial... This is my first Joomla site and I have put a lot of work into it.

I got the remember.php error, which led me to this thread.

Steps I've tried to fix this:
- I replaced my remember.php with remember.php from Joomla 3.1.6. I still can not get to my admin panel so i can't "Fix" the database.
-I ran this sql successfully:

Code: Select all

CREATE TABLE IF NOT EXISTS `xxxx(replaced with my db#)_content_types` (
`id` int(11) NOT NULL,
`content_history_options` varchar(5120) NOT NULL COMMENT 'JSON string for com_contenthistory options'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-I ran this sql query successfully:

Code: Select all

CREATE TABLE IF NOT EXISTS `XXXX_content_types` (
  `type_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `type_title` varchar(255) NOT NULL DEFAULT '',
  `type_alias` varchar(255) NOT NULL DEFAULT '',
  `table` varchar(255) NOT NULL DEFAULT '',
  `rules` text NOT NULL,
  `field_mappings` text NOT NULL,
  `router` varchar(255) NOT NULL  DEFAULT '',
  `content_history_options` varchar(5120) COMMENT 'JSON string for com_contenthistory options',
  PRIMARY KEY (`type_id`),
  KEY `idx_alias` (`type_alias`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 AUTO_INCREMENT=10000;
-I tried accessing my backend through administrator/index.php?option=com_installer&view=database, but i get a white screen.
-I removed the folder ./libraries/joomla/plugin
-I ran cli/deletefiles.php - apparently successful(?), I get a white screen.
-I replaced controller.php with the controller.php from Joomla 3.1.6

Now, I get the following errors:
In root folder:
Fatal error: Call to undefined method RuntimeException::get() in /libraries/joomla/error/error.php on line 797

In Administrator folder:
Fatal error: Call to a member function set() on a non-object in /administrator/components/com_login/controller.php on line 38

Line 38 is:

Code: Select all

		$this->input->set('view', 'login');
Questions:
Can I repair the table via phpmyadmin for a possible fix?
It may be possible that my extensions arent all compatible with Joomla 3 - would that completely break my upgrade?
What do I do to fix my site?

Any help is very much appreciated... I sure hope I can get this working :/

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Wed Jan 08, 2014 2:34 am
by Mishmobile
Hazzaa wrote:Here is my solution
Rename your file remember.php to rememberBAK.php so it looks like this
/plugins/system/remember/rememberBAK.php
Find a copy of Joomla 3.1.15 and make a copy of the remember.php
FTP the file to your folder
/plugins/system/remember/remember.php
Now access your admin panel
Go to Extensions -> Extension Manage -> Database
Click Fix
Now go to ftp, delete the remember.php that you uploaded and rename the original one to it's correct state

Joomla updates do not update the database and this needs to be done manually.
For not developers, the above method is the simplest and quickest way

Good luck
Hazzaa,

Thank you for your solution; my test site is up & running again!

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Thu Jan 09, 2014 6:34 pm
by pdfx
Hi all

Followed this thread after trying to upgrade to 3.21 from 2.5.17, seems I should have not pressed the button!! (was dreading making a mistake) seems like the upgrade is stuffed

I have had some of the errors mentioned in the thread, and seemed to have solved them, I now have
Front end: Fatal error: Call to undefined method RuntimeException::get() in /libraries/joomla/error/error.php on line 803

When i attempt admin:
Notice: Undefined property: LoginController::$input in /administrator/components/com_login/controller.php on line 38

Fatal error: Call to a member function set() on a non-object in /administrator/components/com_login/controller.php on line 38

Any thoughts,
Pd

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Fri Jan 10, 2014 3:36 pm
by QT7
Hazzaa's fix did not work for me.

Is there anyone who can help? I need to get this back up and running.. I can PM my site info if someone can help.. I know little about coding and am desperate.. I've spent a great deal of time on this, and it is being reviewed next week so I have to get it back up and working.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Fri Jan 17, 2014 2:48 am
by tiosus
bonez wrote:
brizola wrote:There is a simple solution, though an adhoc one: just disable the remember me plugin, make the update and enable the plugin again.
This option worked for me. :D
Thanks for the info brizola
its work for me

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Fri Jan 31, 2014 10:16 am
by lionheart_82
Hello,

In my case from Joomla 3.1 to 3.2.1, i had to replace both remember.php and remember.xml

You can find the v 3.1 and 3.2.1 files here(until 7-2): http://we.tl/3yrcm5BLpE.

Just remember after the manual upgrade:
a) Fix the Database

b) Search and install missing plugins

c) after the plugins-modules installation 2 components (ajax interface & Content history) might display an administration menu link that is invalid and will display and error. You can uninstall this manually from the #__menu table

d) The content history component might display an error after that procedure. What id did was to disable and re-enable the component, there are many articles in Google if it doesn't work though.

e) i all had a previous issue with the install from web plugin that couldn't be activated... all i did was to go to the plugin and save the settings..

I hope the info will be of help :)

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Thu Feb 06, 2014 11:54 am
by RubbelDeKatz
It happens if you update from 2.5.17 too.

Just goto line 94 at /plugins/system/remember/remember.php
and add the following line on top of the construct function.

Code: Select all

$this->app = JFactory::getApplication();
Then refresh your Browser by pressing F5 or loading
/administrator/index.php?option=com_joomlaupdate&task=update.install
to complete the update!

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Thu Feb 06, 2014 9:21 pm
by konczal
I got the fatal error when upgrading Joomla! 2.5.16 to Joomla! 3.2.2.

I followed the steps to rename remember.php and replace it with the one from Joomla! 3.1.5 (attached).

While I can now view my home page, the administrator URL gives me the following error:

Fatal error: Call to undefined method RuntimeException::get() in /mnt/web/cms/sandbox32/libraries/joomla/error/error.php on line 803

I checked my saved copies of both the Joomla! 3.1.1 and 3.1.5 distributions, and neither even has a /libraries/joomla/error/ folder.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Fri Feb 07, 2014 3:03 pm
by konczal
Additional: I restored remember.php from the actual version I was upgrading from (Joomla! 2.5.16).

The administrator URL now gives me this error:

Notice: Undefined property: LoginController::$input in /mnt/web/cms/sandbox32/administrator/components/com_login/controller.php on line 38

Fatal error: Call to a member function set() on a non-object in /mnt/web/cms/sandbox32/administrator/components/com_login/controller.php on line 38

The same errors appear when I try to resume the installation or fix the database:

/administrator/index.php?option=com_joomlaupdate&task=update.install
/administrator/index.php?option=com_installer&view=database

Finally, while I can view the home page, all menu links are broken and return the following error:

Fatal error: Call to undefined method RuntimeException::get() in /mnt/web/cms/sandbox32/libraries/joomla/error/error.php on line 803

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Sun Feb 09, 2014 9:05 am
by bruno05
I just upgraded a clean install from 3.1.1 to 3.2.2 and got the remember.php error. Really after all these months and thousands of posts all over the internet, the Joomla team promising to make the upgrade process better, they still have not fixed this?

Hire a few folks from Wordpress, and maybe those developers can show how the upgrade process is done. We also do Wordpress development and my team want to move completely to it. I love Joomla and do not want to move away from it, but these issues have been ongoing for years and somehow Joomla just fails to fix some fundamental issues.

Very frustrated by this process. Thankfully have a backup.

Will do a manual upgrade as obviously the auto upgrade is totally broke.

Bruno

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Feb 11, 2014 8:01 am
by crashtackle
Hi, I just upgraded from 3.0.3 to 3.2.2 via the 'Auto Upgrade' and got the dreaded remember.php error... I have tried to do what I can manage to understand on this forum to get it right, but with my limited 'techi' knowledge can not get it to work.

Front end works - admin now has a Joomla Logo and the copyright footer... nothing else.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Feb 11, 2014 10:52 am
by Webdongle
@crashtackle and @bruno05

Restore from backup
Disable the 'Remember me' plugin
Update
Enable the 'Remember me' plugin

Also you might try updating incrementally because you both updated from versions of Joomla prior to the fix.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon Feb 17, 2014 7:18 pm
by stuffdone
Has this bug been fixed for the next update?

Keep in mind many end-users manage their own site but are not techies and only know about clicking the "Update" button so if they do this and their site goes BOOM on them I get the blame!

Thanks.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Feb 25, 2014 5:15 pm
by pepe53
No it has NOT been fixed. I just ran the auto update and got al;l; the above errors. Because I was stupid enough to think that Joomla would not release an update without it being tested I did not do a backup. I now have to pay my host server £30 to put a serverside backup of the site back on. Needless to say I will NOT be doing anymore upgrades.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Feb 25, 2014 5:38 pm
by Webdongle
pepe53 wrote:... Needless to say I will NOT be doing anymore upgrades.
Surely the lesson learned is always keep a backup before making significant changes. Even if Joomla did update OK there is always the possibility of something going wrong. Not to mention the possibility of being hacked. You get hacked and your backup will be needed.

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Tue Feb 25, 2014 5:51 pm
by pepe53
Believe me. That is a lesson learnt big time!

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Sun Mar 23, 2014 2:35 pm
by birdeye
Followed the steps but now i have this error "Database schema version (3.2.3-2014-02-20) does not match CMS version (3.2.3)."

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Sun Mar 23, 2014 3:54 pm
by JAVesey
birdeye wrote:Followed the steps but now i have this error "Database schema version (3.2.3-2014-02-20) does not match CMS version (3.2.3)."
Lots of posts about this in Forums. It is a reporting error rather than a database error and it will be fixed in the next update. There is nothing actually wrong with your site or database and no need to do anything.

If it really bothers you then a fix has been posted elsewhere, but the reality is that there's nothing wrong/not working other than this small error.

HTH

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon May 19, 2014 10:52 am
by oxygen
Thanks @Hazzaa - simplest and most effective answer. Works first time :-)

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon May 19, 2014 1:10 pm
by sovainfo
For those that still don't understand solution provided by @Hazzaa is bad:

Proper solution:
Fix you infra by properly configuring your webserver and PHP.
As mentioned by many in the thread restore your backup, disable plugin "Remember me", do the update and enable plugin "Remember me" .
The update should report it updated successfully. Discover should not reveal extensions to be installed, Database should not reveal structural changes missing.
It is very unlikely you'll run into problems with future updates. Create a backup of your healthy environment.

Bad solution:
- Renaming remember.php gets you into the backend of an unhealthy environment.
- Joomla doesn't provide tools for recovery of failed update. The tools mentioned are not for that purpose. You need to recover manually.
- The update may have introduced new extensions that have not been administered properly. Extension manager->Discover can be used to register those extensions. Unfortunately the success is depending on where the update failed. Installing the discovered extension will hopefully install it properly and do everything required to use the extension.
- The Extension manager->Database fix to structural changes only fixes half the problem. As mentioned in the report it skips more than it processes. You need to verify whether you need to do something that it skipped.
- The update script should be examined to see what still needs to be done. Also see the logs/joomla_update.php

Hope you have kept your backup and do the update properly. Better to do it now than in 3 years time when you want to update to J4!

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon May 19, 2014 1:22 pm
by oxygen
sovainfo wrote:For those that still don't understand solution provided by @Hazzaa is bad:
...
As mentioned by many in the thread restore your backup, disable plugin "Remember me", do the update and enable plugin "Remember me" ...
I accept what you are saying, but this "Proper" fix is not retrospective is it?
I mean, I didn't know there would be an issue with the upgrade so I couldn't disable the "Remember me" plugin could I?

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon May 19, 2014 1:54 pm
by sovainfo
@oxygen: Don't know what you mean by retrospective. There is no reason not to disable the plugin before doing the update. Instead of renaming you should restore,disable,update. The renaming,running into all kinds of other problems to be fixed manually and hope you covered everything is a bad solution! Fix it before it is too late!

Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag

Posted: Mon May 19, 2014 2:06 pm
by oxygen
oxygen wrote: ... I didn't know there would be an issue with the upgrade so I couldn't disable the "Remember me" plugin could I?
I'll know for next time ;-)