WordPress Ideas » Tag: draft - Recent Posts

Cara-crossborder on "Auto expire/unpublish time for posts"

Cara-crossborder — Thu, 14 Feb 2013 14:59:51 +0000

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.

Ipstenu (Mika Epstein) on "Auto expire/unpublish time for posts"

Ipstenu (Mika Epstein) — Thu, 17 Jan 2013 07:37:45 +0000

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. :)

davidmcc3 on "Auto expire/unpublish time for posts"

davidmcc3 — Thu, 17 Jan 2013 07:10:51 +0000

Corporate denial is rife (and always has been).

Ipstenu (Mika Epstein) on "Auto expire/unpublish time for posts"

Ipstenu (Mika Epstein) — Wed, 16 Jan 2013 22:57:15 +0000

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.

davidmcc3 on "Auto expire/unpublish time for posts"

davidmcc3 — Wed, 16 Jan 2013 17:44:04 +0000

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!

Ipstenu (Mika Epstein) on "Auto expire/unpublish time for posts"

Ipstenu (Mika Epstein) — Wed, 16 Jan 2013 15:12:20 +0000

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).

http://wordpress.org/extend/plugins/content-scheduler/

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 :)

davidmcc3 on "Auto expire/unpublish time for posts"

davidmcc3 — Wed, 16 Jan 2013 11:48:24 +0000

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.

Ipstenu (Mika Epstein) on "Auto expire/unpublish time for posts"

Ipstenu (Mika Epstein) — Mon, 07 Jan 2013 18:49:17 +0000

I don't have a dog in the fight either :) I'm just trying to look at it objectively. I think this is a needed feature for less than 80% of the WP user base, and that's pretty much my benchmark for if I think we should push it. Mostly I wanted to explain that total downloads is only one measurement for 'into core use case' math.

trumpcard21 on "Auto expire/unpublish time for posts"

trumpcard21 — Mon, 07 Jan 2013 18:44:56 +0000

I understand completely, but regardless of version of WordPress or the plugins version, the total number of downloads is a benchmark of a plugins or features desirability. Its the number of people over the course of the plugins lifetime that have reached out for that functionality from the plugin as it wasnt available from the core.

I'm just debating, I have no need of this functionality any longer, but I still think it would be a useful piece of functionality that more people than you realize might appreciate based on the long term download numbers of the post expirator plug-in.

That said, I dont really have a dog in this fight anymore however. I just set up a record prune job externally to do it for me, but I still think it would make a good inclusion.

I do agree about needless feature creep. You always want to keep your core as tight as possible

Ipstenu (Mika Epstein) on "Auto expire/unpublish time for posts"

Ipstenu (Mika Epstein) — Mon, 07 Jan 2013 18:35:21 +0000

WordPress 3.5 is at 4,301,146 downloads, so percentage wise it's different. Only around 56% of people are using the latest version, and the most ever downloads on a day was under 800. The ~60k downloads is 'all users, all versions, forever' and it's really a benchmark like that.

Go look at http://wordpress.org/extend/plugins/w3-total-cache/stats/

That huge spike is when the plugin upgraded. That would be 11k in one day, and that is a way better tell for usage.