Closed (fixed)
Project:
Feeds
Version:
6.x-1.0-alpha2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Oct 2009 at 02:17 UTC
Updated:
30 Jan 2014 at 03:17 UTC
Jump to comment: Most recent
I have the Cron feature enabled in Aegir to periodically execute cron on my hosted sites.
When cron runs against my ManagingNews site (build about 3 or 4 hours ago from the DRUPAL-6--1 branch of the install profile), I get a PHP Notice output from the cron run:
PHP Notice: XML error: Invalid character at line 227, column 30 in /opt/www/deploy/drupal-6.14_build_2009102101/profiles/managingnews/libraries/simplepie/simplepie.inc on line 1801
Comments
Comment #1
Anonymous (not verified) commentedInterspersed with this cron output is another one:
It may be related, not sure yet.
Unfortunately executing the cron command in Aegir with --debug doesn't give anything more, as the error is occuring on the other side of the execution of cron. Nothing is being logged in dblog of use either.
Note the missing variable 'could not be found at in' from
$this->feed_url looks like it's defined in the conditional block before this one based on $file
Comment #2
Anonymous (not verified) commentedA new one!
Some of these may simply be related to my specific feeds so unsure really if this is a bug.. just noisy :) i.e I haven't had the XML one for an hour and a half since I deleted some feeds that I thought might have been faulty, but I continue to get the 'feed not found' and now this one.
Comment #3
Anonymous (not verified) commentedDefinitely was related to a buggy feed of mine somewhere. I removed them all and have been adding them one by one slowly, no errors. I suspect it was a feed that wasn't playing nice with the XML. Just was never alerted to it when I had all my feeds in the core Aggregator module. So you can close this if you like, sorry.
Comment #4
alex_b commentedAre these fees supposed to parse? Care to drop me one of them (privately)?
Comment #5
ckreutz commentedThanks for the info. In my case it was a wrong RSS feed, which was redirected to a normal website. With the correct RSS/feed the error disappeared.
Comment #6
twistor commented