Forum Replies Created
-
AuthorPosts
-
Vladimir
KeymasterWhere 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.
Vladimir
KeymasterThanks 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.Vladimir
KeymasterYes, 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.
Vladimir
KeymasterHi,
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.png05/02/2016 at 14:39 in reply to: Something went wrong: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 #1944Vladimir
KeymasterPlease 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.05/02/2016 at 13:42 in reply to: Something went wrong: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 #1943Vladimir
KeymasterPlease ignore a suggestion you may receive by mail – it’s testing is not finished yet.
05/02/2016 at 13:38 in reply to: Something went wrong: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 #1942Vladimir
KeymasterIn 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.
05/02/2016 at 08:12 in reply to: Something went wrong: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 #1940Vladimir
KeymasterHi,
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.
Vladimir
KeymasterUser 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.
03/02/2016 at 06:33 in reply to: Problems creating new post with user having category/taxonomy ID restriction #1935Vladimir
KeymasterThanks. I reproduced a problem and will develop a fix for it.
Vladimir
KeymasterIf a post was written by other author – user should have ‘edit_others_posts’ capability to be capable to edit that post. ‘Edit posts restrictions’ section does not give to the user additional capabilities, it narrows the existing permissions.
29/01/2016 at 02:00 in reply to: Restrict access to Gravity forms by Role and not just by user #1926Vladimir
KeymasterHi,
Role based access management for Gravity Forms is unavailable currently.
I agree with you. This feature will be very useful. It’s in my development plan already. I hope it will be available in 1-2 months.Vladimir
KeymasterThanks for the suggestion. I will do.
Vladimir
KeymasterThanks for letting me know. I will realize this feature for roles.
Vladimir
KeymasterHi Alex,
Thanks for the feedback.
Do you offer to realize this feature for roles? I thought that 1-2 such users do not require of additional layer. What quant of users are allowed to activate/deactivate plugins in your case?
-
AuthorPosts