Page 2 of 4

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

Posted: Thu Nov 14, 2013 2:07 pm
by sovainfo
Don't think we'll get to 3.1.15. Currently we are on 3.1.6, think 3.1.5 was meant.

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

Posted: Thu Nov 14, 2013 7:16 pm
by erickaps
Nice work Hazzaa!

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

Posted: Thu Nov 14, 2013 9:49 pm
by labon_jones
After the remember.php error I had one more hoop to jump through (plugins/user/joomla/joomla.php on line 228) but I followed the same steps Hazzaa suggested and it worked like a charm. Thanks. I was very worried for a while.

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

Posted: Thu Nov 14, 2013 10:43 pm
by omegareal
I have followed the advice for both the remember.php and joomla.php files, and I still do not have a Fix button when I go to the Database management page. I also do not have the skills to create a new table in the db as described, so I am at a loss as to how to fix it, and my site is currently offline as a result.

Any other advice?

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

Posted: Sat Nov 16, 2013 12:55 am
by brizola
There is a simple solution, though an adhoc one: just disable the remember me plugin, make the update and enable the plugin again.

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

Posted: Tue Nov 19, 2013 12:04 am
by dLuxMediaArts
I was getting the remember error but once I fixed that I know get the following error:

administrator/components/com_installer/controller.php on line 39


Btw this was going from an upgrade of 2.5.16 to 3.2.0 - I'm pretty sure my plugins are 3.0 compatible.

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

Posted: Fri Nov 22, 2013 1:43 pm
by Webdongle
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...
No Avail
now get error
Fatal error: Call to undefined method RuntimeException::get() in C:\wamp\www\test2\libraries\joomla\error\error.php on line 803

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

Posted: Sun Nov 24, 2013 5:31 pm
by bazo
Webdongle wrote: No Avail
now get error
Fatal error: Call to undefined method RuntimeException::get() in C:\wamp\www\test2\libraries\joomla\error\error.php on line 803
I have the same problem

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

Posted: Tue Nov 26, 2013 11:10 am
by oxygen
@Hazzaa - thanks very much for the tip!

It worked perfectly for me. I just happened to have the original J3.1 .zip installation file in my job archive for this site which made life easier tracking down the remember.php

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

Posted: Thu Nov 28, 2013 3:18 am
by hominid4
I tried renaming the remember.php file and FTPing it to the server and that didn't work. Per Hugh's suggestion, I checked and indeed did have the ./libraries/joomla/plugin folder; I renamed that first to test and it work, got rid of my error. I then removed it.

Thanks Hugh,
Wesley
cheesegrits wrote:Try removing the folder ./libraries/joomla/plugin.

What seems to be happening is that a lot of folders which should get removed during the 3.1 to 3.2 update, aren't getting removed if (I think) you use the ftp layer. So if you have a J! site which is fairly old, and has been through a number of updates, and (probably) if you use the ftp layer, you have folders and files which should no longer exist.

As a result, the wrong plugin model is being autoloaded, from the old ./libraries/joomla/plugin folder, instead of the new ./libraries/cms/plugin location.

If you look in ./administrator/components/com_admin/script.php, you'll find a big list of folders and files in the deleteUnexistingFiles() function, starting around line 279. You'll probably find that all of the ones after "// Joomla! 3.2" in those lists still exist on your site.

I'd suggest removing them all by hand, to make sure you don't get any other autoloader snafus.

-- hugh

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

Posted: Thu Nov 28, 2013 10:35 pm
by infidean
Webdongle wrote:
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...
No Avail
now get error
Fatal error: Call to undefined method RuntimeException::get() in C:\wamp\www\test2\libraries\joomla\error\error.php on line 803

Same problem here too.

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

Posted: Fri Nov 29, 2013 12:36 am
by sovainfo
You probably missed it but running cli/deletefiles.php will remove the obsolete files and folders. You are receiving an error in a script that shouldn't even be loaded. Maybe the webserver needs to be restarted or its cache cleared.

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

Posted: Fri Nov 29, 2013 1:43 am
by Webdongle
sovainfo wrote:You probably missed it but running cli/deletefiles.php will remove the obsolete files and folders.....
Yes I did miss it ... please a link to where you found that and instructions on how to run it on wamp ... thanks


Addendum
nm
C:\wamp\bin\php\php5.4.12\php.exe C:\wamp\www\test2\cli\deletefiles.php
did it ... can get in admin now but still a lot to do

Addendum 2
Run cli\deletefiles.php on php from the command line
go to /administrator/index.php?option=com_installer&view=database and fix

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

Posted: Fri Nov 29, 2013 2:28 am
by sovainfo
You could've just executed it from your browser: http://yoursite/cli/deletefiles.php
It doesn't provide any output so use your browser back button to return to what you were doing.

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

Posted: Fri Nov 29, 2013 2:39 am
by Webdongle
sovainfo wrote:You could've just executed it from your browser: http://yoursite/cli/deletefiles.php...
No it did not work that way ... because the site does not work so the same error is received :D Again I tested before I posted.

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

Posted: Fri Nov 29, 2013 4:29 am
by sovainfo
Yes, you are right, joomla requires a properly functioning infra. That is the only difference between the cmdline php and the url as far as I know!
Could this be a caching problem, again?!?

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

Posted: Fri Nov 29, 2013 10:09 am
by Webdongle
sovainfo wrote:Yes, you are right, joomla requires a properly functioning infra. That is the only difference between the cmdline php and the url as far as I know!
Could this be a caching problem, again?!?
Yes and because running it through the browser uses Joomla and Joomla is not working then running it through the browser will raise the the same error screen !!!

No it is not a cache problem ... when nothing on site.com works then trying to run any url after site.com does not work.

Did you actually test on a broken site ?

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

Posted: Fri Nov 29, 2013 11:56 am
by intheair
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
Worked for me, thanks for posting the solution. Why havent they fixed this?

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

Posted: Fri Nov 29, 2013 2:34 pm
by sovainfo
You can't say Joomla is not working, Joomla through a webserver is not working. Joomla from the cmdline does, otherwise you couldn't execute the cli via php from the cmdline.
So, parts of Joomla work depending how you execute them.

The fact that cli/deletefiles.php has the same problem only means it is using the same thing. You never know, till you know what the problem is.

The installation is also using parts of Joomla, that worked!

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

Posted: Sat Nov 30, 2013 2:29 am
by nzampella
Not exactly a 3.1 to 3.2 upgrade, but the error I'm seeing also occurs when trying to go to 3.1. I'm doing all this testing on Wamp Server before going live.

I'm trying to upgrade from 2.5.16 to 3.2. I've tried the ... 'replace controller.php' suggestion, as well as the delete the ./libraries/../plugins directory, and so on. I can see the Control Panel fine if I go to the /administrator/index.php page, but when I try to navigate to http://localhost/administrator/index.ph ... _installer, I get the fatal errors
Migrate.jpg
All the extensions are 3.x certified according to the JED, so I'm stumped. I'd like to get this initial site migrated before I attempt the other 5 I need to migrate.

Thanks in advance.

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

Posted: Sat Nov 30, 2013 3:12 am
by Webdongle
reinstate your backup to a new folder and new database
set Joomla! updater to sts and update (or download 3.2 and install from the extension manager)
When the update fails follow the instructions on http://forum.joomla.org/viewtopic.php?p ... 2#p3111960

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

Posted: Sat Nov 30, 2013 5:03 am
by unstand
Thanks for the information. This was helpful.

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

Posted: Sat Nov 30, 2013 5:34 am
by nzampella
Webdongle wrote:reinstate your backup to a new folder and new database
set Joomla! updater to sts and update (or download 3.2 and install from the extension manager)
When the update fails follow the instructions on http://forum.joomla.org/viewtopic.php?p ... 2#p3111960
OK ... cleared out everything, even updated WampServer.

Installed the site using a backup. Checked to makesure everything worked fine. Used the Joomla Update, selected STS updates, and proceeded from there. Went to 83.8% complete, then white screen.

Used the instructions linked to above, was able to get to the backend. Did the database fix, however, should have cleared out the previous SQL updates, as I did notice that many of the changes from 3.1.2, 3.1.5 and 3.2.0 were not added to the database.

Will proceed with another reinstall, and will clear out the old SQL update files, and then do the update.

BTW ... the joomla_update.php log file confirmed my thought that nothing was updated in the database past the original 3.0.0 database changes.

Will return with results from next test.

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

Posted: Sat Nov 30, 2013 7:12 am
by nzampella
2nd Test:
  • a) Deleted all site files, and dropped the database.
    b) Reinstalled using Akeeba Kickstart.
    c) Verified that 2.5.16 site worked
    d) Deleted all SQL update files in /administrator/components/com_admin/sql/updates/mysql
    d) Attempted install of 3.2.0 using Joomla! Updater. System overwrote files properly, but at 83.4% went to white screen.
    e) Verified that the SQL updates DID NOT properly run. The updates to 3.0.0 stopped at the midpoint of the SQL where the tables are being set to use InnoDB database engine.
    f) Modified SQL to remove commands already accomplished, and ran the rest of the 3.0.0.sql commands in phpMyAdmin to finish that update.
    e) Proceeded to modify SQL files 3.0.3.sql, 3.1.0.sql, 3.1.2.sql, 3.1.4.sql and 3.2.0.sql to enable them to run in phpMyAdmin
    f) I did discover that some of the 3.1.0.sql commands had already been done to the 2.5.16 database; this caused an abort. I'm assuming that it was done as part of one of the 2.5.x updates released at the same time as 3.1.0. Suggest that conditionals be added to the SQL commands so that commands will not abort the update.
    g) I then ran the deletefiles.php using the method as shown in the link http://forum.joomla.org/viewtopic.php?p ... 2#p3111960 from webdongle.
    h) I was then able to log into my backend without a problem. The proper administrator template was displayed (Isis), and the only issue that the Extension Manager -> Database displayed was that the database version was not updated. Clicking on the FIX button took care of that.
So the backend works fine .. however, I'm getting a frontend issue now:

Code: Select all

HtmlBehavior::mootools not found.

Call stack	
#		Function		Location	
1		JApplicationCms->execute()		D:\wamp\www\index.php:40	
2		JApplicationSite->doExecute()		D:\wamp\www\libraries\cms\application\cms.php:264	
3		JApplicationSite->route()		D:\wamp\www\libraries\cms\application\site.php:202	
4		JApplicationCms->route()		D:\wamp\www\libraries\cms\application\site.php:727	
5		JApplicationBase->triggerEvent()		D:\wamp\www\libraries\cms\application\cms.php:1052	
6		JEventDispatcher->trigger()		D:\wamp\www\libraries\joomla\application\base.php:106	
7		JEvent->update()		D:\wamp\www\libraries\joomla\event\dispatcher.php:162	
8		call_user_func_array()		D:\wamp\www\libraries\joomla\event\event.php:71	
9		plgSystemGCalendar->onAfterRoute()		 	
10		JHtml::_()		D:\wamp\www\plugins\system\gcalendar\gcalendar.php:39
I verified that GCalendar is the latest version and is listed as 3.x compatable in the JED.

I'm wondering if the initial issue is being caused by a PHP or MySQL timeout or connection disconnect.

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

Posted: Sat Nov 30, 2013 10:51 am
by Webdongle
nzampella wrote:c) Verified that 2.5.16 site worked
d) Deleted all SQL update files in /administrator/components/com_admin/sql/updates/mysql
d) Attempted install of 3.2.0 using Joomla! Updater. System overwrote files properly, but at 83.4% went to white screen.
Where in http://forum.joomla.org/viewtopic.php?p ... 2#p3111960 does it say to remove database files ?
nzampella wrote:I'm wondering if the initial issue is being caused by a PHP or MySQL timeout or connection disconnect
That is possible but please follow http://forum.joomla.org/viewtopic.php?p ... 2#p3111960 and it will work.

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

Posted: Sat Nov 30, 2013 3:28 pm
by tlink211
I had this, with the plugins/system/remember/remember.php on line 94. Renamed remember.php to rememberBak.php > site came back but had Control Panel error in Admin

I downloaded the 3.0 to 3.2 upgrade from joomla.org and installed it by FTP > nothing seemed to change. If I renamed rememberBak.php to remember.php I got white screens with the same remember.php Fatal error front end and admin both.

Found Hazzaa's solution but all I had to do by this time was fix the database:
Go to Extensions -> Extension Manage -> Database
Click Fix

Site and Admin seem to be working fine now.
To recap, My fix was:
>Download the 3.0 to 3.2 upgrade from joomla.org
>Install those files by FTP
>Rename remember.php to rememberBak.php (because you'll just have white error screens on site and admin at this point if you don't)
>In Admin -> Go to Extensions -> Extension Manage -> Database ->Click Fix
>Rename rememberBak.php to remember.php
>Done

Best of Luck to You.

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

Posted: Sat Nov 30, 2013 11:31 pm
by bwah
Hazzaa wrote:Rename your file as posted above. The site will allow you to access the admin panel long enough to fix your db
Then name the file back and it should be fine
Could only find a 3.0.2 copy, sadly my version didn't allow that. After login a new Fatal message:
Fatal error: Call to a member function checkSession() on a non-object in /customers/d/a/4/bwah.nl/httpd.www/test/plugins/user/joomla/joomla.php on line 228

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

Posted: Wed Dec 11, 2013 11:55 pm
by ChapullerOne
Issue comes from the libraries folder not being properly updated. The best thing to do is to simply delete libraries/joomla after the migration and replace it from a clean unzip of Joomla.

http://joomlacode.org/gf/project/joomla ... m_id=32568

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

Posted: Mon Dec 16, 2013 3:02 pm
by GertSterner
suem wrote:Thanks Hazzaa!
I had that problem in remember.php, then when I renamed and replaced it I had the same thing with joomla.php, so I did the same again. That got me to the error page, then I could get to the Database page with all the database errors listed - it's a pity the Fix button is small and a bit obscure up in the top left corner, I expected it to be below the errors...
Anyway, I've found it and we're up and running again :)
Thanks both Hazzaa and Suem. That helped me and my site now works on the backend again!

:D
Gert

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

Posted: Tue Dec 17, 2013 6:17 pm
by nolanf76
Hello,

I have also had the same problems with the upgrade. I have done everything suggested in the forum but now I appear to have a new problem. I am receiving the following message:

0 - An error has occurred.
Invalid controller: name='', format=''

Return to Control Panel

But when I click the link return to control panel nothing happens. So I am still unable to access the administration side of the website and on the front end of the website I now have error 1054.

Can anyone help??

Many thanks
Fiona