[wp-trac] [WordPress Trac] #10511: Enclosure Custom Fields are automatically deleted
WordPress Trac
wp-trac at lists.automattic.com
Thu Feb 2 16:36:06 UTC 2012
#10511: Enclosure Custom Fields are automatically deleted
--------------------------+-----------------------------
Reporter: animepulse | Owner:
Type: defect (bug) | Status: reopened
Priority: high | Milestone: Future Release
Component: Feeds | Version: 2.8
Severity: major | Resolution:
Keywords: has-patch |
--------------------------+-----------------------------
Comment (by amandato):
Re "Possible way out", would break existing podcasting plugins. You
definitely want the plugins to store episodes in the same way as WordPress
does without the plugins, otherwise you end up with the PodPress mess,
when PodPress breaks podcasts go dark because they store episodes in a
proprietary custom field. If you continue to do the auto deleting, whether
or not the enclosure is hidden or not would delete data that other plugins
have populated.
Re "Other possible way:", keep in mind that there are two popular
podcasting plugins that store the enclosure in custom post type
"enclosure" because that was what was documented as the way enclosures are
to be stored in WordPress years ago. Podcasting has gone beyond just 3
lines of data for an episode, and now uses the 4th line of the enclosure
to store a serialized array of other data. The "include an extra line"
method would have serious ramifications.
I proposed a solution, it's in the first reply to this thread 2 1/2 years
ago. Its simple fix, keeps the auto add logic for automattic's
wordpress.com podcasting support, removes the auto delete logic and also
fixes the problem of multiple enclosures, which are a no-no if you really
are podcasting.
Keep in mind how ill-thought out this auto enclose feature is. So many
bloggers (let alone podcasters) link to media files in their blog posts
without ever thinking that the media link would automatically become a
podcast episode.
The perfect solution is a new option checkbox in WordPress settings
somewhere that would by default (not checked) not do the do_enclose logic,
and when checked, would do the do_enclose logic, and limit it to only 1
media file (read my reply from 2 1/2 years ago why you can't just have an
endless number of enclosures per post).
nacin, If you're the responsible developer at WordPress.org that can fix
this, please contact me at cio [at] rawvoice.com I can save you a lot of
time and tell you what is and is not possible, as far as what would work
for the podcasting community.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10511#comment:25>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list