RSS invalid
Issue #38
open
Hi,
We use our feeds for mailchimp and they are not accpeting our feeds anymore. When running it through the validator https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fcruxnow.com%2Ffeed%2F it shows an error for the ssl.
Is this error related to the plugin or is this strictly an ssl issue? We want to rule out as many of the possibilities right now so we can narrow our search for fixing this.
Thanks!
Comments (13)
-
repo owner
-
repo owner
- changed status to resolved
Fixing Issue #38 - proper URL escaping for <enclosure>, <media:content> and <media:thumbnail> tags
→ <<cset d16823a9a10d>>
-
Interesting, thanks for the quick reply.
Yes, we're using Jetpack and it's activated on our blog.
-
repo owner
- changed status to open
reopened
-
repo owner
Issue
#39was marked as a duplicate of this issue. -
repo owner
Issue
#37was marked as a duplicate of this issue. -
repo owner
- marked as blocker
-
Hello Ladislav,
I'm the user who opened
#39and i was wondering how are you doing with the issue. Is it hard to resolve?Good luck with the development!
-
repo owner
hello, I'm still trying to reproduce the problem so I can fully fix it. I should be able to release update by the end of this week... with some luck, it may be ready later today or tomorrow. (Seems it's already fixed in some cases, but not yet with all possible configurations out there).
-
You rolled out an update 6 days ago that took care of this for me. Sorry I didn't get back sooner. Thanks!
-
repo owner
@freundorfer > no problem :) It is partially fixed, but in some cases, the bug is still there :(
-
Ah then good luck fixing it!
-
Hello Ladislav,
Again, I'm dthe user who opened
#39and I'm checking how are you doing with this issue. Did you publish any fix for it?Thank you very much
- Log in to comment
Hello, thank you for reporting the error. There are two issues with the feed. The first one is the reason that the feed is not valid.
There should be &ssl=1 instead of &ssl=1 (I think). But actually, I'm not 100% sure. I found a reference that can be related to this issue. Do you have Jetpack activated on your blog? Anyway, I should be able to fix this problem. As this tag is generated by my plugin, I should be able to check the image url and do a proper escaping if needed. This should fix the problem. I will try to update the plugin soon, but I need to find a way to test it (replicate your problem first).
I don't know what this is. Seems like some update in WP, but can't find anything related to this namespace addition to RSS feed. But this is only warning... so the feed should be ok even with this "problem".