create branch 'DRUPAL-4-4'.

Cherrypick from master 2004-11-25 09:34:35 UTC Tom Dobes <tdobes@gmail.com> '#11885 - PostgreSQL script by mousse-man':
    scheduler.pgsql

table prefixing fixes and removing the scheduler info after action is performed (so it will not pop up anymore and does not pullute the DB)

adhere to coding standards, plus improve readability and SQL security (by using the built-in sprintf possibility of db_query)

- table(...) -> theme("table", ...")

system, new menu), and fix a typo.

to the scheduler admin table

  really no reason to add a new permission for this module
  (tested the possible scenarios).

- Update the module to have a user friendly interface for
  date setting (no more dependency on Engish date strings)

- Add myself to Authors in INSTALL

changes) and the improvements in this module

scenario: every user (even anonymous) is alloved to
suggest a node, but they are not alloved to set a schedule
for it (only admins).

  a publishing date (so she really would not like to publish the
  stuff yet)
- Provide one more example date
- Use real English date/times when putting the date back to
  the input field, strtotime() only understands that

new admin menu structure. Also return the table instead
of printing it, so it will work with the new integrated admin.

care of the fact that date formats should not be translated)

removed 'Mozilla' text from INSTALL and updated the _cron() queries for the new system. I forgot to update those from Marco's module. _cron() functionality is untested

This module adds scheduled publish/unpublish capability to Drupal. Specifically, 2 select menus are added to node forms for automatically publishing or unpublishing a node at some  future date. The actual publish/unpublish operation is handled by Drupal's cron hook.

An admin page (admin/node/scheduler) is added under the 'content management' tree. This page informs admins on all schedules.