Error log

[MrGForce +]

Constantly getting the same errors showing up in my error log file. They're always referring to the same lines of code in the same includes file. I've enclosed the last several errors and the copyright info from the mysql.php file they are referring to, which I have not made any changes to. The file is from the 4.1.5 version. The last error occured when I did a renewal on one of my listings. The listing seems OK so I don't know what the error is trying to tell me.

The errors .......

[31-Dec-2009 10:37:01] PHP Notice: Query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 SQL: SELECT cTitleCharacters,cShortDescCharacters,cCharacters, cDisURL,cNumImages,cAllowImages,cFeatured,cFeature dPrice,cBold,cBoldPrice,cHighlighted,cHighlightedP rice FROM woogie_products_packages WHERE pID= in /home/mrgforce/public_html/includes/classes/database/mysql.php on line 143


[31-Dec-2009 10:37:01] PHP Notice: Query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY fOrder ASC' at line 1 SQL: SELECT f.fID, f.fOrder FROM `woogie_fields` AS f INNER JOIN woogie_fields_bindings AS fb ON fb.fieldID = f.fID AND fb.catID = ORDER BY fOrder ASC in /home/mrgforce/public_html/includes/classes/database/mysql.php on line 143


[31-Dec-2009 10:37:01] PHP Warning: Smarty error: unable to read resource: "" in /home/mrgforce/public_html/includes/classes/smarty/Smarty.class.php on line 1092


[12-Jan-2010 17:34:06] PHP Notice: Query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 SQL: SELECT id,title,tweeted FROM woogie_listings WHERE id= in /home/mrgforce/public_html/includes/classes/database/mysql.php on line 143


[13-Jan-2010 06:43:55] PHP Notice: Query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 SQL: SELECT id,title,tweeted FROM woogie_listings WHERE id= in /home/mrgforce/public_html/includes/classes/database/mysql.php on line 143


[13-Jan-2010 10:25:19] PHP Warning: Smarty error: unable to read resource: "" in /home/mrgforce/public_html/includes/classes/smarty/Smarty.class.php on line 1092


The copyright from the mysql.php file......

<?php
/**
* @copyright 68 Classifieds
*
* @author 68 Designs, LLC
* @version $Revision: 65 $
* @package 68Classifieds
* @link 68 Classifieds - PHP Classifieds Script
*
* @Updated: $Date: 2008-11-12 21:51:29 -0500 (Wed, 12 Nov 2008) $
*/


************************************************** ************

Anyone know what might be causing these errors?

Thanks.





.

[Lhotch +]

Looks like the package the ad was originally placed under no longer exists.

[MrGForce +]

None of the packages have changed or have been deleted. I did find out that the listing was updated through a secondary test install that I had placed in a directory under the original, which uses all the same templates, database etc that the original one does. Didn't realize someone would find this test site so quickly. All I did was change the look and layout of this test site by editing some of it's main templates such as the layout and home templates. Did nothing to any of the core files.



.

[Lhotch +]

It would appear by the errors that certain variables are not present for the mysql query to use. This could be due to changes you have made to templates or core files or possibly special characters in the ads title.

Have you altered any of the core php files?

Have you tried using the default untouched templates to see if errors are still triggered?

[MrGForce +]

No Larry, I haven't edited any of the core files other than say the language file which hopefully wouldn't have anything to do with this.

I have made extensive revisions to many of the purple and default templates, so I will take a look at a bunch of them to see what I may have left out.

It's just a shame that the errors don't indicate what was being done at the moment the error occurred. That would give me some place to look. At least the errors don't seem to be causing anything to happen to the database, at least I don't see anything.

I'll see what I can find. Thanks for the help steering me in the right direction. I really appreciate it.


.

[Lhotch +]

Instead of digging through your templates the easiest thing to do is just switch to the default untouched template and see if the errors continue. If they do you know its your templates, if not then no sense wading through your templates. Make sure to clear the template cache if you switch templates.

[MrGForce +]

I'll do that and see what happens. Might take a while to see, as the errors weren't occurring very often.

Thanks again.