[4.49.1] 12.11.2018
Core version: 4.47
- Fix: Content view restrictions add-on: Fatal error was fixed: Argument 1 passed to URE_Content_View_Restrictions_Posts_List:can_edit() must be an instance of WP_Post, instance of stdClass given.
- Update: Unused code was removed from user-role-editor-pro/pro/includes/classes/bbpress.php
- Core version was updated to 4.47:
- Fix: “Users->User Role Editor”: Capabilities view was not refreshed properly for new selected role in case “Granted Only” filter was turned ON before other role selection.
- Update: Unused code was removed from user-role-editor/includes/classes/bbpress.php
- Update: Prevent sudden revoke role ‘administrator’ from a user(s) during capability with the same ID (‘administrator’) deletion from roles.
- Update: Adding custom capability ‘administrator’ was prohibited.
- Update: Marked as compatible with WordPress version 5.0
[4.49] 21.10.2018
Core version: 4.46
- New: Content view restrictions add-on: It’s possible to set default URL for redirection in case of view access error. If redirection URL for post/page is not set, URE uses default value. If default value is not set URE redirects user the automatically built to the site login URL.
- Update: Content view restrictions add-on: Internal cache usage was optimized to increase performance for sites with large quantity of posts and users.
- Update: Other roles access add-on: ‘Blocking any role for “administrator” is not allowed.’ message is shown after click “Other Roles” button for “administrator” role.
- Update: Meta boxes access add-on: Dialog markup uses fixed columns width in order all columns will be visible without horizontal scrolling.
- Update: Admin menu access add-on: White listed arguments are supported now for the links from the “Tools” menu.
- Fix: Widgets admin access add-on: “Undefined index … in widgets-admin-access.php line #78” warning was fixed. Warning was shown in case if blocked widget does not exist (due to related plugin deactivation or deletion).
[4.48] 25.09.2018
Core version: 4.46
– typo at word ‘pemissions’ was corrected at the “Settings->User Role Editor->Additional modules” tab.
– source code .php file reading file(…) call was wrapped by ‘try …catch’ to exclude PHP warning generation in case of a problem with access to a source code file.
It is critical for sites with large quant of users.New query does not take into account though some cases with incorrect users data (usually imported from the external sources). It’s possible to use older (comprehensive but slower) query version defining a PHP constant: “define(‘URE_COUNT_USERS_WITHOUT_ROLE_THOROUGHLY’, true);” or return false from a custom ‘ure_count_users_without_role_quick’ filter.
[4.47.3] 18.08.2018
Core version: 4.45
- Update: Admin menu access add-on: admin menu copy creation priority was increased from 9999 to 9999999997 in order to execute code after that FooGallery plugin added all its menu items.
- 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.
- Fix: Content view restrictions add-on: try to access the restricted child page returned “page not found” error instead of redirect to URL. Redirection did not work in case global $post was not define to the moment. Find the page ID by its path from the URL for this case now.
- Fix: Syntax error was fixed which produced “PHP Warning: A non-numeric value encountered in …/wp-content/plugins/user-role-editor-pro/pro/includes/classes/meta-boxes.php on line 434”.
- Core version was updated to 4.45:
- Fix: Capability checkbox was shown as turned ON incorrectly for not granted capability included into a role, JSON: “caps”:{“sample_cap”:”false”}. Bug took place after the changing a currently selected role.
- Fix: Custom capabilities groups “User Role Editor” and “WooCommerce” were registered at the wrong 3rd tree level – changed to 2.
[4.47.2] 05.07.2018
Core version: 4.44
- Update: Widgets admin access add-on: It’s possible now to block the access to sidebars (widgets areas) created by a user with help of Divi theme.
- Fix: Content view restrictions add-on: ‘warning index not defined’ (content-view-restrictions-posts-list.php, line #395) was fixed.
- Core version was updated to 4.44:
- Update: URE had executed ‘profile_update’ action after update of user permissions from the user permissions editor page: Users->selected user->Capabilities. It was replaced with ‘ure_user_permissions_update’ action now. It will allow to exclude conflicts with other plugins – “WP Members” [lost checkbox fields values](https://wordpress.org/support/topic/conflict-with-wp-members-2/), for example.
- Update: Additional options for role (like “Hide admin bar” at the bottom of URE page) did not applied to the user with ‘ure_edit_roles’ capability. This condition was removed.
- Update: fix PHP notice ‘Undefined offset: 0 in …’ at includes/classes/protect-admin.php, not_edit_admin(), where the 1st element of $caps array not always has index 0.
- Update: PHP required version was increased up to 5.4.
[4.47.1] 05.06.2018
Core version: 4.43
- Core version was updated to 4.43:
- Update: references to non-existed roles are removed from the URE role additional options data storage after any role update.
- Fix: Additional options section view for the current role was not refreshed properly after other current role selection.
[4.47] 22.05.2018
Core version: 4.42
- New: Support for new user capabilities introduced by WordPress 4.9.6 was added: manage_privacy_options (Settings->Privacy), export_others_personal_data (Tools->Export Personal Data), erase_others_personal_data (Tools->Erase Personal Data).
- Fix: Divi theme et_pb_layout (Divi Library) custom post type (CPT) was unavailable even for admin when “Force custom post types to use their own capabilities” URE option was turned ON. et_pb_layout CPT is not available by default at User Role Editor pages (users.php), and we have to tell Divi to load et_pb_layout for URE pages via Divi’s custom filter ‘et_builder_should_load_framework’.