Hi,
It should work in multi-site environment, except of case you found a real bug. If such I will fix it.
It’s very strange error message about ‘wp_2_usermeta’ doesn’t exists, but SQL query contains ‘wp_4_usermeta’ only.
I didn’t tested per site activation. As plugin is available for the super-admin only it is no sense activate it site by site. Please try to activate it for the whole network at once using ‘Network Activate’ link from the Network admin Plugins link and let me know if error still exists.
Login question is not related to the User Role Editor plugin. It is a common feature for WordPress. User is created not in site N, but in the network and added to the selected site then. So you can login and see your profile in any case, even you are not added to any site.
Hello ,
Thanks for your response.
I understand that on Multi Site environment, it makes no sense to activate a plugin per site. I have done Network Activate first, it has givne me error then. Then i activated per site, it has give the above error. Now, i have done Network Activate once again and now it is giving me following erorr many time:
WordPress database error Table ‘DB_NAME.wp_2_usermeta’ doesn’t exist for query SELECT count(*)
FROM wp_2_usermeta
WHERE user_id=1 AND meta_key=’wp_2_capabilities’ AND meta_value like ‘%administrator%’ made by require_once, do_action, call_user_func_array, ure_init, ure_is_admin, ure_has_administrator_role
So, basically it is throwing error in both cases for me: Per site and Network Activate.
Please let me know if you need more info.
Thanks,
Harpinder
Hello,
It seems you found the bug and I should use more universal code in this place. Please try this updated version of URE plugin
http://www.shinephp.com/wp-content/downloads/wordpress/plugins/user-role-editor-3.2.1.zip
and let me know if bug is gone or not.
Regards,
Vladimir.
Hi Vladimir,
Issues seems to be fix now… I have tested this plugin for both Network & Site wide … working fine for me.. no php errors.
Thanks for correcting the issue.
Harpinder
Hi Harpinder,
Thanks to you. I could isolate and fix this issue with your help only.
Thus it’s resolved, I will publish 3.2.1 update.
Regards,
Vladimir.