Thank you, Peter!
After mulling on this for a while I think I agree with you about being able to view the Archived content if you are a logged in user with the proper capabilities to do so. You can expect this change in the next release.
However, I do think that Archived content still should not be editable. It defeats the purpose of the status since it’s meant to be a “post-published” state, not a “pre-published” state like Drafts.
Once a user archives something, they should have the reassurance that the content has not changed since when it was a published piece of content.
Hi
Actually, while I see your point, I do disagree. That’s why I think a setting that controls the behaviour would be beneficial – in that way, I have the option to control just how “archived” the posts are.
One of my main reasons for wanting to be able to edit the post is that, I have many sites with custom post types that are only used to pull information onto a page. These CPTs do not have code to view them as individual posts, so it is not possible to view the post via the front end and when I click on the view link, all I get is a 404 error. If the posts are archived, then there is absolutely no way to view the content.
Perhaps you might consider a settings page? The options would be (1) No view (2) View via front end only (3) View edit post screen but make them non-editable (4) Allow editing
Cheers!
Hey Peter,
Any person with the read_private_posts capability will be able to view archived content on the front-end.
You can customize the default capability using the aps_default_read_capability filter for which an example is provided in the FAQ.
Exposing an API for different “options” may certainly be something that is added in the future. However, I tend to shy away from such panels unless the options they present are very in demand and varied.
The preferred route for customization is for developers to take advantage of the many low-level hooks provided in the plugin and override them with their own desired behaviors. There is a little manifesto about this also at the top of the FAQ page.
