Cron Producing Errors
For the past week (or so), the News feeds have not been updating automatically (as they used to). When manually running cron, it produces the following error:
The website encountered an unexpected error. Please try again later.
Updated by Lippe Lippe 9 months ago
From the logs/watchdog, I'm seeing:
PDOException: SQLSTATE: String data, right truncated: 1406 Data too long for column 'link' [...] Array ( [:db_insert_placeholder_0] => Occupy Activists Join Social Justice Organizations to Protest the 1% at the Bohemian Grove for 2 weeks in July [...]
I flipped through the aggregator output on http://occupywallstreet.net/aggregator/sources/1 & 2 & 3, found the corresponding entry on feed #1 "News From The Occupations," (http://reader.occupy.net//public.php?op=rss&id=-1&key=0dfcda7557d87f4eca0af7e684c1812c2b6b9116)
Found the item in the feed, looked at the feed source:
<id> and <link> properties are 309 chars, link has rel & type attributes..
So it looks like the occupynashville.org feed is totally pewing the scrooch with their use of utm variables. "Campaign" should be just that, a campaign.. not the full title of each post.
This wouldn't be a problem except that there's an issue with Drupal and a 255 char limit for the datatype used to store relevant info, see discussions:
I deleted all aggregator source 1 items, and re-updated it, but it choked on the bohemian grove again, posted on July 19.
I recreated this error locally, but have had mixed results testing the other feeds. One moment I coulda sworn twitter was updating fine, and that the php error wasn't interfering with other feeds, but then my local started acting exactly like live.
I think debugging feeds can be made more tricky by the fact that feed items aren't necessarily processed by cron, but are added to a queue.
Thanks for looking into this. I'm fine with deleting the offending feed.
Seems like there is a patch for this http://drupal.org/node/218004 ?