14
Quote:
I get the following error in XHLD (no errors in XOOPS debug):
le="color: #000000"><?php Failed saving data to database for headline Testing XmlParse error: Invalid character at line 10
Coincidentally this is the first line the native characters are displayed in the source. Perhaps an issue with the feeds encoding (iso-8859-7)?
I got that error too, but as the TS stated:
le="color: #000000"><?php I have got other feeds working with the same encoding, so I tempted to believe it is not an encoding issue.
I didn't look into it.
I assume he adapted /language/hislanguage/headlinerenderer.php or something.
Quote:
Out of curiosity, how did you see the 403 error?
I expanded the document empty error with the content. From that I learned that Snoopy is a 'good wheater' program and handles poorly the HTML status. In fact it is saved in _httprequest (but not in _httpsrequest), but nowhere checked. I think after
le="color: #000000"><?php $this->status= $status[1];
should be something like
le="color: #000000"><?php if ($this->status >= 400) { return false; }
The same should be added for _httpsrequest.
After that every call of _httprequest and _httpsrequest should check its return status and if false add an appropriate error message and propagate the false return.
Quote:
The feed validates in W3C and shows no errors in firebug.
If the site checks browser signatures, the result is different (You could eg allow Firefox and block IE).
Quote:
the forum here isn't displaying the characters correctly in the bottom code box
Despite XOOPS.org is UTF-8,
this bug is still not resolved.
