rocknbil - 5:32 pm on Nov 21, 2011 (gmt 0)
the error - .. - is not public.
Recently, somebody pointed out that the site shows the following error:
Anyway all right then, you search your scripts for
News WHERE id
If it's properly coded, those values might be in variables, something like
.. from $current_table where $target_field = '$target_value'
(don't search for those variables, they are just for example)
So it might make that may be harder to find. You'll have to locate what exact function it's doing when that happens. For example, if it happens when someone searches it's in a search function; or opening an item's detail, the detail function.
I will need to find php.ini ... do I have to change "Display Errors to On"?
No . . . .there are two things at play here.
There are php errors/warnings, and there are mySQL errors/warnings. They are distinctly different "layers." When you see this,
You have an error in your SQL syntax;......
This is a mysql error, but if the script is set up to display errors, it passes from the database interface to PHP. so you are chasing a "ghost" by changing php.ini in any way to display or not display errors. To answer the question, it's best if the global PHP error display settings in php.ini are set to off.
If you need it, a better way to display errors is to temporarily add this at the top of your php script:
<?php error_reporting(E_ALL); ?>
This allows PHP errors to display in this script while leaving the global error reporting off. But the issues is that what you have there is a mySQL error, not a PHP error.