Auto expire/unpublish time for posts

  1. davidmcc3

    Being able to schedule posts being published and unpublished has been 'core' territory for (proper?) content management systems for at least 10 years (to my personal knowledge as a former corporate IT Director).

    While I understand the origins of the application and continue to use it enthusiastically for client sites, it's about time WordPress caught up.

    I remember years ago the car makers in the UK saying air-con wasn't available because no one wanted it. When something IS available (without it being a retrofit which may or may not work with your model/release version), it's surprising how many people find they'll use it.

    Posted: 2 years ago #
  2. Ipstenu (Mika Epstein)

    Unlike a car, WordPress makes it easy to install a feature like heated seats (which is nice to have, but not a deal breaker unless you live where it's cold).


    You have to remember, plugins are the right way to go about this. It's how we find out if that feature really is all that needed or not :)

    Posted: 2 years ago #
  3. davidmcc3

    No, plugins IS NOT the way to go for something which should be core functionality (is WordPress serious about being a CMS?)

    Plugins are/can be:

    1. not well written
    2. cause issues with other plugins, themes etc.
    3. don't always work with new versions of the core
    4. can't be relied upon to be updated
    5. could be harbouring a virus

    Authorisation workflow probably IS a minority interest for users of WordPress ('proper' CMS systems have this), but not the automatic ability to set an unpublish date ... even Joomla has it!

    Posted: 2 years ago #
  4. Ipstenu (Mika Epstein)

    WordPress is not Joomla.

    Im sorry you don't feel that using a plugin can be perfectly safe, but that is the way we encourage development. Unscheduling posts is, right now, a minority interest.

    Please have a look at http://wordpress.org/about/philosophy/ to understand how we approach these sorts of things.

    Posted: 2 years ago #
  5. davidmcc3

    Corporate denial is rife (and always has been).

    Posted: 2 years ago #
  6. Ipstenu (Mika Epstein)

    As a recovering corporate wage slave, I agree.

    But you have a bit of a misconception going on if you think WP is 'corporate.' You should read the make.wordpress.org blogs, and the IRC chats. :)

    Posted: 2 years ago #
  7. Cara-crossborder

    I agree with the above commenters - unpublish functionality is basic CMS stuff. There are often times when a post is time-limited e.g. job adverts, special offers etc. and with WP you have to remember to go back to each post and delete instead of an automated unpublish by date function to remove it from the public site. Fair enough for blogging software, but if you want to call yourself a CMS, then at least provide basic CMS functionality.

    Sloppy of you to insist we rely on plug-ins for this, when experience has shown that plug-ins may not be updated, supported or even fixed if they fail.

    Posted: 2 years ago #
  8. johnny_canuck

    I look after several small community sites (as in non-corporate), with events, announcements and members that come and go. Functionality like this seems to be pretty basic to me. Not that it's up for voting, but here's another one for making unpublish to be part of core.

    Posted: 2 years ago #
  9. crdunst


    +1 for making it part of core. I've used one of the plugins on a few sites, but it seems to conflict with caching plugins.

    One other alternative plugin that does handle expiry doesn't handle custom post types.

    If expiry control was part of core, plugin developers, would factor that in. At the minute the conflict falls between two stools.

    No-one wants bloat, but expiry just feels like it should be in core - like someone else pointed out, you can schedule publish times, why not expiry times too.

    Posted: 1 year ago #
  10. davidmcc3

    Just started working with another client who needs expiry functionality.

    As previous poster said, using a plugin makes us too reliant on it being kept up-to-date. This is more of an issue now with the accelerated versions, both for us as users and the plugin developers.

    The number of people downloading expiry plugins doesn't represent all who would use the functionality if it was in the core - many probably delete posts manually.

    Having spent many years in corporate IT, all the CMS platforms we used/evaluated had to have expiry.

    As WP is the leading CMS and developing into a system large organisations will look at, both ways scheduling should be part of the core.

    I can't contribute to WP directly, as I've never had programing skills. I've always worked with customers/clients to help them get what they need from the IT department ... so this is the direction I'm coming from with this feature request.

    Posted: 1 year ago #

RSS feed for this topic

Reply »

You must log in to post.

  • Rating

    5 Votes
  • Status

    This is plugin territory