visibility of post

Hi Lisa,

There is a filter called aps_status_arg_public that is already available in the plugin. So if you feel comfortable hooking into this filter with your own function, you could customize this behavior however you like.

However, I do plan to take this a step further in the next update by adding two custom capabilities called read_archived_posts and read_archived_pages which will be granted to Administrators and Editors by default.

This will make viewing Archived content similar to viewing Private content, which uses the read_private_posts and read_private_pages capabilities.

Thanks Frankie, please update me when you do.

Also please be sure to share with AWP, going to be giving your Prevent Concurrent logins a try soon.

Hi Lisa,

I just released 0.3.0 which addresses the visibility issue.

I opted not to create a custom role (yet), as that will be more extensive. But in this release, any users with the read_private_posts capability will be allowed to view Archived posts on the frontend.

https://www.ads-software.com/plugins/archived-post-status/changelog/

The redirect issue is another topic entirely and will likely take a lot of time and thought as to how exactly it should work. I’m not even sure if it can work since post objects aren’t yet available during template_redirect.

Wow, that was fast!

I suggest working with Joost on the redirects.

Meaning perhaps this could tie into WordPress SEO Premium?

Is there a way to toggle this front-end visiblility off?

It’d be nice to have an option to have archived content not visible anywhere except via the “Archive (0)” link in the admin. (I posted another thread about hiding them by default in the admin listing, like Trashed items.)

Hi mpmchugh,

There are a lot of filters available in this plugin to customize the behavior to pretty much do whatever you want.

As stated above, any user with the read_private_posts capability will be allowed to view Archived posts on the front-end. There is a filter to change the default read capability called aps_default_read_capability.

There are other filters available for even higher-level control of visibility:

add_filter( 'aps_status_arg_public', '__return_false' );
add_filter( 'aps_status_arg_exclude_from_search', '__return_true' );

As stated above, any user with the read_private_posts capability will be allowed to view Archived posts on the front-end. There is a filter to change the default read capability called aps_default_read_capability.

Frankie, how so you set a user to read_private_posts capability? We have three admins and we cannot see one another’s archived posts.

Andy

Hi Andy,

The read_private_posts should be given to all Administrators by default.

If you want granular control over which capabilities each role has assigned to them, I recommend the Members plugin by Justin Tadlock.