Forum Replies Created
-
Posts
-
Hi Daniela,
License key is required to get access to the auto-updates. Without a valid license key update package is not available.
Hi Daniela,
URE Pro is fully functional just after installation.
License key is needed for the access to the auto-updates. You may find it at this page after login.Hi Urs,
Version 4.23 is published. Please check your Plugins page and Update center if the information about this update is available.
Hello,
Thanks. I added a code to fix this notice in upcoming version 4.23. I plan to publish it soon.
Where did you get information that the current version is 4.23.2? It’s a number of current free version at wordpress.org plugins repository? Free and Pro version numbers don’t match sometime. I added a ‘core version’ information into the Pro version changes list for this reason.
According to the Download page (you should login 1st) the current Pro version is 4.21.1. I just plan to publish Pro version 4.23 (with core (free) version 4.23.2 included) after fixing some minor issues recently discovered during tests.
If you don’t wish to experiment with manual version change at the user-role-editor-pro.php file, please wait a little until I publish Pro version 4.23 and let’s return to the subject then.
Thanks for the feedback.
There is a “per plugin access for users with ‘activate_plugins’ capability” add-on. Look this video:
It was made for the older version of WordPress and URE but the main functionality is unchanged.Yes, it works for the WordPress multisite. If plugin is network activated auto update information is available at the “Network Admin” dashboard only.
You may test that easy – change version number at user-role-editor-pro.php file header to the lower one and look.
Hi,
Thanks for the feedback.
URE Pro supports auto-update from the very begin:
https://storage.googleapis.com/role-editor/downloads/support/ure-autoupdate-plugins.png
https://storage.googleapis.com/role-editor/downloads/support/ure-autoupdate.pngPlease re-test. It’s seems my service provides right answer for the older curl versions now.
At least an error was gone when I try to test from my 1and1 server.In general problem may be resolved by updating server side curl version to one which support automatic selection of TLS v. 3. I agree that it’s a problem with a shared hosting. Fortunately, I can reproduce a problem at my 1and1 hosted server and search a solution currently.
Hi,
Earlier versions did not check license key after you updated it.
This issue could be related to the older version of system software (PHP, curl) installed at your hosting server:
http://unix.stackexchange.com/questions/192944/how-to-fix-curl-sslv3-alert-handshake-failureTry input into browser this URL:
https://www.role-editor.com/update?action=get_metadata&slug=user-role-editor-pro&license_key=your-license-key-hereDoes it work without error?
URE just calls wp_remote_get() with this URL. A problem with SSL connection occurs at PHP or even deeper system level.
User Role Editor Pro will provide it.
If you give to a user role ‘edit_others_posts’ capability, you have these variants how to restrict his access to the posts list:
1) input to a user profile the only ID of the post from other author – user will can edit just the only post with that ID (or the list of posts in you input multiple IDs).
2) input this user ID to the ‘with author user ID (comma separated)’ field. User will can see and edit its own posts only at WordPress the admin backend.
