You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently got a contract where i'll have a huge need of this plugin.
So i'll submit a bunch of feature requests / improvements in the next few days / weeks, and provide accompanying pull requests.
My use case is:
I'm making a simple restricted content plugin where some posts (or any singular post type object) have to be private, but accessible via a specific url containing a key triggering a transparent login to a restricted account (having only read_posts and read_private_posts capabilities)
After a lot of research i determined that the best way to do this is to use the 'private' Wordpress visibility option, to avoid a lot of coding regarding the content not being available in SEO, posts lists, etc...
These 'private' posts have to be shareable via json API to a third-party, that will publish the private links in a member area
Hi,
thanks for your work!
I've recently got a contract where i'll have a huge need of this plugin.
So i'll submit a bunch of feature requests / improvements in the next few days / weeks, and provide accompanying pull requests.
My use case is:
I'm making a simple restricted content plugin where some posts (or any singular post type object) have to be private, but accessible via a specific url containing a key triggering a transparent login to a restricted account (having only read_posts and read_private_posts capabilities)
After a lot of research i determined that the best way to do this is to use the 'private' Wordpress visibility option, to avoid a lot of coding regarding the content not being available in SEO, posts lists, etc...
These 'private' posts have to be shareable via json API to a third-party, that will publish the private links in a member area
So the goal is to add a filter on this line.
A good name could be 'jras_listener_post_statuses' ?
The text was updated successfully, but these errors were encountered: