eisaacson

That snippet is not for me. That snippet is a suggestion for you to implement in a next release so that everybody doesn’t lose the previous functionality of their non-public pods that should be allowed within dynamic features.

The issue isn’t that I can’t make things work with the new Access Rights. The issue is that it’s already built on a lot of websites, many of which I no longer maintain. I used the settings in the way they needed to be used to do what was needed in the previous system and now this update has broken everything that was set to non-public. I’m not saying you should have set the defaults differently. Setting dynamic_features_allow=1 and restrict_dynamic_features=0 for any EXISTING post type that was not set to public maintains the functionality as it was for everything existing, thus making it backward compatible. This would be easy to push out in a new update and would correct the issue across all of the websites. It could look something like this:

function fix_nonpublic_pods() {
    $pods_post_types = get_posts([
        'post_type' => '_pods_pod'
       ,'numberofposts' => -1
    ]);
    foreach ($pods_post_types as $post_type) {
        $is_public = get_post_meta($post_type->ID, 'public', 1);
        $dynamic_features_allow = get_post_meta($post_type->ID, 'dynamic_features_allow', 1);

        if (!$is_public && $dynamic_features_allow == 'inherit') {
            update_post_meta($post_type->ID, 'dynamic_features_allow', 1, $dynamic_features_allow);
            update_post_meta($post_type->ID, 'restrict_dynamic_features', 0);
        }
    }
}

That’s interesting. I was able to get it to work by building the page without elementor. It’s weird though. I literally do the same thing on dozens of websites and this is the only one with this issue. Thank you. The workaround will have to do in this case.

I was not able to resolve the issue. For the time being, I have a workaround in place.

in functions.php

function get_pod_content($post_id) {
	$post = get_post($post_id);
	return $post->post_content;
}

then in my template, I call it with {@ID,get_pod_content}. That works for now. It’s not a fix though.

In the Elementor Pods – List Items, I’m using {@post_content} within the "Custom Template" field.

Using a Pod Template, I’m using {@post_content} within the main section of the “Template” field.

All other fields such as {@post_title} are properly pulling the values for the expected pod. I have done this dozens of times on dozens of websites. This one is just not working as expected.

In Elementor, there are a lot of ways to use shortcodes. I’ve used the following elements:

• HTML
• Shortcode
• Text Editor
• Pods – List Items

All of these options have the same issue.

If I did that, wouldn’t I just hoping that it makes in the next update then? If not, I’ll be reverted back to my same issue. That’s why I don’t love updating the plugin code. I’m going to keep my workaround it in my functions.php until we know things are going to work natively. It would be great to know when this is updated though.

That would be great. Thank you!