Publishing changes

I’d like to suggest some changes to the way that publishing is handled. I’m trying to work through some of this right now and finding it a bit tricky.

1. Add a publishedon field to site_content that functions just like createdon or editedon. The published date seems much more valuable to me than the created date when it comes to news, blogs and other things.

2. When a document is unpublished it should clear the pub_date if it is already passed and vica-versa.

I need this for a site one way or another, if we want it in the core I’ll just make the changes and commit them, otherwise I’ll see if I can get by with a plugin some how.

Adam, can you explain why we would add publishedon in addition to the already existing pub_date; I don’t understand the difference or why both would be needed...

I think this is an area that completely makes sense... and would agree that it makes a great addition to the core. Being able to publish/unpublish individual [*content*] or [*TVs*] would be really, really cool.

pub_date does not represent the date the document was actually published. It is only set manually if a person wants to have a timed published date. Publishing and unpublishing a document using the published checkbox won’t affect the pub_dat at all. So the only way that you can use that for say sorting news is if you tell your users to manually enter it whenever they publish a document.

publishedon would be set automatically whenever a document is published in a very similar way to editedon.

We could use pub_date but we’d have to change the way it works so that it would be automatically set when you published a document and couldn’t every be cleared for a published document, but would have to be cleared for an unpublished document. I wouldn’t mind that either but it seems much easier to just add a publishedon field.

Quote from: rthrash at Jan 31, 2006, 12:45 PM

Being able to publish/unpublish individual [*content*] or [*TVs*] would be really, really cool.

Are you thinking at a document level or a global level?

@Adam: document-level

Quote from: rthrash at Jan 31, 2006, 12:55 PM

@Adam: document-level

I never thought about that. I can see that it could come in handy though.

Just to keep throwing things out, view permissions on TVs would be cool too.

bingo!

Moving permissions down to a granular / object vs. the current page level would indeed be cool.

For consistency sake should we also create a publishedby field? I don’t see a lot of point to, but I don’t see a lot of point to createdby or editedby either.