[Vladimir]

Fix is available with Beta version 4.50.3.b1 from the same download page after login.

[Vladimir]

Thank you very much. I confirm the bug. I will try to offer a fix tomorrow.

[Vladimir]

Can you look via Google Chrome “Developer tools – Network” tab if JSON response from server does not support any not waited error message beyond JSON data structure itself, but it’s clear as at this screenshot?

[Vladimir]

Hi,

Even deactivation of URE removes all additional restrictions set for roles and users. But the changes you made to roles (grant/revoke capabilities) are permanent and does not depend from URE presence at your site.

As restrictions for media library items are still in action after URE deletion – the source of a problem is in some other plugin.

[Vladimir]

I missed this topic somehow. My apologies for delay with response.
The recent clarification is very important. I missed during development the scenario with user account activation via link sent by email and tested only interactive user creation by admin without confirmation email involved. So look at this part (activation of account with multiple roles via link from confirmation email) as a feature, which is not realized yet. I will add it definitely. I will try to make it with the next update.

[Vladimir]

As “Not selected” requires careful tuning by including additional URL arguments to white list, I asked you to show how do you build “Selected” list. Is it direct inversion of that you showed above? I wonder why do you have a problem with access to Widgets and Menus under Appearance with “Selected” model. It’s the 1st time I get such report. If it’s possible to looks at your site on-line send URL and admin credentials to suport [at-sign] role-editor.com

[Vladimir]

Hi,

Show screenshot of “Admin menu access” selection you made for the “Block Selected” variant.

“Block not Selected” requires more careful tuning to workaround a redirection to admin dashboard. Explanation is here.

[Vladimir]

I published version 4.50.1 just now be cause of other bug report – Front-end menu access add-on was not loaded due to it. Both bugs were fixed at 4.50.1 release.

[Vladimir]

Hi,

Thanks for this bug report. I confirm it. I will include a fix into upcoming version 4.50.1. I will publish it in a few days, just in case some other bugs will be discovered. Until that, it will be available as beta version 4.50.1.b1.

Quick fix – replace URE_Other_Role_Access::update_data() method with this version:

    public function update_data() {
    
        if (!isset($_POST['action']) || $_POST['action']!=='ure_update_other_roles_access') {
            return;
        }
        
        $editor = URE_Editor::get_instance();
        if (!current_user_can(self::OTHER_ROLES_ACCESS_CAP)) {
            $editor->set_notification( esc_html__('URE: you have not enough permissions to use this add-on.', 'user-role-editor') );
            return;
        }
        $ure_object_type = filter_input(INPUT_POST, 'ure_object_type', FILTER_SANITIZE_STRING);
        if ($ure_object_type!=='role' && $ure_object_type!=='user') {
            $editor->set_notification( esc_html__('URE: other roles access: Wrong object type. Data was not updated.', 'user-role-editor') );
            return;
        }
        $ure_object_name = filter_input(INPUT_POST, 'ure_object_name', FILTER_SANITIZE_STRING);
        if (empty($ure_object_name)) {
            $editor->set_notification( esc_html__('URE: other roles access: Empty object name. Data was not updated', 'user-role-editor') );
            return;
        }
                        
        if ($ure_object_type=='role') {
            $this->objects->save_access_data_for_role($ure_object_name);
        } else {
            $this->objects->save_access_data_for_user($ure_object_name);
        }
        
        $editor->set_notification( esc_html__('Other roles access data was updated successfully', 'user-role-editor') );
        
    }
    // end of update_data()

[Vladimir]

Workaround:
Deactivate new version of URE Pro at the new site.
Copy older version of URE Pro via FTP to other folder of new site, like user-role-editor-pro-4.40.
Activate older version of URE Pro.
Fulfill roles import.
Deactivate older version of URE Pro. Delete it via FTP.
Activate back newer version of URE Pro.

You can make similar steps with newer version of URE Pro at old site. But you will need to export/import roles one by one. Newer versions of URE Pro (4.41+) do not support multiple roles export/import as a single operation.
It will be added with time.

[Vladimir]

Got it. This file was exported with older version of URE Pro. It’s format is not compatible with versions of URE Pro starting from 4.41:

= [4.41] 06.02.2018 =
* Core version: 4.40.1
* New: Export-import module was rewritten:
* - Attention: New exported data format is not compatible with data exported by older versions.
* - Users->User Role Editor: Export/Import buttons applied to the single currently selected role only.

[Vladimir]

Send me exported .dat file (support [at-sign] role-editor.com). I will check what is wrong with its content.

[Vladimir]

I plan to publish version 4.50 at the 1st week of March.

[Vladimir]

Hi Armel,

One of updated files is JavaScript file. It sends critical parameter related to the redirection.
Force full refresh for User Role Editor page at network admin (or clear browser cache) to be sure that the latest JavaScript works during your test.

[Vladimir]

Issue with redirection after “Plugins access” data update from the network admin was fixed at 4th beta.

[Author]

Posts