[ANN] Scheduler extension

Ruby Apps Radiant CMS
1

Ask and you shall receive.

The Scheduler extension is now available from:

http://dev.radiantcms.org/svn/radiant/trunk/extensions/scheduler

Its primary job is to create publish and expiration dates (or
appearance and disappearance) that are configurable by the content
editor. These may be set in the “meta” area of the page editing
screen, and include a calendar-style date picker, thanks to Dan W.'s
wonderful LowPro library (and his date_selector behavior). These
dates only affect what may be found from the ‘live’ site. All pages
are accessible when in ‘dev’ or ‘preview’ mode.

Unfortunately, the extension does not affect iteration over children,
etc. I will probably fix this limitation this week, as it affects a
great many usage patterns in Radiant for generating navigation, etc.
In the meantime, enjoy the extension. Here’s a quick installation
tutorial

  1. Use subversion to checkout or export the above URL into
    vendor/extensions of your Radiant project.
  2. Run ‘rake production db:migrate:extensions
    radiant:extensions:scheduler:update’ (substitute development if you
    are using that env)
  3. (Re)start your server.
  4. If you want to run the extension tests, make sure to run ‘rake
    db:test:prepare’ before you begin.

Cheers!

Sean

2

Thanks, Sean!

Would you mind dropping this into the README for the extension?
It seems like half the extensions out there say “Description goes
here” and I always appreciate the details with the extension itself.

3

No problem.

Sean

4

Unfortunately, the extension does not affect iteration over children,
etc. I will probably fix this limitation this week, as it affects a
great many usage patterns in Radiant for generating navigation, etc.

FYI This limitation has been fixed as of r511 and r512.

Sean

5

I failed to mention it before, but I just updated the README to
reflect this… The scheduler extension requires you to install the
“shards” extension. Additionally, while it is not required, it is
recommended you freeze your instance to edge. This is primarily so
you can use the extension loading order configuration that Daniel
created. If you don’t, you will need to prefix the shards directory
with 000_ or something so it loads first.

Sean