| 17 |
|
|
| 18 |
INSTALL |
INSTALL |
| 19 |
======= |
======= |
| 20 |
|
|
| 21 |
This module is not (YET at least) compatible with previous versions. So its only |
This module is not (YET at least) compatible with previous versions. So its only |
| 22 |
indicated to new sites. |
indicated to new sites. |
| 23 |
|
|
| 24 |
|
|
| 25 |
|
USAGE |
| 26 |
|
===== |
| 27 |
|
|
| 28 |
|
The first thing you shuold do is give the proper permissions: "administer node expire" |
| 29 |
|
will allow you to enable the feature on node types and put a default value. "edit |
| 30 |
|
node expire" will allow you to put the real date on nodes. |
| 31 |
|
|
| 32 |
|
Then you should go to admin/content/types and should the node type that will use |
| 33 |
|
expiration feature. Under "Workflow settings", put the default expiration date |
| 34 |
|
using PHP strtotime format. |
| 35 |
|
|
| 36 |
|
Now, all users that have "edit node expire" will be able to select a diferent |
| 37 |
|
expiration date during node creation/editing. If not, the default value will be |
| 38 |
|
used. Note that if the user edit the node, the expiration date will not change. |
| 39 |
|
|
| 40 |
|
|
| 41 |
CREDITS |
CREDITS |
| 42 |
======= |
======= |
| 43 |
|
|
| 44 |
Daryl Houston <daryl@learnhouston.com> (Original author) |
Daryl Houston <daryl@learnhouston.com> (Original author) |
| 45 |
Andrew Langland (D5-dev and D6-dev rewrite) |
Andrew Langland (D5-dev and D6-dev rewrite) |
| 46 |
Bruno Massa (D6 v2 rewrite) |
Bruno Massa (D6 v2 rewrite) |