jricesystemsinsight

The issue may be related to me using get_post_meta() vs get_field()

Sorry for wasting your time, I’m not being a very good debugger today.

Thanks again and I appreciate your fast responses!

Thanks that works! I should have tried ID too I guess, but the description led me to believe no specificity was required.

I am noticing another issue, but I am not sure if I should start another topic please let me know if that’s more appropriate:

Its seems the return value only returns ID no matter if you choose object or name. Is this a part of the same issue?

I don’t think this information is a solution for the OP, but I had a similar issue.

Turns out, the Elementor Builder Plugin has an authorization check that requires a user role to have ‘edit_posts’ granted or else the builder will not load/throw a permission error.

You can find that return statement here: \wp-content\plugins\elementor\core\editor\data\globals\controller.php

Line 21 get_permission_callback() has a return statement: return current_user_can( 'edit_posts' );

In my case with a custom role, custom capabilities for a custom post type I was at a lost.

— I don’t necessarily suggest modifying this line of code, because of the overwrites when updating the plugin, but if you need a temporary fix this can help —

***** Update ******

After some deep diving my colleague located that “edit_posts” is in fact a required capability located in “\wp-content\plugins\elementor\core\editor\data\globals\controller.php”

The return statement in get_permission_callback() is causing the authorization check that fails:
return current_user_can( 'edit_posts' );

Not a permanent/well coded fix, but we simply altered this line of code to have an OR statement for our specific capability. – Be wary this fix will be overwritten when updating the plugin –

In our case the users also could not import pre-created Elementor templates or custom templates. This might be able to be fixed with some other user capabilities, but I am not sure.

For any that may see this question in the future:

I am not 100%, but after doing some testing it looks like you probably need “edit_posts” at the most basic level to get past the authorization error or endless loading. Even with a custom post type with custom capability and capabilities, I think the user needs “edit_posts” for saving Elementor templates and the like. That being said I did not play around with the role manager to reduce user functionality.

Of course this will mean your role can now edit any post types with that capabilities, so I will have no other choice than to simply hide those areas of the menu for that custom role with a 3rd party plugin.

Any update on this?

I also have a custom role with specific capabilities that hangs when trying to load up. The exact same posts work for admins so I know its related to the role.

Thanks this was the issue! I didn’t realize ACF Pro was required or else I would have updated it.

Sure, but the links included were from the plugin creator’s own resources located on Github? Which, I should add were part of my review, considering that would have helped me make a decision before downloading the plugin.

Sidenote: If links are not permitted, WordPress should remove the “link” button. Yeah?

I am struggling with ACF as well when showing certain fields based on the post category/taxonomy selected.

I’m guessing ACF is specifically comparing with the checkbox’s “name” or “type” attribute for the taxonomies and categories. Since the new radio buttons differ it’s causing an issue, at least that’s what I am guessing.

@helgatheviking My suggestion, maybe not best, could you perhaps update the checkbox values based on the correlating radio selections? Depending on what your code does keeping the checkboxes there but hidden?

I think async with JS or on save with PHP could work. I have very limited experience with plugin development though so I am sure it’s not that easy.

I thought I found a solution because everything was cached but that still doesn’t take care of the weird shortcode hidden field issue. So I moved my original reply into my topic as an edit and am leaving this here because I cannot remove it.

• This reply was modified 5 years, 6 months ago by jricesystemsinsight.

Great thanks!

Oh okay, I noticed you said v2.9.0 and the current version is v2.8.3 so I assume this is not something that I can take advantage of until the 2.9.0 release?