23/08/2018 at 13:08 #5106
Our HR team has a user that is a Specific Page Manager/Editor, they used to be able to see the categories in posts and add categories when creating posts but they can’t anymore. I looked at their roles and don’t see anything that isn’t checked that may relate to categories. I’m able to see all categories but I’m an admin.
Could I give you credentials to log in and see what the issue may be?
Thanks!23/08/2018 at 14:26 #5107
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.com23/08/2018 at 22:35 #5108
I don’t believe they are but I’m not positive. Just sent the credentials24/08/2018 at 04:02 #5109
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.24/08/2018 at 16:51 #5112
They used to be able to see the categories though. We need them to be able to add a new post to the “Job Posting – Faculty” or “Job Posting – Work Study” categories, how can I accomplish that?26/08/2018 at 03:48 #5114
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.27/08/2018 at 19:43 #5115
Hey Vladimir, here are the error logs I found:
[Sun Aug 26 02:26:36.629836 2018] [:error] [pid 11490] [client 126.96.36.199:10566] KILLED QUERY (21165 characters long generated in /wp-content/plugins/user-role-editor-pro/pro/includes/classes/posts-edit-access.php:520): SELECT term_id, meta_key, meta_value FROM wp_termmeta WHERE term_id IN (3075,3073,3997,1756,1760,1754, …
[REMOVED]28/08/2018 at 03:09 #5116
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.28/08/2018 at 04:21 #5117
I uploaded updated version of /user-role-editor-pro/pro/includes/classes/posts-edit-access.php file to your site.
* Update: Edit posts/pages restrictions add-on: non-public taxonomies are not included into restricted database queries. URE will build now much shorter database queries for the sites which have a lot of such taxonomies at the database. For example sites with WP SEO Premium plugin, where ‘yst_prominent_words’ taxonomy may count thousands records at wp_terms and wp_term_taxonomy db tables.
It fixed a problem. Make own tests.28/08/2018 at 21:41 #5118
Awesome! Thank you so much!!! Everything appears to be working on my tests as well, thanks again!
- You must be logged in to reply to this topic.