#30993 GHengeveld:

I've just implemented a 5-phase page state sequence. A page can now have one of the following statuses:

1. Draft (work-in-progress, not visible in validation queue)
2. Pending (visible in validation queue)
3. Approved (validated by moderator but the page_begin time isn't reached yet)
4. Published (validated and active)
5. Expired (validated, but page_expire has passed)

When adding or editing a page you now have the option to 'Save as Draft' besides 'Submit for validation' (previously 'Submit') and 'Publish' (only for admins). Also, after saving as draft you're taken back to the edit screen, so you can continue working on the page.

There are 2 new page tags for status: {PAGE_STATUS} and {PAGE_LOCALSTATUS}. STATUS is the lowercase, English status string (draft, pending, approved, published, expired) while LOCALSTATUS is the localized version of it as defined in page.en.lang.php.

The system is backwards compatible with templates that use the old 'rpublish' submit button. In the new templates you should use 3 buttons with name="rpagestate" and a value of 0 (approved/published), 1 (pending) or 2 (draft).

 

1. Draft (work-in-progress, not visible in validation queue)
2. Pending (visible in validation queue)
3. Approved (validated by moderator but the page_begin time isn't reached yet)
4. Published (validated and active)
5. Expired (validated, but page_expire has passed)

When adding or editing a page you now have the option to 'Save as Draft' besides 'Submit for validation' (previously 'Submit') and 'Publish' (only for admins). Also, after saving as draft you're taken back to the edit screen, so you can continue working on the page.

There are 2 new page tags for status: {PAGE_STATUS} and {PAGE_LOCALSTATUS}. STATUS is the lowercase, English status string (draft, pending, approved, published, expired) while LOCALSTATUS is the localized version of it as defined in page.en.lang.php.

The system is backwards compatible with templates that use the old 'rpublish' submit button. In the new templates you should use 3 buttons with name="rpagestate" and a value of 0 (approved/published), 1 (pending) or 2 (draft).

I don't think expiration per category is worth implementing. Expiration per page is quite enough.

Alex proposal would come in handy(the extrafield).

maybe set expire date options in the categories (as a general setting for that category)? this way peepz can make categories for short term items, and items that have to be stored for 'x' time.

There is no chance of this feature being available in Genoa for at least a month. Or there is such a chance if somebody in the community backports it while I'm on vacation and submits a patch.

Will the changes made to 0.9.4 also be implemented to 0.6.19?
I dare not migrate 11.000+ pages to Cotonti Siena yet from Cotonti Genoa

haven't got that many pages, but the same question applies...

I have implemented it for 0.9.4 this way:
* Page Date is set to the date the page was last updated
* Page Begin sets when the page will become available (and listed)
* Page Expire sets when the page will become unavailable (and not listed). By default Page Expire is set to 0 which means "never expires". Expiration of all existing pages upon update is set to 0, to avoid their undesired disappearing.

Maybe it would be better to add new field to store the date the page was last updated

* Page Date - use date of page creation
 

"reset" expiration maybe?

I have made changes (corehacked) in the SQL statements (in pages and news plugins) to still see the article (even though publication is on the future)
I use something like: page author can always see all pages he/she made (also the ones in the future).
So when an article is published in the future... the author still has the ability to get to that page....

Ow and another thing.... I also show pages to the author that havent been approved yet.. !!!

hope this helps. (I think it is just some smarter SQL statements)

@Trustmaster:
The administrators off these systems know that old pages will go offline.... The expiration date is pretty clear functionality.
Just mention it in the release notes that this could happen in a new version.

I also would like to see this feature to be implemented correctly. Actually it is part of our plans to rewrite all major modules, which will take some time.

1. Draft (author can edit) - red
2. Pending (item is in validation queue, author can't edit, admin can edit or approve) - yellow
3. Approved (publication date is in the future, item is automatically published when it's time) - green
4. Published (item is visible on the site) - blue
5. Expired (item expiration date is expired and no longer visible on site) - gray

Some steps may be skipped. For example an item created by an administrator can go from Draft to Approved instantly (skipping the Pending state), because he can approve it himself. The Approved state itself may be skipped if the publication date is the same as the creation date, because the item would be Published immediately. Most items will not ever reach the Expired state since they don't expire (this feature must be added).

Actually, it seems that the current implementation only lacks a check in lists. This shouldn't be too hard to fix, so I'll look into it.

There should be an option to automatically post items/news/pages with a date set forward in time, just like Wordpress and all other CMF & CMS has.

Today, you can't create a page and set a date for it to be published in 2-3 days time, automatically, since if you validate the page, with it's forward date, it still shows up in Lists and when you click on it, it says "This page will be published in 13 hours and 34 minutes."

This is stupid, above, since If I want a page to go "LIVE" at a certain time, I don't want it to be "sneak previewed" in a list, I want it to be invisible until it's release, i.e. the time & date has passed, and I want to be done automatically.

Wanted Scenario:
1. Create a page and set the date 2011-07-31 10:00 GMT
2. Put in Validation que and edit it so that all dates & times are the same as above
3. Publish it/Validate
4. The page disappears from Validation Que and doesn't show up in any list, rss or alike until the time has come.
5. At 2011-07-31 10:00 GMT the page appears in it's category in all it's splendour.

Current Scenario:
1. Create a page and set the date 2011-07-31 10:00 GMT
2. Put in Validation que and edit it so that all dates & times are the same as above
3. Publish it/Validate
4. The page APPEARS in the category list, rss or alike with the text "This page is published in 13 days 13 hours 2 minutes". NOT GOOD
5. At 2011-07-31 10:00 GMT the page appears in it's category in all it's splendour and that stupid text disappears.

If this option can be fitted to Cotonti, it would make it much more flexible and one doesn't have to babysit the site all the time, since one can publish items that would appear in the future, making it much more appealing to a wider audience.

Ps. I have 2 times before asked for this functionality and it's high tide to implement it!