Not seeing Private posts with Pods find() or shortcodes (breaking from default WP behavior with WP_Query) #6717
Replies: 17 comments
-
|
OK, so I've revisisted this. After a follow-up from Jim I installed a clean WP and installed only your plugin and worked up my example above creating public and private posts with public and private pods.... I'm attaching the json file for this. When the pod is marked as private it does not show in the front end as it should - following WP rules. I set up two pods one public and one private. The private pod did not show (I verified this by making it public when it did).
|
Beta Was this translation helpful? Give feedback.
-
|
I'm still a little confused on some of your issues (I also would've preferred you provide us a Package Migration that included any Templates or Drop-downs as you had configured them so we could see the same issues you're seeing). This statement:
Doesn't make any sense to me. The owner of the data can always see their posts. Always, as long as they're logged in; if they're not logged-in, they're a guest and can't see anything. That's WP Core functionality. From using your test configuration above, if I'm not logged in, I can't see a private post, I can't even see that it exists, which is also intended. I also checked this against WP standard "Posts" and I see the exact same behavior. I can't see private posts unless I'm the owner of the post. I have no awareness whatsoever of private posts, they're not in my back-end admin view nor in the front-end. No title, no anything and they aren't listed in recent posts or archive views. This is as intended. As an Admin, I can see all private posts. This is also as intended by WP Core, unless you change capabilities of your Admin user. As to relationships to private posts (ie showing up in the lists of related items), you aren't going to see private items in the drop down, because they aren't 'published'. That may not be as intended. In such a situation, I'd honestly get away from the concept of "private posts" which aren't actually published, so they're not going to be visible to anything other than the person who created them and they can't probably be linked together for that same reason through a relationship field. Maybe look at instead changing roles & capabilities to create a role that can only post, publish and read their own posts and use that very helpful addition by Members Plugin that allows you to restrict visibility on the front-end at the post level, instead of publishing as Private, just change the visibility of the Content on each page to 'Author' (or one of your own defined roles).
That way, you'd still get to see them in related content, though you might need to change your Relationship rules to ONLY show related posts in the relationship where Author was the logged in user. If I'm totally off on what you're describing the issue is, please be specific, show examples, etc. to help us get to the root of the issue you're experiencing. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately when using the Pods shortcodes, templating, and Pods PHP API, the private posts are probably not taken into account, only published / visible posts show up. We may want to follow up with this. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, they're definitely excluded in the relationship selection. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I think sc0ttkclark understands... the purpose is that an 'author' or whatever role one defines cannot see the element of private pods which are created by them. *What can/cannot be done currently: * Have public post with public pod fields -- everyone can view Have a public post but any pod fields saved as 'private' can't be viewed by anyone even the author and the relationships in the private pod won't work. I can have a private post, with public pod fields and only the author can see this, but any private pod fields can't be viewed even by the author and the relationships in the private pod won't work. If I create a new role as you suggest (and I am assuming it will work as described) it doesn't entirely help because I only want some parts of the pod to be restricted to the author - not all of the fields. The purpose of what I am trying to do (and use pods to do it and nothing else!) is: Create a pod which an author can complete through form fields. Have certain data which is I am trying this on a new install with TwentySixteen theme and all of the posts etc are attached. |
Beta Was this translation helpful? Give feedback.
-
|
For clarification, when you're saying 'private pods fields', are you referring to Fields, Advanced Settings, Visibility, Restrict Access by Roles/Capability? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I can see this is not clear. |
Beta Was this translation helpful? Give feedback.
-
|
The default status used for your pod configuration appears to be 'Draft'. Can you check your Pod settings to confirm the Default Post Status is set to 'Draft'? When you create your pod items, are you setting the status to 'Private' or is it getting forced to that on saving the draft or publishing the content? |
Beta Was this translation helpful? Give feedback.
-
|
@enquirer32 do you have some time today or this week to chat with me directly on this issue to help figure out a solution? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Scott. Yes, the default status is 'draft' but they are definitely not draft because I set them as private. Status is 'privately published'. Happy to give you my admin access to the site I set them up on. Yes, we can talk on Slack - @enquirer |
Beta Was this translation helpful? Give feedback.
-
|
Just a quick update, we need to think about a better long-term solution for setting the where_default option for a Pod dynamically instead of caching it, for support for things like private posts. Here's a quick hack for shortcodes to support private posts in the list, when listing items from a post type pod: add_filter( 'pods_shortcode_findrecords_params', '_private_pods_shortcode_support', 10, 3 );
function _private_pods_shortcode_support( $params, $pod, $tags ) {
if ( 'post_type' == $pod->pod_data['type'] && is_user_logged_in() ) {
$where = sprintf( 't.post_status = "publish" OR ( t.post_status = "private" AND t.post_author = %d )', get_current_user_id() );
if ( ! empty( $params['where'] ) ) {
$params['where'] = '( ' . $params['where'] . ' ) AND ( ' . $where . ' )';
} else {
$params['where'] = $where;
}
}
return $params;
} |
Beta Was this translation helpful? Give feedback.
-
|
Renamed the title of this issue to better reflect the actual issue as it stands |
Beta Was this translation helpful? Give feedback.
-
|
Updated issue description with some tasks |
Beta Was this translation helpful? Give feedback.
-
|
Just to clarify, although I think this is coverd in Tasks above, apart from being unable to view the private pod in a private post, it is not currently possible to view a private pod as a relationship to another pod. |
Beta Was this translation helpful? Give feedback.
-
|
Have just noticed that with the hack one can see anyone's private pods. And, as we saw other day relationships between private pods don't work... |
Beta Was this translation helpful? Give feedback.
-
|
Only the author of the private posts can see them with the shortcode hack, unless you're caching the pages for logged in users somehow? |
Beta Was this translation helpful? Give feedback.
-
|
Guys, did this ever get addressed, please? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Task list
ORIGINAL ISSUE DESCRIPTION by @enquirer32:
I’ve created two pods. The entries associated with these are saved as ‘private’. One cant view the content on the front end of the website.
As admin on this WP installation.
I created new a CPT.
Created one field.
I added new 'testpod' from admin - 'Add New'.
Filled in my one field.
I created a new post and inserted the following shortcode:
[pods name="testpod"]<br />{@test_field}<br />[/pods]I made sure the pod was 'private'
If one views the post on front end one can see the title but no output (it is 'Private')
Reset the pod item to 'public' - the content shows up on the front end.
For me this is a serious issue and it isn't how core WP works. When something is 'Private' the author can always see their own posts.
My set-up: My intention was to restrict the content others could see but always intending that the creator of the content (adding content through a Pod form) could see their own. For example, I have a logged in user who creates content in both pods. He has all the permissions required to edit ‘private’ content and it his content. So long as the data in the pods he created is private he can't access this data.
In my real install I also have a couple of single relationship dropdowns. However, he can’t access these unless the pods are ‘published’ – they don’t work as private either. This is also an unforseen problem which means I can't use Pods the way I had intended.
Is there a temporary fix for this - some hack I can add to the files? Was this always your intention?
You don't need files or images to replicate this yourself - it is very straight forward.
Beta Was this translation helpful? Give feedback.
All reactions