Podpress feed validation problem

Hi Tara,

Please, try to find out whether this post with the podcast episode has a custom field with the name “enclosure” and the URL of the media file and two further numeric values as custom field value.

You can find these custom fields in one of the boxes below the post editor of your blog.

If you set a link to media file (e.g. a MP3 file) inside the post content then WordPress is going to create such a custom field automatically and if such a custom field exists WP puts an <enclosure> tag into the Feed item. But if there is more than one <enclosure> tag in one <item> of a RSS Feed then the feed is not valid.

If there is such a custom field then you should delete it.

Regards,
Tim

Hi Tara,

if have checked this my guess with my own blog again and discovered that not the number of the <enclosure> tags per <item> is the reason why your feed is not valid. That is not nice and it is recommended to use only one <enclosure> per <item> but the bigger problem seems to be that the URL of the .mp3 file starts with https:// and not https://.

The explanation of the error message of the feedvalidator says:

“[…]If this is a link to a web page, you must include the “https://” at the beginning and immediately follow it with a valid domain name.

Otherwise, the valid values for a URL are specified by RFC 3986.
[…]”

A solution for this problem might also be deleting the custom field with the name “enclosure”. Because the “https://”-link is only in a <enclosure> tag which is not added by podPress.
You are using the statistics feature of podPress and one effect of using this feature is that podPress masks (temporarily) all the URLs of the media files have been added with podPress.

Regards,
Tim

Hi Tim

I will try removing the custom field and see if that works thank you. I don’t know how to get round using https:// as the file is on amazon S3 secure server.

I will aslo try disabling the statistics.

Thanks for your help.

Tara

Hi Tim

Removing the custom field seems to have let it validate – thanks very much. I just need to remember to do this each time now ??

I will aslo try disabling the statistics.

No, don’t do that. The statistics function masks the URLs as long as it is active, so that the URLs with https:// become URLs with https://. That is in your case helpful.

Removing the custom field seems to have let it validate – thanks very much.

I’m glad that I could help.

Ok thanks again