Upgrading from dev version to beta1, I broke what had been working.

To install, I completely uninstalled the old version before installing the new version. Now I can't get the new version to work.

I observe these two things when I try to refresh a feed to create new feed items:

1. This error message is displayed:
user warning: You have an error in your SQL syntax near 'ON fi.nid = n.nid WHERE fi.feed_nid = 965 ORDER BY fi.timestamp DESC' at line 1 query: SELECT n.nid FROM node n JOIN feedapi_node_item fi ON fi.nid = n.nid WHERE fi.feed_nid = 965 ORDER BY fi.timestamp DESC in /var/www/drupalbase/includes/database.mysql.inc on line 172.

I confirmed that the table feedapi_node_item was created when the module was installed. I appears that all fields were properly created, as well.

2. After refresh, I also receive a message like:
10 new item(s) were saved. 0 existing item(s) were updated.

Despite this message, there are no new items to be found. The feedapi_node_item table remains empty. No links appear on the feed node.

These problems are observed using both the lightweight items aggregator and the feed node aggregator.

Comments

alex_b’s picture

Assigned: Unassigned » alex_b
Category: bug » support

Hi jns,

Thanks for reporting.

I ran the query in 1.) on a vanilla feedapi 1.0 beta 1 install and had no problems. An idea for finding out what is wrong in your installation might be to try to run this query directly through a SQL client on your database and see what exactly fails.

These are the fields you should have in feedapi_node_item:

fiid feed_nid nid url timestamp arrived guid

What database are you using MSQL or PostgreSQL?

Number 2.) seems to be related to number 1.) - if the SQL statement above fails, you won't be able to see items on your feeds.

Let's concentrate first on get this working with the feedapi_node processor.

Alex

jimsmith’s picture

I am using MySQL version 3.23.58.

I checked the table and found all rows were there.

The error message from the SQL client doesn't say anything I didn't know before:
failed : You have an error in your SQL syntax near 'ON fi.nid = n.nid WHERE fi.feed_nid = 966 ORDER BY fi.timestamp DESC' at line 1 ' at line 1

alex_b’s picture

Did you try to find out what exactly the problem with the SQL query is? - as I can't reproduce this error it would be really helpful for me to know what exactly in the query fails.

jimsmith’s picture

Yes I did. Unfortunately, I'm not getting any additional information, or perhaps I don't know where to look to get that additional information. I providing as much as I have.

I believe the problem could be with my particular version of MySQL. I have seen problems, for example, with tables not installing, when I have installed some modules on my server. In those cases I have had success manually creating the tables.

However, this seems to be different, as the feedapi_node_item table is installed. Initially it appeared nothing was writing to it. Now it will, but I continue to get the error message and none of the nodes appear on the feed page.

If I am using FeedAPI in the simple aggregator mode I get the same error. Are the feed items also supposed to write to the feedapi_node_item table when a node is not being created? In this mode they do not on my system.

alex_b’s picture

What I meant was, could you try variations of

SELECT n.nid FROM node n JOIN feedapi_node_item fi ON fi.nid = n.nid WHERE fi.feed_nid = 965 ORDER BY fi.timestamp DESC

to find out which part of the SQL query is breaking and then post here which one it is?

e. g.: does

SELECT n.nid FROM node n JOIN feedapi_node_item fi ON fi.nid = n.nid

break?

Could you also post here the exact structure of your feedapi_node_item table? - Most easily, you could just export the table structure with mysql or phpmyadmin.

Are the feed items also supposed to write to the feedapi_node_item table when a node is not being created? In this mode they do not on my system.

This behaviour is ok. feed items that are not nodes won't be written into feedapi_node_item table.

Did you try a fresh install on the same server? Did it work?

Alex

alex_b’s picture

Title: upgrade trouble » Upgrade from < 0.6 to 1.0 beta 1 trouble

More descriptive title.

aron novak’s picture

Status: Active » Closed (fixed)

No reaction for 9 months. Nobody wants to upgrade between ancient versions now.