Support

Admin Tools

#10193 Latest Update 2.2.a1 Security Exception Fatal Error

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 Friday, 06 January 2012 15:14 CST

Tuesday, 03 January 2012 13:14 CST

user48456
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 1.7.3
PHP version: (unknown)
MySQL version: (unknown)
Host: HostGator
Admin Tools version: svn670


Description of my issue:

After applying update I tried going to the Security Exception Log and when I click on Add To Blacklist I get a fatal error 


Fatal error: Call to a member function save() on a non-object in /home/dwrg/public_html/domain.com/administrator/components/com_admintools/controllers/log.php on line 34

Tuesday, 03 January 2012 13:48 CST

nicholas
Please try this https://www.akeebabackup.com/support/forum/admin-tools-support/500-error-accessing-waf-after-udate/55317.html#p55317

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!

Tuesday, 03 January 2012 14:04 CST

user48456
I Tried That already and is still giving me that fatal error message

Tuesday, 03 January 2012 14:45 CST

nicholas
No way, unless you have a failed installation. Take a look at what I've written here: https://www.akeebabackup.com/support/forum/admin-tools-support/upgrade-has-site-crashed/55388.html#p55388

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!

Tuesday, 03 January 2012 14:47 CST

nicholas
Ugh, not "failed" installation, I meant "partial", as in not all files have been copied to their final location. Most of the times, installing the update twice or using the manual installation method (as I mention in that other thread) fixes the problem.

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!

Tuesday, 03 January 2012 15:47 CST

user48456
I went ahead a read it multiple times to see if I missed something I did a re-installation to make sure it installed successfully and it did I also notice another error when you try to deleted a ip from the automatic ip block it will just refresh it wont deleted anything and if you tried to unpublished it you get the following error message on the top

Unknown column 'enabled' in 'field list' SQL=UPDATE `qm81e_admintools_ipautoban` SET `enabled` = 0 WHERE (`ip` = 71)

Tuesday, 03 January 2012 17:16 CST

nicholas
Fixed in dev release svn673.

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, 04 January 2012 12:09 CST

user48456
Thank You It Works Fine now

Wednesday, 04 January 2012 15:16 CST

nicholas
Awesome! Thank you for the feedback :)

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, 06 January 2012 01:24 CST

user17328
I have the exact error message:

Fatal error: Call to a member function save() on a non-object in /home/domain.com/administrator/components/com_admintools/controllers/log.php on line 34


Friday, 06 January 2012 12:10 CST

nicholas
Can you please try the latest dev release? It shouldn't throw that error any more.

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, 06 January 2012 12:49 CST

user17328
Just installed Release 688 and the exact same error is coming up.

Friday, 06 January 2012 12:52 CST

nicholas
No way. Line 34 on the new release reads:
);

In fact, lines 30-34 read:
$data = array(
			'id'			=> 0,
			'ip'			=> $item->ip,
			'description'	=> JText::_('ATOOLS_LBL_REASON_'.strtoupper($item->reason))
		);

and your error message reads "Fatal error: Call to a member function save() on a non-object" which is impossible to happen. Maybe the error message has changed a bit? Can you paste the new error message, please?

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, 06 January 2012 13:28 CST

user17328
The new error is as follows:

Fatal error: Call to a member function save() on a non-object in /home/domain.com/administrator/components/com_admintools/controllers/log.php on line 34

Friday, 06 January 2012 13:35 CST

user17328
Thank you for your prompt replies.

When I went into the admin tools, I saw that the admin tools needed an update after the svn688. I ran the update, which set me to version Admin Tools version 2.2.a1

However the same error pops up when I try to blacklist an IP.

Friday, 06 January 2012 14:15 CST

nicholas
I now see what you're doing wrong. You have to install the latest dev release (I am now uploading svn691). After installing it, it will tell you that there is an update available, 2.2.a1. DO NOT INSTALL THIS!!!! Remember, 2.2.a1 is the BROKEN release. The dev release is newer than this. However, all dev releases propose to be upgraded to the latest official release. This is by design. Until I publish 2.2.a2, you must NOT install an official release, or we're back to square 1, where we started. After installing svn691 you should see that all the reported issues are gone.

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, 06 January 2012 15:11 CST

user17328
Thank you for the prompt reply. The svn691 fixed the problem. Whatever it was. As you can see, nothing is impossible. You should never take these things personally. It's just software, and people have the weirdest configurations.

Again Thank you for all your hard work. I am sure that the rest of the Joomla community appreciates your work.

-AJ

Friday, 06 January 2012 15:14 CST

nicholas
Hi AJ,

The impossibility was not in the error message itself, but at the line number. I was trying to figure out why you were receiving a wrong line number. It was (and still is!) impossible that PHP decided to have the line numbers off by one. Well, the downgrade to 2.2.a1 explained it. But the error message allowed me to imagine where the problem was and fix it ;)

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!