Support

Admin Tools

#10873 deprecated.php running amok

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 Sunday, 29 January 2012 13:57 CST

Sunday, 29 January 2012 13:22 CST

tberg
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting ? Yes
Joomla! version: 1.7.4
PHP version: 5.3.6
MySQL version: 5.1.56
Host: http://cpanel6.proisp.no/~norskvur/norskvann/
Admin Tools version: 2.2.a3

Description of my issue:

After reinstalling ATP earlier today, I noticed that my logs/deprecated.php file was growing at an alarming rate. Within 15 minutes it was up to 6 Gb (!) with messages looking more or less like the file I'm attaching.

I'm not saying that ATP is behind this, but that's when I noticed the behaviour.

Any idea what is causing this?

Sunday, 29 January 2012 13:23 CST

tberg
BTW: Error logging is set to "None" until I figure this out.

Sunday, 29 January 2012 13:32 CST

nicholas
Torje,

You are doing something VERY WRONG on your site. If you read the description of the deprecated logging option you will see that you should enable it ONLY for a VERY LIMITED time and ONLY when debugging an extension you are writing. Last time I checked, Joomla! itself was adding a few hundred lines of its own on each page load. Even a "Hello, World" programme written using JCli throws three dozen of deprecated warnings, mostly due to the forced use of JLog and JError.

That put aside, please remember that Admin Tools is written to support Joomla! 1.5, 1.7 and 2.5, running on PHP 5.2 and 5.3 alike. As such it DOES have to use deprecated APIs. If it didn't, it would only run on PHP 5.3.9 hosts using Joomla! 2.5.0, i.e. on 1% of Joomla! sites. Not going to happen.

Finally, do remember that Joomla! ITSELF has not provided alternatives for all APIs it has marked as deprecated. The only way to reliably not use deprecated APIs would be not using the Joomla! Platform API at all. This completely beats the purpose, doesn't it?

So, the major problem I can see is that you're using a debugging tool on a live site, despite the clear warning in Joomla!'s interface and documentation not to. The intention of this tool is to let the CMS developers gradually revisit and refactor the entire codebase of the CMS, removing deprecated API calls. Then, third party developers can sing along and start replacing their calls to deprecated APIs. This will be a 2-3 year process. Complaining today that we're still using deprecated APIs is like complaining that even though scientists can produce tiny amounts of extremely expensive graphene in the laboratory, graphene is not used in cheap, ultra-high capacity batteries today. Yeah, sure, everybody would want that, but it'll take another 10 years or so before that's possible.

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!

Sunday, 29 January 2012 13:40 CST

tberg
Hmm.

I moved this site from another ISP (using Akeeba Backup and kickstart).

I didn't have these problems there, and I certainly haven't consciously enabled any debugging tools since moving.

Might this be an ISP-enabled issue?

Sunday, 29 January 2012 13:45 CST

nicholas
Not really. You had set the Error Reporting to "Development". You shouldn't do that. A live server should always have this set to None, unless you are trying to debug a PHP 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!

Sunday, 29 January 2012 13:55 CST

tberg
Hmmm again.

In my configuration file and on the admin panel it was set to none.

Any way. Turned off Debug System alltogether and that stopped it.

Thanks for your help, even though none of your coding was causing it!

Sunday, 29 January 2012 13:57 CST

nicholas
Technically, parts of my code are indeed using deprecated APIs, but that's required for Joomla! 1.5 compatibility. When the time comes to completely drop that kind of compatibility, I will drop the deprecated APIs. Most of them are stupid name changes, e.g. using quoteName instead of nameQuote :)

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!