I'm starting this out as a support request since I don't know enough to call out a "bug".
While I cannot see any loss in functionality, I am getting LOTS of RED MySQL user warnings at top of a lot of pages including Home page -- mostly stuff like:
user warning: 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 ' , FROM node n LEFT JOIN flexinode_data flexinode_2 ON n.nid = query: SELECT , , FROM node n LEFT JOIN flexinode_data flexinode_2 ON n.nid = flexinode_2.nid AND flexinode_2.field_id = 2 LEFT JOIN flexinode_data flexinode_6 ON n.nid = flexinode_6.nid AND flexinode_6.field_id = 6 LEFT JOIN flexinode_data flexinode_1 ON n.nid = flexinode_1.nid AND flexinode_1.field_id = 1 WHERE n.nid = 35 in /home/suzan24k/mysite/includes/database.mysql.inc on line 120.
With my SQL experience I see that after the SELECT there are two commas that don't look right, but I certainly don't know where to fix something I did potentially wrong.
Does anyone have any clues on how I can get rid of the warnings beside turn off flexinode?
I would like to add that I am running on PHP 4.4.0, MySQL 4.0.23, Drupal 4.7.3 and the latest (I know of) flexinode version 1.77.2.1 2006/08/22 12:11:32 ber Exp $.
Much appreciation.
Suzan
Comments
Comment #1
suzan24k commentedWhile waiting for a kind soul(whom never appeared) to give me some pointers, I've been testing a lot of different options.
I got my warnings to go away. I did two things; the last being what I think fixed the problem.
1. I did my best to install the CVS version of flexinode. I think it worked but I stil was getting warnings.
2. From my phpMyAdmin panel I exported with Drop Table 4 tables: event, flexinode_data, flexinode_field, flexinode_type. I deleted the inserts since I wanted to remove all the records. (I'm not sure I should recommend this removing inserts part but I did this since my site is not up and running.)
I then ran the four exported SQL table drop and create code.
I think I ran the www.example.com/update.php since I was running that quite often. Not sure it ever made a difference.
While my efforts and explanation may not be the true fix needed for others in the future with similar problem, I thought I would post the potential solution here. Knowing me, I will probably be looking for the same solution again some day and glad I posted something here.
Thanks to anyone whom may have sympathized with me.
Suzan :-)
Comment #2
Bèr Kessels commentedClosing old issues.