Forum Replies Created
-
AuthorPosts
-
Vladimir
KeymasterThanks for the information. Generally, URE makes nothing critical. It modifies GF dashboard widget SQL query adding to it WHERE conditions like “AND id IN (1, 2, 3)” to limit the list of forms available at this widget. This modification is not query consumable. I may just suppose that you may have some active add-ons for Gravity Forms, which may lead to the conflict.
I may just repeat my question:
Can you provide me a copy of site database and files (without wp-content/uploads) via DropBox or similar? Use email address support [at-sign] role-editor.com
I will monitor using my debug environment, what does really happen after user login with your site copy.Vladimir
KeymasterHi,
Does 502 error take place for a user with access restrictions to Gravity Forms realized with URE Pro? Show me the screenshot of URE GF restrictions section from this user profile.
Vladimir
KeymasterTry version 4.42 (published today).
Page templates list is available as blocking criteria for a role just below the categories.04/04/2018 at 02:07 in reply to: How to hide certain pages from user role in backend but allow front end viewing #4733Vladimir
Keymastersupport [at-sign] role-editor.com
Vladimir
KeymasterYou can try. Login with working account, clear the cache, wait 3-5 minutes, login again. It should stop working, if I understand the situation right.
Can you provide me a copy of site database and files (without wp-content/uploads) via DropBox or similar? Use email address support [at-sign] role-editor.com
I will monitor memory usage and look if we can optimize the restrictions criteria.Vladimir
KeymasterHi,
URE does not apply any restrictions to the users with ‘administrator’ role. It may use older cache for such user in this cache. Data are cached by user ID without saving user role, taking into account that changing user role to administrator and back is not a situation from a real life.
29/03/2018 at 04:10 in reply to: How to hide certain pages from user role in backend but allow front end viewing #4725Vladimir
KeymasterGive me more information. What settings did you make for restricted user? What do you try as restricted user at the wp-admin? Show screenshots.
29/03/2018 at 02:17 in reply to: How to hide certain pages from user role in backend but allow front end viewing #4723Vladimir
KeymasterHi,
Right, it’s possible with content edit restrictions add-on:
Vladimir
KeymasterHi,
It depends from what criteria do you use when restricts admins with limited privileges.
For example, if you block access to some posts, you can use block model and block 1000 posts by some criteria, but allow 5. Apparently much more memory is required to get those 1000 posts ID list than just 5 posts ID.
URE caches results of db queries using WP transients, thus for some time memory consuming may be postponed.The most simple workaround: increase available memory for logged in users with some role. Use
ini_set('memory_limit', '512M');
and wp_login action.
Vladimir
KeymasterHi Martin,
Menu item “Settings->Admin Columns” is protected by “manage_admin_columns” capability. Check if it was granted to the administrator role. If it does not exist for some reason, re-create it manually.
Vladimir
KeymasterHi,
You can remove URE’s content view restriction from such post and look it a WordPress built-in post visibility features (private or password protected posts) will fit for your need:
Post VisibilityVladimir
KeymasterHi Urs,
This feature is worth to be realized. I will do it with one of the next updates.
Vladimir
KeymasterHi Urs,
Currently URE copies to a new created subsite only the roles from the main site. Settings made for the main site via add-ons are not copied to new sub-site automatically.
It seems as a missed feature. Thanks for pointing me on this.
Vladimir
KeymasterHi,
Such feature is not supported.
Vladimir
KeymasterHi,
Thanks for the clarification. We looked at the different versions. Download link at https://wordpress.org/plugins/redirection/
leads to the version 3.2, but “Download Plugin” button at the https://redirection.me/ leads to the version 3.2.1 (development version).
v. 3.2. uses for admin menu item “Tools->Redirection” the ‘administrator’ role, but v. 3.2.1 (which I tested) uses ‘manage_options’ already.
You can update to version 3.2.1 or use this filter to change ‘administrator’ to ‘manage_options’ or your own custom capability:add_filter('redirection_role', 'replace_redirection_cap', 10, 1); function replace_redirection_cap($cap) { $cap = 'manage_options'; return $cap; }
I recommend the 2nd variant, as version 3.2.1 still use ‘administrator’ in some places, for the REST API calls, for example.
-
AuthorPosts