cover photo


cron fail

 Xerta last edited: Thu, 22 Mar 2018 17:11:55 +0100  
@Feed2Red I am getting the following failure on my cron job (spelled out to make it display):

:213: parser error : PCDATA invalid Char value 4

Obviously something not escaped properly somewhere, but where can I look for further debugging (which feed for example)?
Hm, already tried to answer here, but it seems it didn't post?

Anyway, this was because seemingly in some cases, some called subroutines simply die() instead of giving back a proper error. This is covered with an eval() now, so we'll now get a proper error message by and thus information about which feed it was that it happened on.

There might be wrong error messages behind the : in such a case, though, like none at all, an error that actually happened at another feed before, or even "Success", because the XML_Feed class probably doesn't have achance to set its own error message, either.

I'll keep an eye on that.
Oh. it did. :-)

 Xerta last edited: Thu, 22 Mar 2018 17:15:24 +0100  
@Feed2Red  I'm still having difficulty with re-enabling expiration. The Content Expiration feature in my feeds channel is definitely on. I have the latest git pull of the script. Here is the DEFAULTS section of


Is perl case sensitive? The only difference from the example config is expiredays/ExpireDays, but I've not changed this. Incidentally there are a number of inconsistencies like this in the docs. Shall I don my proof-reading hat?
No. All my FEED sections are after DEFAULTS.
If it's not too private, could you create a copy of the config file(s) without your password and attach it to a private post to me? I could then install it here and see if I can reproduce it.
avatar/logo proposal

 Xerta last edited: Thu, 22 Mar 2018 18:04:39 +0100  
@Feed2Red  Can't help with the coding, but this may be useful:


Also SVG and PNG versions in my cloud:
Ah, didn't even think of that. But you're right, there might be use cases for some people. I'll add it to the git next week because here at home I don't have a simple way to transfer the files.
That's already the case, yes, at least if the URLs match (http/https and a trailing / are deemed as equal, but if someone has ?format=xml at the end and the other hasn't or something similar, these will be different feeds for Feed2Red).