Classifieds filling up error log - undefined constants

[ktmtalk]

Hey Chuck... my entire system just crashed big time... out of disk space. There is a 600 gig error log full of these:

Content visible to verified customers only.

.

[Chuck S]

Turn down your PHP error reporting level. That should fix your log issue

[ktmtalk]

Originally Posted by Chuck S

Turn down your PHP error reporting level. That should fix your log issue

at the top of pp-inc.php???
at the top of pp-inc.php, we have:
error_reporting (E_ALL ^ E_NOTICE);

what if I add some defines at the very top of pp-inc.php?
for example:

Content visible to verified customers only.

[Chuck S]

No our reporting on the script is set correctly thats why you dont see empty variables all the garbage like that. Your server side must be set to report every little thing. You can talk to your host about this if you dont have access to edit the server php settings. that would be in your php.ini file.

[ktmtalk]

Chuck... with all due respect, I should not have to change the php.ini file for the classifieds system.

If there is a statement in the classifieds that is causing an error because, as in this case, it is making a reference to a variable that has not been declared, then the code needs to be fixed so it doesn't cause that error.

Then again... thats the way I feel... Your Mileage May Vary.

btw: I am the host...

.

[Chuck S]

Well our classifieds is not showing any errors is it?

There is nothing wrong with the constants use in the files they use valid PHP.

The issue is the server wide php error reporting is set TOO HIGH. Hense your error log is reporting empty variable etc etc so if you look at it this way if your the host your the one causing this. If you turn down the reporting to only report true real php errors like noted in our script you will not get those types of things reported in your logs.

The defines your talking about are already defined in config-intc.php

[ktmtalk]

The defines your talking about are already defined in config-intc.php

yes they are but not all modules include that file... hence the errors from calling a variable that is never set.

fine... somehow I knew this would end up being my fault and not the code.

[Chuck S]

Those variables are defined and called and used throughout the program.

pp-inc.php which is our global file used by all program files requires config-inc.php. That file requires header-inc.php and that file requires config-intc.php. See they are indeed defined. They are either on or off.

No one is placing blame here. I am merely explaining what your issue is. It has to do with PHP error reporting on the server being set to high. I am sorry you dont like my answer but I cant give you another.

There is no magical change to the code I can tell you to prevent what happens in your error logs based on what is being reported.

[ktmtalk]

Originally Posted by Chuck S

Those variables are defined and called and used throughout the program.

pp-inc.php which is our global file used by all program files requires config-inc.php.

yeah ??? How about showing me where you include that file in pp-inc.php BEFORE you make reference to those variables in pp-inc.php.

here is the pp-inc.php code you updated on 11/09/09

Content visible to verified customers only.

No include config-inc.php before the reference to "VB3_INTEGRATION" is made.

here is the pp-inc.php code you updated on 10/28/09

Content visible to verified customers only.

again.... No include of config-inc.php before the reference to "VB3_INTEGRATION" is made.

I could post the other updates but the point is moot.

There is NO include of "config-inc.php" before the reference is made to "VB3_INTEGRATION" .... hence, there will always be an error generated when a reference is made to an undeclared vraiable.... just like the 600 gig error log shows.... thousands and thousands of times.

forget it... I'll fix it myself. Like I said... I knew it was going to end up being my fault.

.