WordPress.org

Ready to get started?Download WordPress

Forums

How do I take out an enclosure? (29 posts)

  1. allthewhile
    Member
    Posted 9 years ago #

    I don't want an enclosure pointing to a video file. How do I remove the enclosure element. When I hit delete, it doesn't do anything.

  2. Lorelle
    Member
    Posted 9 years ago #

    Is this something on your site? How did it get there? Is it in a Theme or in one of your posts? If it is in a post, from the admin panel, MANAGE > POSTS and find the post, click EDIT and find the enclosure and delete it.

    If it is in your php template files or the theme, that's a bigger issue, but I don't know of anyone who has yet put a video file inside of a Theme template....that would be a first.

    So can you be more specific? I looked at your site and found a lot of links to audio and mp3 and such, but didn't spot a video reference.

  3. roland_ob1
    Member
    Posted 9 years ago #

    I'm having this problem too, after linking to a .mov file. I didn't even know wtf was going on until I googled "wordpress enclosure quicktime". This link was helpful for explaining what was happening, but I don't really care what happens in my RSS feeds (not sure anyone even uses them) but what I do want to do is remove the bit it automatically adds to the end of my post:
    enclosure: http://blahblah/blah.mov 41509080 video/quicktime
    I have the same issue as allthetime - I can't delete the custom field that WP adds the enclosure as.
    I understand what's happening, and what WordPress is doing, but is it necessary to add this (useless imo) info to the actual post as well as the RSS feed? There doesn't seem to be any option to turn it off, but if someone wants to point me to the right file I'll see if I can hack it to stop it displaying.

    And Lorelle - it's not part of the site or a Theme, it's a built-in function of WP.

  4. timbearcub
    Member
    Posted 9 years ago #

    hmm bit a major bug deleting unwanted enclosures - just upgraded from 1.5 nightly (not sure which one - early Feb, 02 or 03 I think?) to 1.5 proper - you can't delete enclosures from a Published post. You have to goto draft first. But then when you publish they come back again.... aaargh!

    You get the message 'Custom Field Deleted' while trying to delete enclosures from a published post, but they don't go away and stay in the feed and on the page...

    For your information you could at least delete Published enclosures in my 1.5 nightly - just switched back and yes it does still work.

    Also is there anyway you can restrict or limit the types of enclosures being automatically created?

    I put a MP3 on a new line but also have anchor links to other media in the copy- WordPress is still (in this latest version) making several of them enclosures, even when the link is only in the href, not in the body of the page.

    hmm....rather than piss everyone off by leeching their bandwidth by RSS feeding other people's files I've had to switch back...for the *second* time! :-(

    I've had less trouble with the 1.5 Nightlies (RIP) than upgrading to the new version...:-( But I won't get support if I don't upgrade, but to be honest my nightly seems much more stable than the full version and does everything I want to do...the only reason I've tried to upgrade unsucessfully twice is the 'no support' thing.

    Oh well...least I saw more than a white page this time :-¦

  5. allthewhile
    Member
    Posted 9 years ago #

    What is the formal way to get help around here? 1 billion wordpress downloads, no support. I'm sure I'll get flamed for complaining, but this is the second time I've tried to seek help and was either ignored or rudely told to post the bug on some other site.

    Good game.

  6. lstelie
    Member
    Posted 9 years ago #

    I don't want an enclosure pointing to a video file. How do I remove the enclosure element. When I hit delete, it doesn't do anything.

    hello,

    It's not a bug it's a feature :-)
    Someone looking at your site using a RSS reader that supports enclosures, will be able to get the file directly without needing to go to the site, read yet again the text (he read it in the rss reader, and read it twice on the web) download it and so on.

    The enclosure RSS tag is harmless for those who doesn't need it and of a great feature for those who need it

    my two euro-cents

    Luc

  7. timbearcub
    Member
    Posted 9 years ago #

    It's not a feature when you're leeching other people's bandwidth accidentally because WP is adding enclosures to any linked media in your post?

    I don't want to kill people's bandwidth constraints because I can't delete an enclosure...still having problems with this, and using the gamma version because to be honest the proper version*doesn't work properly*

    It's not a feature, it's a bug that you can't delete enclosures! Otherwise why is there a 'Delete' button in the first place?

    Unless WP want to create the ability to have separate feeds according to category for me? I doubt those subscribing to my podcast really want to download everything I ever post...

  8. iand
    Member
    Posted 9 years ago #

    Unless WP want to create the ability to have separate feeds according to category for me? I doubt those subscribing to my podcast really want to download everything I ever post...
    Something along the lines of: http://www.mutantpop.net/radioclash/feed/?category_name=Podcasts

  9. timbearcub
    Member
    Posted 9 years ago #

    oops sorry I didn't know it could do that!

    thanks! :-D

    sadly won't get over the deleting enclosures issue unless I create podcasts with show notes with no other links....:-(

    But really cool it ca do that :-)

  10. timbearcub
    Member
    Posted 9 years ago #

    As you can see in the other thread this is still an issue for me and others and still no response.

    Quite a lot of the podcasting community chose WordPress to podcast from, a few in part from my personal recommendation.

    I can't recommend WordPress anymore because not being able to delete the automatically generated multiple enclosures is a major issue, and podcasting clients will just ignore the feed or ignore the extra files, probably ignoring your podcast.

    A month later and I hear nothing - and sadly I think the podcasting community using WP will go elsewhere eventually. I'm quite disgusted at the lack of support, even for a free product.

    Developers used to post here before Strayhorn's lauch...even a short one line post of 'we're looking at it' or 'we wont fix this' will let us know what to do next.

    I'm patient, have been for a month since this was raised...but I'm starting to lose patience.

  11. asianmack
    Member
    Posted 9 years ago #

    I second timbearcubs' concerns. I constructed a post with multiple links out to various mp3 files and WordPress is creating multiple enclosures in my RSS 2.0 file resulting in an Invalid file. This RSS file should be valid and WordPress should not be automatically generating enclosures for each mp3 link. Does anyone have any fixes so that my RSS feed can come alive again?

  12. timbearcub
    Member
    Posted 9 years ago #

    you still can't take out an enclosure in 1.5.1.2. You click the delete button and it just doesn't do it - so another 'downgrade' to my unsupported nightly. Sigh.

    So do I need to find a better podcasting platform? Web Application of the Year don't make me laugh...

    a disappointed ex-fan.

  13. Matt Mullenweg
    Troublemaker
    Posted 9 years ago #

    If you send us a list of podcasting clients that are broken we'll work with the authors.

  14. wnmurray
    Member
    Posted 9 years ago #

    No! PLEASE just tell us how to delete the unwanted enclosure tags, or disable the enclosure feature altogether so we can hand-code it into our posts or something.

    It's a widespread standard for enclosures that only one should be allowed per post; for those of us who wish to comply with this standard, so our blogs can be properly syndicated, please fix.

    Right now, I generally get two enclosure tags added by WordPress to each post but I only want one (for the first movie file in the post, the hi-res and the lo-res versions). When I delete the second enclosure, it refreshes and I end up with THREE, ie the second one and a duplicate of it.

    Waz
    http://www.crashtestkitchen.com

  15. wnmurray
    Member
    Posted 9 years ago #

    Sorry, to clarify, I have two movie files in each post, a hi-res first and then a lo-res one, and I only want the hi-res to go out in the feed. The lo-res one is for dialup visitors to the site.

    WordPress is attracting some negative comment in the video blogging and podcast communities because of this problem, so I hope the developers will take note and rectify.

    Waz
    http://www.crashtestkitchen.com

  16. wnmurray
    Member
    Posted 9 years ago #

    A common-sense suggestion was made here:

    http://wordpress.org/support/topic/28375#post-198391

    Can someone come up with a PHP hack that will mean only links that include rel="enclosure" are turned into RSS enclosures by WordPress?

    The hack would only have to be implemented by those who want it ...

    Waz

  17. timbearcub
    Member
    Posted 9 years ago #

    It's not the podcasting platforms which are broken; some work, some don't. I just want control of which file links *I* include in *my* feed.

    Is that so hard?

    Although if you really want to talk to a developer rather than a lowly user, you can go and speak to Dave Winer of audio.weblogs.com http://blogs.law.harvard.edu/dave/ - audioblogs doesn't work with more than one enclosure; as he came up with RSS enclosures he might know whether they should have 1 or more for podcasting?

    I can guess his reponse tho; I think podcatcher.com or the old iPodder.org has an interesting FAQ about it where it says podcatching clients shouldn't download more than 1 enclosure...if they do it's something else...there was a big argument about it last year. But I don't know if anyone decided whether it should be single or multiple; hence the confusion I expect.

    But just because you CAN include multiple enclosures doesn't mean you WANT to or CHOOSE to.

    Anyway if you're NOT supposed to delete an enclosure; why does it have a bloody big DELETE button next to it? That when pressed, doesn't work?

    Very hitchhikers - you really should have a sign saying 'please do not press this button again!' appear when you do...

  18. greeley
    Member
    Posted 9 years ago #

    This seems to be related to an issue I'm having. I had to host a couple of mp3 files elsewhere because we hit a demand spike and my ISP couldn't keep up. When I change the URL of the mp3 file in the post, the corresponding URL in the "enclosure" field doesn't change. When I make the change in the enclosure field, the change doesn't take, that is, it isn't reflected in the RSS feed.

    Essentially, once you include an enclosure in a post, that's it; no changes can be made. I suppose I could go into the database and make the change, but I don't really want to muck around there, and in any case it seems a little inefficient. This is a HUGE issue for podcasting, and it's definitely not a problem to be solved by talking to the podcatching clients.

    Thanks in advance for any insight -

  19. andper
    Member
    Posted 9 years ago #

    Well, if any of you are like me and don't want the "enclosure" feature *at all*, here's an amateur solution.

    All you have to do is open your wp-includes/functions.php file and take a look at line no. 766. There's a preg_match_all function which is responsible for "discovering" the audio or video file(s) linked in your post. You have to "break" that function somehow, for instance, add an additional "p" after "http" so it'll read "httpp".

    Now WP won't find any of your media files linked in your post anymore, nor will it include them in your blog's feed, plus the delete button for the "enclosure" custom field in the administration panel will automagically start working.

    Hope it helps, at least until someone comes up with a more profound solution. :)

  20. alastair
    Member
    Posted 9 years ago #

    Can I add my voice to those who think this feature is a Bad Idea, or at least not well thought through. I highly recommend that this feature be removed (or at least disabled by default) ASAP.

    Here is my reasoning. Some RSS clients like NetNewsWire (which BTW is NOT a specific podcasting client) can be configured to download enclosures automatically. This is a feature, and a good one IMHO.

    So wordpress users that are unaware of this feature and unintentionally link to someone else's media file may be triggering all their subscribers to automatically download that file.

    Matt, you will have a hard time talking to the client authors trying to convince them to turn off the automatic enclosure downloads in order to prevent accidental bandwidth leaching like this.

    I realise that wordpress is trying to help me here, but at a conceptual level I don't see how linking to an audio or video file should automatically imply that you want to include it as an enclosure. The suggestion in the other thread to only enable this feature when a specific attribute in the link (I think rel="enclosure" was suggested) sounds like a great idea to me.

    In the meantime there needs to be a way to disable this feature (besides the hack mentioned by andper above).

  21. scruffy
    Member
    Posted 9 years ago #

    I just want to add my vote for disabling this "feature." I can only second (or third, or fourth...) the concerns about breaking standards, causing major inconvenience for those who don't want the feature, unnecessarily increasing bandwidth loads for others, and forcing downloads for several readers.

    There seems to be many valid arguments for disabling the feature or altering it, and I have yet to read anything which supports keeping it in as is.

    Wouldn't it make more sense to have a "Include File as Enclosure" field in the advanced editing options?

    People could just put the URL to the file they want in that field.

    For anyone thinking that a free and open product like WP doesn't deserve a particular level of support consider this: When you link to and recommend WP, you send traffic to this site. When you do that, you are also increasing the potential number of people clicking through to the various affiliate programs, as well as garnering attention for the developer.

    Lack of support or response to this issue is not something that should be written off as something which should be expected because beggars can't be choosers.

  22. Joshua Sigar
    Member
    Posted 9 years ago #

    I heard there's gonna be more hooks/filters for RSS for the next release; so, expect a plugin solution sometime.

  23. scruffy
    Member
    Posted 9 years ago #

    Here's an interesting solution this.

    I'm making an MP3 blog, and I'm wanting to link to about three mp3s per day. I'm also going to be doing a podcast, so i'm still going to want to have an enclosure on particular posts.

    What I've figured out, is that if you implement andper's hack above (I actually added 2 "p"s (so it reads httppp) just to be safe), you can then *manually* enter an enclosure by adding it as a custom field. Simply add 'enclosure' as the key (It may already be in the drop-down menu) and the URI of the podcast file in the value field.

    Seems to work great.

  24. vsa
    Member
    Posted 9 years ago #

    thanks to andper for his solution.
    I hope someone works this issue out in a professional way though...

  25. oconnor
    Member
    Posted 9 years ago #

    Ah! This "multiple enclosures, can't delete 'em" problem also breaks Feedburner feeds quite nicely. Thanks to andper for your hack -- and I'll also lend my voice to the "this should get fixed" chorus. If you're doing multiple MP3 links in your posts, you should definintely "break" this function.

  26. Kyle Gilman
    Member
    Posted 8 years ago #

    I just got started with WordPress yesterday and I'm very impressed with it so far. But I'm developing a video blog and I quickly ran up against this problem of multiple enclosures. Rather than breaking the thing altogether, I added a "break;" in the do_enclosure function after line 790 in wp-includes/functions.php so it looks like this:

    $wpdb->query( "INSERT INTO '$wpdb->postmeta' ( 'post_id' , 'meta_key' , 'meta_value' )
    VALUES ( '$post_ID', 'enclosure' , '$meta_value')" );
    break;
    }

    That forces the function to exit after creating the first enclosure. Unfortunately you still can't delete that first enclosure because the function is run every time you publish the post, which re-creates the enclosure you just deleted. You also can't choose which enclosure you want to use. You're stuck with the first media link in the post. I'm going to work on a plugin to give some flexibility to this process, but it could be a while since I don't really know what I'm doing.

  27. Kyle Gilman
    Member
    Posted 8 years ago #

    update: In 2.0 add the break; after line number 1044

  28. Kyle Gilman
    Member
    Posted 8 years ago #

    Another update. I actually wrote a plugin to deal with enclosures. http://www.15framespersecond.com/enclosureflex/

  29. kri
    Member
    Posted 8 years ago #

    I must agree with the general consensus here. This was a badly implemented feature, and something that should be more easily turned off. This is not something that should automatically happen whether I want it to or not, and I should be able to turn it off in the WordPress options.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags