Support

Admin Tools

#11228 Fatal error: Call to a member function getValue() on a non-object in /mypath/plugins/system/admintools/admintools/core.php on line 78

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Wednesday, 29 February 2012 14:29 CST

Thursday, 23 February 2012 08:23 CST

user8290
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? yes
Have I read the documentation before posting (which pages?)? yes
Joomla! version: (2.5)
PHP version: (5.3.8 )
MySQL version: (unknown)
database version 5.1.56-log
Host: (optional, but it helps us help you)
Admin Tools version: (was updating to the newest pro version from 2.2.a3-pro )

Description of my issue:
I just hit the upgrade button for admintools and got error and now I can't get to the admin or the frontend.
Fatal error: Call to a member function getValue() on a non-object in /home/proboat/public_html/plugins/system/admintools/admintools/core.php on line 78

Fatal error: Access to undeclared static property: JLoader::$classes in /home/proboat/public_html/libraries/loader.php on line 189

Please help.

Thursday, 23 February 2012 08:29 CST

nicholas
Joomla!'s extension installer did its small miracle again... It is called in the last step of Live Update, asking it to install the component. It turns out that it removed the component's record from the database, causing the Admin Tools plugin to fail.

Start by removing the plugins/system/admintools directory from your site. This will allow you to get back to your site's back-end. Then try re-installing the component. This should normally solve this issue.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 08:44 CST

user8290
Thanks for the quick reply!

I removed /plugins/system/admintools and now the front end is working but when I go to the admin the page is blank, I can't login.
https://www.proboat.com/administrator/

Thursday, 23 February 2012 08:45 CST

nicholas
Oh, yes, I forgot about that. You may also want to delete the administrator/modules/mod_atjupgrade directory as well. This is the Joomla! update notification icon module installed by Admin Tools.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 08:58 CST

user8290
Did that, still no backend.
I doubled checked myself and I did delete administrator/modules/mod_atjupgrade

Do I also have to delete administrator/components/com_admintools ?

Thursday, 23 February 2012 09:05 CST

nicholas
Let's try a manual uninstallation which doesn't remove your settings, only the code. Using an FTP programme, please remove the following files and directories, in the order outlined below:
libraries/fof (only if you are not using Akeeba Subscriptions!)
plugins/system/admintools
plugins/system/atoolsjupdatecheck
plugins/system/atoolsupdatecheck
administrator/modules/mod_atjupgrade
components/com_admintools
administrator/components/com_admintools

Doing that there is absolutely no Admin Tools code running on your site. If your backend still doesn't load, the problem comes from a different extension, not Admin Tools.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 09:12 CST

user8290
If you look at my first post could it have something to do with second error?

First error:
Fatal error: Call to a member function getValue() on a non-object in /home/proboat/public_html/plugins/system/admintools/admintools/core.php on line 78

Second error:
Fatal error: Access to undeclared static property: JLoader::$classes in /home/proboat/public_html/libraries/loader.php on line 189

Just to be clear - I'm not using Akeeba Subscriptions so that means that I should delete libraries/fof ?


thanks again.

Thursday, 23 February 2012 09:14 CST

nicholas
The second error comes from a core Joomla! file. It's not something I've developed so I can't help with that.

If you do not have Akeeba Subscriptions then yes, please remove the libraries/fof directory.

And now a tough question. Is this a brand new site, or did you install/restore a Joomla! 2.5 site on top of a previous Joomla! 1.5, 1.6 or 1.7 site? The second error you mention reminds me of what I would experience when mixing files from different Joomla! versions.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 09:23 CST

user8290
I don't like tough questions but here goes... Yes, this is a previous 1.6-1.7

Why would it be causing problems now? After updating to 2.5.1 I then installed Admin Tools Pro. I also use Akeeba Backup but today I did a very stupid thing and did not do a backup before hitting the upgrade button.

Should I still follow your last instructions on removing the list of files?

Also I do not have a libraries/fof directory.

Thursday, 23 February 2012 09:37 CST

nicholas
I think you didn't get my question. If you used Admin Tools or Joomla!'s integrated upgrade to upgrade from Joomla! 1.6 to 1.7 to 2.5, it's OK. If, however, you had an existing site, let's say in Joomla! 1.7, and you restored a Joomla! 2.5 site ON TOP OF IT, without removing the old site, then this DOES cause problems. Is this the case, or did you upgrade from 1.6 to 1.7 to 2.5 using any of the two aforementioned procedures?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 09:46 CST

user8290
We went to 2.5 using Admin Tools.

Now do I continue to delete those files/directories?
I do not have a libraries/fof directory.


Thursday, 23 February 2012 12:21 CST

user8290
Ok, I deleted those files you listed but it did not work so I restored files and database from yesterdays server backup.

So now I'm afraid to upgrade Admin Tools.

Thanks for your help, wish I new what's going on.

Do you suppose its the Joomla Extensions manager update thats the problem.
Would I be safer going to Admin Tools > Update Found! Click to Update.

Thursday, 23 February 2012 13:31 CST

nicholas
Yes, it's best to use Live Update (the "Update Found!" button) in Admin Tools itself. FYI, if you delete all of the files and directories I mentioned, Admin Tools is no longer installed on your site. If this didn't work, the problem was certainly unrelated to Admin Tools.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 15:14 CST

user8290
Thanks Nicholas,

I did delete the files you mentioned and it did not work. I suspect the database got corrupted? The only thing I did was run the update so the problem is either Joomla Core code or the Admin Tools Update.

Thursday, 23 February 2012 15:19 CST

nicholas
Can you retry installing Admin Tools?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 23 February 2012 15:39 CST

user8290
I will but not today, just a bit wary that something will go wrong again and if something does go wrong I have to leave soon. On the road until Monday. But then I will try the upgrade and report back to you.

Friday, 24 February 2012 07:11 CST

user8290
Hi Nicholas,
There is one thing that I did not mention, maybe nothing to do with what went wrong. This site has very few extensions - JCEditor, Akeeba Backup, and Akeeba Admin Tools
with a joomlashack template impacto.
I had Akeeba Admin Tools installed, then I subscribed to the Pro Version. I installed the Pro version without uninstalling the free version. Should I have uninstalled the free version and then intalled the pro version?

Friday, 24 February 2012 07:20 CST

nicholas
Nope. Going from Core to Pro is supported. However, sometimes the Joomla! installer screws up when going from Core to Pro; it's the same version with a different list of files, so the extensions installer ends up not copying all files. A second installation attempt usually solves this.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 24 February 2012 07:39 CST

user8290
I just read on another post you mentioned:
2.2.a3 can't update to 2.2 stable. You'll have to use the Live Update to go from 2.2.a3 to 2.2 stable.

2.2.a3 is what I have installed. So I'm unsure of how I should update to 2.2 stable?

Do I download the 2.2 stable and use the Extension manager to install the update?
The reason I ask is I think I was using the live update which is what broke the site or by live update do you mean going to the Admin Tools panel and use the UPDATE FOUND! Click to Update?

Would it be safer to uninstall 2.2.a3, then use the Extension manager to install 2.2 stable?

Sorry for so much back and forth, I just don't want to break the site again, I have no time right now to reinstall from a backup.

Friday, 24 February 2012 07:47 CST

nicholas
Going from 2.2.a3 to 2.2.0 is, of course, supported using any installation method: Live Update or installing the 2.2.0 package on top of 2.2.a3. Maybe that post was much older or I was referring to something else (or, most likely, going from 2.2.0 back to 2.2.a3, this is something I've written quite a few times lately).

Moreover, the issue you have is NOT related to Admin Tools. When I told you to delete a bunch of files you practically uninstalled Admin Tools. All PHP code related to Admin Tools was gone. Vapourised. No longer running. Not there. Absent. I don't know how else to say this. It's software, not witchcraft. If the code IS NOT THERE, there is nothing to run. If you delete all of Admin Tools' files, using my instructions, Admin Tools is no longer installed and no longer runs and can not have anything to do with any issues you continue to have with your site.

If you don't feel comfortable restoring backups of your site on the live server, why don't you do something dead simple? Take a backup of your site. Restore it on a local server (e.g. XAMPP, WAMPserver, Zend Server CE, MAMPP, Uniform Server, ...) or a new subdomain. Try the update on that clone of your site. With Akeeba Backup (even the free Core release) you can do that in a matter of minutes.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 24 February 2012 08:04 CST

user8290
Ok, thanks, I've taken up enough of your time. You can close this ticket, I'll follow your suggestions.

Friday, 24 February 2012 08:08 CST

nicholas
I'll leave the ticket open so that if you run into any issues after the resintallation you can post back here and I can remember all of our conversation, allowing me to help you faster :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 27 February 2012 13:57 CST

user8290
I'm working with Greg to resolve the problem updating Admin Tools. I pulled down a backup of the live site and set it up locally using MAMP. I've run into some errors with the upgrade and here's what I did:

Went to Components > Admin Tools
Saw the Update Found button and clicked on it.
Was giving this warning: You have to supply your username/password or Download ID to the component's parameters before trying to upgrade to the latest release. The upgrade button will remain disabled until you do that.

Returned to the main Admin tools screen and clicked on Options and entered ID
Returned to the Live Update page and clicked on the Update to the latest version button.
Got these errors:
• JFolder: :files: Path is not a folder. Path: /Applications/MAMP/htdocs/ProBoatLocal/tmp/com_admintools_update
• JInstaller: :Install: Cannot find Joomla XML setup file
• Invalid package type. The update can not proceed.

Can you tell me what might be going on?


Thanks,

Michelle

Tuesday, 28 February 2012 01:47 CST

nicholas
You have to follow the instructions about the Download ID, of course.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 29 February 2012 12:32 CST

user8290
Thanks for the link. I followed the instructions and added the download ID. I refreshed and then ran the update locally and it worked fine.

I then went to the live site and added the download ID. I refreshed on the live update page and then clicked the button to update. I got this error:

Fatal error: Cannot pass parameter 2 by reference in /home/proboat/public_html/administrator/components/com_admintools/liveupdate/classes/download.php on line 40

Fatal error: Access to undeclared static property: JLoader::$classes in /home/proboat/public_html/libraries/loader.php on line 189

I looked it up on your site and saw that some folks got around it by changing the tmp directory to 777. I did this and the update ran correctly. I then changed the tmp directory back to 755.

Does the tmp directory need to be set to 777 for live update to work?


Thanks,

Michelle

Wednesday, 29 February 2012 14:29 CST

nicholas
Normally Live Update should work even when the tmp directory is not writable, as long as you have Joomla!'s FTP mode enabled. But you bumped into a bug which only occurs in PHP 5.3 as far as I can see. Nice catch, I am writing a workaround now.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!