Posted 2 years ago #
I had 8.8.10.3 of podpress and was getting feed errors so I went to the development version last night. I saw this morning there was an update release of 8.8.10.4 and so I installed it. Feed errors returned.
Error I get is
This page contains the following errors:
error on line 217 at column 271: CharRef: invalid decimal value
Below is a rendering of the page up to the first error.I went back to development version and it's working again. Thought I should report this.
Hi Terry,
Thank you for the report!!
Which Development Version do you use? Until some minutes ago the Dev version was the same as 8.8.10.4.
Is it possible that this error has not occurred in a line with a <itunes:category>?
It would maybe helpful to see the line of the XML code which includes the error.
The error message that you have received seems to point to a different problem than the problem which was report for 8.8.10.3.
I really like to find out what has caused this error.
The current Development Version (8.8.10.5 beta 1) includes again some lines which I have deleted in 8.8.10.4.
I would appreciate it, if you could install this version or if you could tell me more about the faulty XML code or if you could post the link to your podcast (so that I can take look what is in line 217 of the code of your RSS feed).
Thanks,
Tim
Posted 2 years ago #
My player has totally disappeared. I have the same "type" player on another site I access that works but it is gone on this 8.8.10.4 ver. on the one I manage with podpress.
Hi Terry,
please, switch to 8.8.10.6.
Regards,
Tim
Posted 2 years ago #
I upgraded from 8.8.10.3 to 8.8.10.6 and it broke my feed with the same error, I reverted back to 8.8.10.3 and it worked agin
@LucaTNT: It would be great if you could try the current Development Version (8.8.10.7 beta 4). I have revisited the faulty function once more and it works better than the one in .10.6.
In case that version does also not work, please copy and paste the error message from the validator and some lines above and below the line of the XML source code of the feed with the error. Maybe use a pastebin service to post the whole source code.
Regards,
Tim
Posted 1 year ago #
@ntm Sadly I cannot risk to break my feed now, sorry. I will try ASAP
Yesterday, I have had help of an other beta tester and could resolved most likely the last problem in the new feed function. 8.8.10.7 will probably come out this weekend.
You may wait for that version.
But it would be great if I could see the error messages you mentioned above. Maybe I would discover a problem which I have not thought about yet.
Posted 1 year ago #
Ok, I tested everything I could, here are my results:
Version 8.8.10.6
Feed: http://pastebin.com/4G2p9WED
Chrome's error loading the feed:
This page contains the following errors:
error on line 1256 at column 271: xmlParseEntityRef: no name
Below is a rendering of the page up to the first error.Version 8.8.10.7
Feed: http://pastebin.com/GiLxuP0W
Chrome showed the same error.
As you can see in the feed, I use WP SuperCache, but I deleted the cache to get the correct feed for each version. I also tried to disable feed caching and the whole plugin - same results.
This is the working feed from podPress 8.8.10.3: http://pastebin.com/mxMagpQG
If you need it, here is the feed's URL: http://www.easyapple.org/feed/podcast
Is the code in the pastebins copied from source code view of the feed in your browser? Or have you have mixed up the pastebin links.
I'm asking because the code in 8.8.10.6 pastebin seems to be the code from 8.8.10.7 and the other one is most likely from 8.8.10.6. If e.g. a itunes:subtitle gets cut in 8.8.10.7 then the abbrevation sign is "[...]" and no longer only "...".
The code in this pastebin http://pastebin.com/4G2p9WED (which is probably from 8.8.10.7) is valid feed code. See yourself and paste it in the direct input of the validator http://validator.w3.org/feed/#validate_by_input
I will try to find out why Chrome has a problem with that feed a little bit later.
Regards,
Tim
Posted 1 year ago #
I got the feed i posted on pastebin through using curl in a terminal window, but I might have mixed them (someday I will learn to give files meaningful names)
xmlParseEntityRef: no name is often a sign for a single ampersand character which is not part of a htmlentity like & or è.
But line 1256 does not contain such a single ampersand in none of the 3 versions (the 2 from the pastebins and your current feed).
Also I'm really not sure that message should appear for the 8.8.10.6 and the 8.8.10.7 feed.
line 1256 from http://pastebin.com/GiLxuP0W (probably 8.8.10.6):
<itunes:subtitle>L'ospite dell'ottava puntata è Paolo, blogger di JustYourApple (il nuovo AppleLAB).
line 1256 from http://pastebin.com/4G2p9WED (probably 8.8.10.7):
<itunes:subtitle>L’ospite dell’ottava puntata è Paolo, blogger di JustYourApple (il nuovo AppleLAB).
line 1256 in your current feed:
<itunes:subtitle>L'ospite dell'ottava puntata è Paolo, blogger di JustYourApple (il nuovo AppleLAB).
In the current version none of the special characters are transformed into their numeric entities. That is okay. But it should also be okay to transform them into the numeric entities (see iTunes Podcasting Resources sub section "Using HTML Named Character Entities.")
In the feed produced with 8.8.10.6 only the small e with the grave is transformed. Shouldn't the column number in the error message be different compared to the column number in the message regarding the feed produced with 8.8.10.7 if the transformation of these characters should be the problem?
Or did you insert this character via an unusual way?
I have copied and pasted the line from the source code of your current feed into one of my test posts "undeuxoutrois.de/wp/2011/03/22/episode-with-a-whitespace-in-the-filename/" to see how it looks in my RSS feed. I have also tried to reproduce the error message with Chrome.
But in my RSS feed the e is not transformed and my version of Chrome has no problems with the feed.
Furthermore the feed is still valid as the XML code of http://pastebin.com/4G2p9WED (which was probably produced with 8.8.10.7)
The questions for me are now: Why is the e transformed into the numeric entity in your RSS feed?
and
Was the error message really the same for both the feeds from the pastebins? Or was only the line number the same?
I have made a further test in which I have inserted the latin small e with grave plain and as its numeric htmlentity into the feed. The Chrome on my computer (Chromium 11.0.696.68 as part of Ubuntu 10.10) had no problems with both versions and both times the feed was valid.
That is why I think that the numeric entities are not the problem. The not-transformed plain character is not the problem either.
But the question remains: Was the error message really the same for both the feeds from the pastebins? Or was only the line number the same?
Please, try 8.8.10.7 again. Clear the browser cache before you reload the feed. Maybe update Chrome. Validate your feed with the feed validator http://validator.w3.org/feed/
Posted 1 year ago #
Ok, I set up a test environment: http://test.easyapple.org/
It is completely separated from the main site (duplicated files & db), so I'm able to test freely without risking to break the main site. Also, I completely disabled WP-SuperCache to avoid cache-related issues.
I got each feed that I uploaded to pastebin through CURL, and I added a random ?something after the feed URL to prevent Chrome's (version 12.0.742.60) caching
I did not enter the data in any non-standard way: I always used WordPress' and podPress' forms to enter everything
Version 8.8.10.6
INVALID feed shown by w3c's validator:
This feed does not validate.
line 1263, column 93: XML parsing error: <unknown>:1263:93: not well-formed (invalid token) [help]
... tà di vincere una copia di 2Do, pi&...</itunes:subtitle>ERROR from Chrome
error on line 1256 at column 271: xmlParseEntityRef: no name
NOT WORKING with iTunes 10.2.2
Feed: http://pastebin.com/ziim8vuV
Version 8.8.10.7
VALID feed from w3c's validator (not even a warning, I got 2 with 8.8.10.6)
NO ERROR from Chrome
WORKING with iTunes 10.2.2
Feed: http://pastebin.com/P8M1kxGN
I hope I did not forget to test anything. If I did, let me know, I'll try it ASAP.
Thank you for all that work. It helps me to figure out the problem.
The last results are consistent. The error message from the feed validator shows it. In 8.8.10.6 (http://pastebin.com/ziim8vuV) the function which limits the number of characters of the itunes:subtitle and itunes:summary did not respect html entities (the numeric entity of è is è). The function did cut those entities in half like in the error message of the validator. There you can see that the last character in front of the ... is an ampersand. But this character is only as part of a complete html entity allowed in XML (something like &... is not allowed).
The error message from Chrome points to the same issue. xmlParseEntityRef: no name means there is a single ampersand nearby. The line number is maybe different because it does not count the empty lines.
I have enhanced the function which limits the number of characters and something like this will not happen any-more.
Version 8.8.10.7
VALID feed from w3c's validator (not even a warning, I got 2 with 8.8.10.6)
NO ERROR from Chrome
WORKING with iTunes 10.2.2
Feed: http://pastebin.com/P8M1kxGN
That result confirms that the bug is fixed in 8.8.10.7.
I'm hoping that I could explain what has happened. Your tests and posting the source code of the feed produced by the different podPress version has helped a lot.
Regards,
Tim
Posted 1 year ago #
I'm very happy I could help you.
That bug reminds me of a script I wrote to cut the first characters of an article, which looked for the end of the word (i.e. it went a little over the limit looking for a blank space). Guess what happened when the article was long exactly what was needed to have my limit in the middle of the last word: the script entered a loop and killed the server, I went crazy to track that down.
If you ever need any other testing on anything just ask, as it's the least I can do to thank you for the awesome work, since at the moment I cannot donate :(
If you ever need any other testing on anything just ask
Thank you for the offer!! It would be great if you could test the beta version (or the RC version) next time. I will probably make an announcement via Twitter when there is something new to test.
Thanks again,
Tim
Posted 1 year ago #
Sure, just followed you on Twitter, I hope not to miss the tweet ;)
I can contact you via your blog too.
This topic has been closed to new replies.
