Upgrade from 3.1 to 3.2 Fatal Error in Administrator Page
-
- Joomla! Exemplar
- Posts: 8808
- Joined: Sat Oct 01, 2011 7:06 pm
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Don't know whether it is needed next time. You might even restore 3.1 and update to 3.3. First try without disabling. You could also update 3.2 to 3.3.
Sofar, the actual cause of the issue has not been identified AFAIK. You might want to try https://github.com/joomla/joomla-cms/pull/3467.
Sofar, the actual cause of the issue has not been identified AFAIK. You might want to try https://github.com/joomla/joomla-cms/pull/3467.
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!
Blank screen? Verify pagesource for HTML code (javascript error)
Installation failing on populating database? Install with set_time_limit(0)
Document your customizations!
-
- Joomla! Fledgling
- Posts: 3
- Joined: Fri Mar 30, 2012 11:57 am
- Location: Turin, Italy
- Contact:
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
OMG I was in pain. I managed whit the method
rename remember.php -> rename joomla.php -> create table -> fix db
But now I have the backend layout totally mixed up.
Why!?
rename remember.php -> rename joomla.php -> create table -> fix db
But now I have the backend layout totally mixed up.
Why!?

-
- Joomla! Fledgling
- Posts: 3
- Joined: Fri Mar 30, 2012 11:57 am
- Location: Turin, Italy
- Contact:
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Sorry, what do you mean with "search"? Manual search?lionheart_82 wrote:b) Search and install missing plugins
I think I miss some plugin because the layout of backend is confused...
-
- Joomla! Fledgling
- Posts: 3
- Joined: Fri Mar 30, 2012 11:57 am
- Location: Turin, Italy
- Contact:
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Well, I can answer to me
The last step was to Discover and Install all plugins and templates missing, then select isis as backend template.
http://docs.joomla.org/Help33:Extension ... r_Discover

The last step was to Discover and Install all plugins and templates missing, then select isis as backend template.
http://docs.joomla.org/Help33:Extension ... r_Discover
-
- Joomla! Fledgling
- Posts: 1
- Joined: Fri Jun 20, 2014 7:52 pm
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Thank you so much, your solution solved my problem and I was able to upgrade finally to 3.3.1Hazzaa 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
-
- Joomla! Intern
- Posts: 97
- Joined: Tue Jun 02, 2009 12:10 pm
-
- Joomla! Fledgling
- Posts: 3
- Joined: Wed Sep 03, 2014 10:40 am
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
How do I disable the remember me plugin?
It's greyed out, and marked with a lock icon (for protected).
It's greyed out, and marked with a lock icon (for protected).
-
- Joomla! Exemplar
- Posts: 8808
- Joined: Sat Oct 01, 2011 7:06 pm
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Go to Extensions->Plugin manager
Search for Remember and click on status to disable.
Search for Remember and click on status to disable.
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!
Blank screen? Verify pagesource for HTML code (javascript error)
Installation failing on populating database? Install with set_time_limit(0)
Document your customizations!
-
- Joomla! Fledgling
- Posts: 3
- Joined: Wed Sep 03, 2014 10:40 am
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Hey sovainfo.
That's what I'd usually do, but the plugin is protected (greyed out and marked with a lock icon) and I can't click on it. Clicking on status does nothing. Is this unusual behaviour? What can I do to disable it?
That's what I'd usually do, but the plugin is protected (greyed out and marked with a lock icon) and I can't click on it. Clicking on status does nothing. Is this unusual behaviour? What can I do to disable it?
-
- Joomla! Exemplar
- Posts: 8808
- Joined: Sat Oct 01, 2011 7:06 pm
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Think you are confused with Extensions->Extension manager->Manage!
For some reason you can not disable protected extensions there, use Plugin manager!
For some reason you can not disable protected extensions there, use Plugin manager!
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!
Blank screen? Verify pagesource for HTML code (javascript error)
Installation failing on populating database? Install with set_time_limit(0)
Document your customizations!
-
- Joomla! Apprentice
- Posts: 12
- Joined: Mon Apr 07, 2014 1:21 am
- Location: 70 6a St. NE Calgary, Alberta
- Contact:
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
Thank you Hazza and PeterSW! Worked perfect.
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!
-
- Joomla! Exemplar
- Posts: 8808
- Joined: Sat Oct 01, 2011 7:06 pm
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
No, it doesn't!
Read the whole thread and you'll know why!
Read the whole thread and you'll know why!
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!
Blank screen? Verify pagesource for HTML code (javascript error)
Installation failing on populating database? Install with set_time_limit(0)
Document your customizations!
-
- Joomla! Fledgling
- Posts: 1
- Joined: Tue Dec 02, 2014 10:57 am
Re: Upgrade from 3.1 to 3.2 Fatal Error in Administrator Pag
I try to install autotrweeting but is not working and i uninstall one, log out. Next day i have same error via admin "Class 'FOR Platform' not found in " I try to change remember.php - not help.
So for me works:
I find same Joomla version what i have (3.2) and just rewrite "fof" folder in the /libraries/fof
and it start working!
Just my suggestion please backup a original fof folder (in case)
Good luck to everibody
So for me works:
I find same Joomla version what i have (3.2) and just rewrite "fof" folder in the /libraries/fof
and it start working!
Just my suggestion please backup a original fof folder (in case)
Good luck to everibody