Closed Dovizu closed 3 years ago
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
I’m not sure I understand what is being asked here. <media:content>
is not a replacement for <img>
.
As far as I understand, <img>
is not an enclosure, so I don’t understand how the MailChimp advice is relevant here.
Could you maybe provide a bit more detail, maybe with specific examples of current behavior vs expected behavior?
Ah, since I filed this bug, I talked more with Mailchimp’s support and have realized that the problem is that Mailchimp does not support relative paths in <img>
indicated by xml:base
. So I hope Jekyll-feed will allow absolute path generation in the future.
@Dovizu Thanks for the update! That makes more sense. :+1:
I use MailChimp to convert my RSS feed into an email campaign, but images embedded in the body of a post don’t work. For example in my feed, an image shows up as
<img src="C98B12E5-9C22-48FC-B91B-E7C1F3FF2B3C.jpeg" alt="" />
Pretty standard, but when viewed in MailChimp, it doesn’t quite work.
I contacted Mailchimp customer support and they said that images must use
<media:content>
tag to show up. Quoting from this support article:Would it be possible to use
<media:content>
instead of<img>
in the generated XML file?