Hi!

Many thanks for this perfect and necessary product. But now I have some problems.

For 5.x-1.0.

There is a mistake on page mysite.com/feed-item/1 after change of some nodefeed's parameters:

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 'DESC LIMIT 0, 10' at line 1 query: SELECT node.nid, feedapi_node_item.nid, feedapi_node_item.timestamp AS feedapi_node_item_timestamp, created FROM rss_drupal_node node LEFT JOIN rss_drupal_feedapi_node_item feedapi_node_item ON node.nid = feedapi_node_item.nid WHERE (feedapi_node_item.feed_nid = 4) ORDER BY feedapi_node_item_timestamp DESC, DESC LIMIT 0, 10 in /var/home/......./public_http/includes/database.vbulletin.inc on line 164.

After that

During update 5.x-1.0. to 5.x-1.x-dev (2008-Feb-19):

user warning: Table 'nattabi2.feedapi_node_item' doesn't exist query: REPLACE INTO rss_drupal_feedapi_node_item_feed (feed_nid, feed_item_nid) SELECT feed_nid, nid FROM feedapi_node_item in /var/home/...../public_http/includes/database.vbulletin.inc on line 164.

...

The following queries were executed

feedapi_node module

Update #3

    * CREATE TABLE IF NOT EXISTS {feedapi_node_item_feed} ( `feed_nid` int(10) unsigned NOT NULL default '0', `feed_item_nid` int(10) unsigned NOT NULL default '0', PRIMARY KEY (`feed_nid`,`feed_item_nid`), KEY `feed_nid` (`feed_nid`), KEY `feed_item_nid` (`feed_item_nid`) ) DEFAULT CHARSET=latin1;

    * <strong>Failed<strong>: REPLACE INTO {feedapi_node_item_feed} (feed_nid, feed_item_nid) SELECT feed_nid, nid FROM feedapi_node_item

    * ALTER TABLE {feedapi_node_item} DROP `feed_nid`

....

All tables have a prefix (for example, 'rss_drupal_').

Thanks.

Serg

PS

My System Information:


$db_prefix
    Array ( [default] => rss_drupal_ [authmap] => sha_drupal_ [sessions] => sha_drupal_ [sequences] => sha_drupal_ [users] => sha_drupal_ [profile_values] => sha_drupal_ [role] => sha_drupal_ [users_roles] => sha_drupal_ [bueditor_buttons] => sha_drupal_ [bueditor_editors] => sha_drupal_ [locales_meta] => sha_drupal_ [locales_source] => sha_drupal_ [locales_target] => sha_drupal_ [user] => drupal_ ) 

Active Drupal modules

    adminrss, block, blockcache, bueditor, color, feedapi, feedapi_aggregator, feedapi_inherit, feedapi_mapper, feedapi_node, feedapi_node_views, filter, googleanalytics, help, imce, locale, menu, node, panels, panels_export, panels_mini, panels_node, panels_page, panels_simple_cache, panels_views, parser_common_syndication, parser_simplepie, path, profile, rustemmer, search, site_map, statistics, system, taxonomy, update_status, user, vbbirthdays, vbcore, vbforumblocks, vbpm, vbpolls, vbuser, views, views_argument_api, views_bonus_archive, views_bonus_export, views_bonus_grid, views_bonus_panels, views_bonus_summary_combo, views_bookmark, views_rss, views_ui, watchdog

Current memory usage
    13764536

Database class
    vB_Database

Database client encoding
    utf8

Database driver
    includes/database.vbulletin.inc

Database encoding config
    utf8

Database interface
    mysql

Database version
    5.0.51

Drupal version
    5.5

PHP version
    5.2.5

memory_limit
    52M

vBulletin version
    3.6.8

vbDrupal version
    5.5.1

Comments

aron novak’s picture

Assigned: Unassigned » aron novak
Status: Active » Postponed (maintainer needs more info)

Well, I committed a fix about the upgrade. I hope you had a backup, if the site is production, so you can step back easily. The upgrade can be done now without problem at your environment too.

For 1.0:
Can you describe here exactly what have you changed in nodefeed's parameter and why? The bogus SQL query, as far as i can see, comes from views. I see the error in the query: "DESC, DESC", but i cannot explain the reason unless you tell me exactly how you modified the original views, which is created by FeedAPI Node Views module.

Poznii’s picture

Hi, Aron.

Thanks for the answer. With backup all by ok. :)

I changed nothing in the 'feed-item' view's and did not use 'add' for this view. I only saw, what it there is and it is enabled.

I only can suppose about figure '10' from parameters for DESC. I changed it for 'Promoted items:' on pages '/node/*/edit' (create or edit node of Feed and/or lightweight-Feed). I have noticed a bug in some hours after changes.

But now I shall try to repeat it and to make experiment with my step-by-step backups...

Thanks.

Serg

Poznii’s picture

I managed to repeat this bug. FeedAPI works perfectly. The bug appears after the first sorting a feed by the module feedapi_mapper (5.x-1.0-beta4) by cron. Cron has carried out the feedapimapper-task without bugs. But bug appears on page feed-item/* after that. It is:

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 'DESC LIMIT 0, 10' at line 1 query: SELECT node.nid, feedapi_node_item.nid, feedapi_node_item.timestamp AS feedapi_node_item_timestamp, created FROM rss_drupal_node node LEFT JOIN rss_drupal_feedapi_node_item feedapi_node_item ON node.nid = feedapi_node_item.nid WHERE (feedapi_node_item.feed_nid = 81) ORDER BY feedapi_node_item_timestamp DESC, DESC LIMIT 0, 10 in /var/home/....../public_http/includes/database.vbulletin.inc on line 164.

After disabled feedapi_mapper, the bug disappear.

alex_b’s picture

That's strange. The query actually looks like generated by views.

Poznii’s picture

maybe any overlap of variable, which joins after performance of maping?

aron novak’s picture

Project: FeedAPI » Feed Element Mapper
Assigned: aron novak » Unassigned

I move to Feed Element Mapper, because FeedAPI side seems to be ok.

davecormier’s picture

Hey folks,

If I'm right... this is happening when variables that are being called in a given view no longer exist in the drupal structure. So, if, for instance, you've deleted a content type or a field, and it is called in a view... Something that happens during the upgrade pings this and returns this error. I've had it happen several times, and I think that's it.

maybe.

alex_b’s picture

- Dave: if your assumption is correct, this issue wouldn't be FeedAPI related?

alex_b’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

No response.