Currently episodes coming from CMS Stories will have their content attribute set to the same as the description. This is then rendered into the feed as <content:encoded>.
But when a show moves to the Feeder UI, the ep.content field gets stuck into a stale/old state. This PR just nils out the field, so the <content:encoded> tag disappears. Which shouldn't be a problem - it's only present on full episodes, and basically always redundant with <description>.
Similar to #956.
Currently episodes coming from CMS Stories will have their content attribute set to the same as the description. This is then rendered into the feed as
<content:encoded>.But when a show moves to the Feeder UI, the
ep.contentfield gets stuck into a stale/old state. This PR just nils out the field, so the<content:encoded>tag disappears. Which shouldn't be a problem - it's only present on full episodes, and basically always redundant with<description>.