[Vladimir]

Hi,

Your hosting provider WpEngine added as MU plugin the condition to kill automatically so called long queries (longer 16384 characters) having database productivity in a mind. This is a reason why a restricted user does not see categories list.

My own thought: It is quite good to kill some ineffective query if it takes too much time at the database server to fulfill it. But it’s not a good idea to measure query productivity at the client side just counting characters inside a query string.

Returning to the problem, query is so long due to Yoast prominent words. Yoast product saves them as taxonomies and currently you have 4108 taxonomy db records automatically created by Yoast. (Some times it seems to me that not SEO exists to enhance the Internet usability) but all around exists to work for SEO. It takes too much resources.)
I will look how to exclude Yoast related taxonomies from a queries modified by URE Pro without having to list them all by ID. I found the related discussion about problem created by prominent words taxonomy for other plugin.

[Vladimir]

I see a problem now.
I created backup copy of your site files and data (except wp-uploads) and installed its copy at my local development environment. When I login as a humanresources user and open the 1st post from the list for editing, I see the list of allowed categories.
But the same meta box shows empty categories list at the production site. I assume that some database error may take place at your installation. Can you look at the system logs for the PHP or MySQL error messages from your server? May be temporal setting of WP_DEBUG and WP_DEBUG_LOG to true may help to see the error message.

[Vladimir]

Hi,

Roles are exported by User Role Editor into zipped .json file, not PDF one.

Restore corrupted role capabilities list granting them manually again. Backup role by exporting them. It will allow to restore missed role back at any moment. Monitor which action/change/update may lead to this result. Report the issue if you can repeat it. I’m ready to investigate the reasons and develop a fix if any bug or incompatibility will be discovered

[Vladimir]

I can not use a new user as got message ‘Disabled’ after try to reset password. I found the older credentials you have sent me earlier and logged-in successfully.

All users with ‘Specific Page Manager’ role (except one) has edit restrictions by categories list set at the user profile. Thus URE does not allow user to create new category and restricts a list of categories available to selection at the post editor page according to that condition from a user profile.

[Vladimir]

Hi,

1st, check if editing for this user is not restricted by category at user and role level both.

If that will not help, then Yes, send login credentials to support [at-sign] role-editor.com

[Vladimir]

Starting from version 4.45 from 07.05.2018 URE Pro follows Gravity Forms version 2.3+ data model change:
Quote from changes list for v. 4.45:
“Function GFFormsModel::get_lead_table_name() call was replaced with GFFormsModel::get_entry_table_name() to provide compatibility with Gravity Forms v. 2.3+”.
This update is not compatible with earlier versions of Gravity Forms.

Workaround: replace URE Pro back with version 4.44 and plan update to the latest version of Gravity Forms 2.3+.

[Vladimir]

Hi,

What version of Gravity Forms do you use?

[Vladimir]

Hi,

You can not install other version of installed plugin via .zip file. You have to delete plugin via WordPress before install it this way as you will always get “Destination folder already exists” error message. Deleting plugin via WordPress will delete the settings you made for URE. So its better to deactivate plugin and remove its folder via FTP or file manager.

If you input a license key at the “Settings->User Role Editor->General” tab, it will be possible to update URE Pro directly from WordPress as any other plugin – from the Plugins or Updates pages. License key is available at your account page after login. Read this article for more details.

[Vladimir]

Excellent! Thanks for the help with testing.

[Vladimir]

Hi Jake!

Good news that they work on a problem. Let’s wait for the update.

[Vladimir]

The fix was included into version 4.47.3, which I published today.

[Vladimir]

I published version 4.47.3 today, which includes the update for this issue:
* Update: Content view restrictions add-on: meta box is added with ‘low’ priority now instead of ‘default’. It’s done for compatibility with custom post types (like “LearnPress->Courses”) for which this meta box was not shown.

[Vladimir]

Thanks for finding this. Line 434 at meta-boxes.php has a syntax error. It should use ‘.’ operator for strings concatenation instead of ‘+’. So valid code will be:

return array('result'=>'success', 'message'=>'Widgets permissions for '. $ure_object_name, 'html'=>$html);

I will include this fix into the next version 4.47.3. Let me know the result of your testing with updated version of this file.

[Vladimir]

Thanks for your help in isolating this bug. I will publish the fix.

[Vladimir]

Hi,

Go to every subsite where you have a problem and check if ‘Administrator’ role there has those custom post types capabilities granted.

[Author]

Posts