Reasoning for the custom post status of ‘private_post’ rather than using ‘private’
Hi,
Is there a reason that the post status ‘private_post’ is used instead of the default WordPress status of ‘private’?
A client of ours has been setting the questions as private from the back end post edit page, and wondering why they are not appearing on the anspress dashboard where the label shows ‘private’. I have realised this is because the posts status needs to be ‘private_post’ to show here.
Is there a better way to set questions as private in the backend, or does it have to be done from the front end for the questions to be set with the ‘private_post’ status?
Thanks for your help!
Matt
Hi Rahul,
That’s ok, looking forward to 4.0!
Do you have an anticipated release date? This site is in production so I’ll hold back on using the Beta.
Thanks
Matt
Awesome! Thanks!
Hey Matt,
There is a reason behind doing this. WordPress ‘private’ posts are strictly not available to anyone who do not have editing capabilities. Hence AnsPress moderator and post author itself will not be able to edit private post if I use default ‘private’ status.
This can be fixed using AnsPress hooks but I don’t want to confuse people by AnsPress private Q&A and private post. Also I want AnsPress moderators can easily access AnsPress private posts (AnsPress moderator do not have any admin capabilities only they can edit AnsPress posts and comments).
AnsPress private post are meant for private discussion with admin or moderators.
You can set private post from wp-admin edit page but its not available in quick edit screen (I am referring 4.0 beta).
Its releasing this week.