• eddyj

    (@eddyj)


    Im using a theme that puts posts online with a date of expiry, upon hitting that day ( 30 days ) they are marked Expired but remain viewable to the general public

    Then to get them to disappear from the blog so they arent viewable to the public the theme has created a cron job that would check every hour the posts and if it finds one that says EXPIRED it puts it back into draft ( no longer viewable to public )

    Now my question to them was.. why do you need a cron job to hit your site every hour checking for posts marked expired as that is a lot of cron job hammering that web hosts might not like

    When you could just have it coded in to have it turn back into a draft upon the date it is set to expire

    They said wordpress doesnt allow that.. they said this

    ” Yes, ideally that’s how it should work and what I was initially trying to do, however I wasn’t able to get it working in time for 3.0.

    Believe it or not, WordPress doesn’t have a true cron scheduler so you can’t auto expire posts unless someone hits a page on your site first. So no matter what, a page needs to be loaded before the WP cron actually kicks off which is how plugins like Post Expirator and WP-DB Backup do it is.”

    SO question is.. is this TRUE??

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Calling all WordPress Experts – Is this True?’ is closed to new replies.