Page 1 of 3

[podcasting] invalid token

Posted: Mon Mar 26, 2012 6:33 am
by Lux
Hi!

Any ideas what that means?

http://feedvalidator.org/check.cgi?url= ... 2Fatom.xml

XML parsing error: <unknown>:49:64: not well-formed (invalid token)

Thanks for any hint

Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 10:20 am
by Timbalu
I would say the validator script is not God! ;-)
But I also would try to use <audio controls="controls" preload="none"> instead.

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 10:25 am
by Lux
Timbalu wrote:I would say the validator script is not God! ;-)
Agreed, but the guy writing Instacast for iOS mentioned that there are erros in the feed.
Timbalu wrote:But I also would try to use <audio controls="controls" preload="none"> instead.
This brings even more errors and warnings.

Cheers

Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 10:50 am
by Timbalu
Try to move things around between line 49 and 64. Maybe the closing audio tag and or the p tags...

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 11:01 am
by Lux
Timbalu wrote:Try to move things around between line 49 and 64. Maybe the closing audio tag and or the p tags...
How?

This is copied from the plaintext of the article:

Code: Select all

<a href="http://archiv.radiotux.de/sendungen/radiotux/2012-02-29.RadioTux.Magazin.Februar2012.mp3">Februar-Sendung MP3</a>
<a href="http://archiv.radiotux.de/sendungen/radiotux/2012-02-29.RadioTux.Magazin.Februar2012.ogg">Februar-Sendung Ogg</a>
Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 12:06 pm
by Timbalu
Try to disable the nl2p for audio tags or for the full entry (or use the extended instead).

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 12:54 pm
by Lux
Timbalu wrote:Try to disable the nl2p for audio tags or for the full entry (or use the extended instead).
Does not work either.

Audio can not be moved to extended, because the files have to appear in the feed.

Cheers

Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 1:15 pm
by Timbalu
Not the extended entry part, the extended nl2br plugin...2.x

Did you really disable the nl2p plugin for this entry?

I think you need to get rid of the p class=break things here, to validate, e.g.

Code: Select all

<audio controls="controls" preload="none">
  <source src="/archiv.radiotux.de/sendungen/radiotux/2012-02-29.RadioTux.Magazin.Februar2012.ogg" type="audio/ogg" />
  <source src="/archiv.radiotux.de/sendungen/radiotux/2012-02-29.RadioTux.Magazin.Februar2012.mp3" type="audio/mpeg" />
  Your browser does not support the audio element.
</audio>
    <a href="http://archiv.radiotux.de/sendungen/radiotux/2012-02-29.RadioTux.Magazin.Februar2012.mp3">Februar-Sendung MP3</a><br />
    <a href="http://archiv.radiotux.de/sendungen/radiotux/2012-02-29.RadioTux.Magazin.Februar2012.ogg">Februar-Sendung Ogg</a>
 

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 1:19 pm
by Lux
Timbalu wrote:Not the extended entry part, the extended nl2br plugin...2.x
I can not find it on Spartacus.
Timbalu wrote:Did you really disable the nl2p plugin for this entry?
No, only for audio and source tags. There are around 2000 articles that use the plugin, I can not disable it completely.

Cheers

Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 1:37 pm
by Timbalu
Lux wrote:I can not find it on Spartacus.
Well its not there, as delivered by core. You will find it in 1.7, but you have way to much entries to allow a change...
Lux wrote:
Timbalu wrote:Did you really disable the nl2p plugin for this entry?
No, only for audio and source tags. There are around 2000 articles that use the plugin, I can not disable it completely.
But if you use the entryproperties plugin you will become the ability to disable certain markup plugins by entry. Try that.

Your entry still seems to have <source> <a href> <source> <a href> maybe this has to be written like in my example...

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 1:57 pm
by Lux
Timbalu wrote:Well its not there, as delivered by core. You will find it in 1.7, but you have way to much entries to allow a change...
Ok.
Timbalu wrote:But if you use the entryproperties plugin you will become the ability to disable certain markup plugins by entry. Try that.
Done and no change ...
Timbalu wrote:Your entry still seems to have <source> <a href> <source> <a href> maybe this has to be written like in my example...
This is done by the Podcasting Plugin.

Cheers

Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 1:59 pm
by onli
Agreed, but the guy writing Instacast for iOS mentioned that there are erros in the feed.
Prevent they anything?

The invalid-token error points not to nl2p/nl2br, but to preload="none". If that is a valid token, there is no error and the validator is wrong (probably don't know that one). Or he chokes at the controls.

For testing, you could disable nl2br only for that entry via the extended property plugin, with the controls under the entry-editor.

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 2:01 pm
by garvinhicking
Hi!

Quite interesting, the "p" of "preload" seems differently colored in my editor. It seems that some hidden, invalid character appears there...

Check your podcastplayer configuration, there edit the "preload='none'" and re-type it again from scratch with a keyboard, no copy+paste.

After that, you first need to publish a new entry to make sure that your browser displays the most recent atom.xml, and nothing cached from the server.

Regards,
Garvin

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 2:25 pm
by Lux
onli wrote:Prevent they anything?
We already removed some errors, which prevented Instacast from downloading.
onli wrote:For testing, you could disable nl2br only for that entry via the extended property plugin, with the controls under the entry-editor.
Did that.

Cheers

Dirk

Re: [podcasting] invalid token

Posted: Mon Mar 26, 2012 2:27 pm
by Lux
garvinhicking wrote:Check your podcastplayer configuration, there edit the "preload='none'" and re-type it again from scratch with a keyboard, no copy+paste.
Did it, no change.
garvinhicking wrote:After that, you first need to publish a new entry to make sure that your browser displays the most recent atom.xml, and nothing cached from the server.
Even removing all tags did not solve the problem.

Cheers

Dirk