I'd like to learn the reason why these lines might be creating this error.

Thanks

05-29-2013, 09:55 PM

NogDog

Anything in the PHP error log?

05-30-2013, 08:29 AM

chrisjchrisj

Quote:

Originally Posted by NogDog

Anything in the PHP error log?

I see no changes in the error_log file, last entry was 05/21/13.
Any additional help will be apprecaited

05-30-2013, 10:06 AM

NogDog

Next thing I'd look at is the HTTP logs, then maybe try turning up the PHP error_reporting level to E_ALL if it's not already there.

Also, sometimes weird things happen if you copy-paste code in terms of non-printing unicode or other non-ASCII characters getting picked up by the copy, so you might want to re-edit the file in your text-only editor of choice.

05-30-2013, 10:42 AM

chrisjchrisj

Thanks

Thanks for your reply. Much appreciated.
I don't know where the http logs are.
In public_html, the folder Logs has convertor.log.txt, logfile.rtf and search_log.txt, none of which show anything regarding an error today.
Also the error_log file shows nothing since 05-21-13. All these files are CHMOD'd at 777.
I don't know what E_ALL is.
Additionally, I idn't copy and paste, I simply replaced search.php with search.php from another working site.
Any additional help will be appreciated.
Thanks again.

05-30-2013, 10:50 AM

NogDog

Try sticking this at the top of the PHP file:

PHP Code:

<?phperror_reporting(E_ALL);

However, if the problem is a parse/compile error of some sort, that won't get triggered, in which case you would need to set it in either your php.ini config file or in .htaccess (via a php_value command).

05-30-2013, 12:01 PM

chrisjchrisj

Thanks for that help.
Just for my education, if I add that E_ALL code "to the top of the PHP code", what will it do?

05-30-2013, 07:42 PM

NogDog

PHP will log all errors, warnings, and notices (or, if you have the display_errors setting turned on, it will display them in the output).