Forum Replies Created
-
AuthorPosts
-
Vladimir
Keymaster2nd, there is a user_can_richedit filter hook which may globally switch off a Visual Editor. Check if such filter was not added somehow to your site via plugins of theme files.
Vladimir
Keymaster1st, check browser JavaScript console for the error messages. Visual Editor is realized via TinyMCE made in JavaScript.
Vladimir
KeymasterPeter,
There is no visible reason for ‘aa_’ prefix inside permissions related database records until it may stay from the older data imported from the other database with such ‘aa_’ prefix.
These articles describe how WordPress stores it’s roles:
1) Single site;
2) Multisite.WordPress multisite stores user permissions inside a single database table ‘wp_usermeta’ in assumption that database prefix is ‘wp_’.
So look what ID your user has and try to get all permissions records related to this user with query like:SELECT * FROM wp_usermeta WHERE user_id=1 AND meta_key like '%capabilities';and look if a record with ‘wp_capabilities’ meta_key value is there or it is not.
If it is not try to rename ‘aa_’ to ‘wp_’ and look if it will help.
As always, it’s a good habit to make a fresh backup before any manual data change.Vladimir
KeymasterIf you restricted the custom role with Admin menu add-on pay attention on the Technical details part of the documentation article.
Vladimir
KeymasterPlease try a beta version 4.49.2.b1. It is available from the same downloads page after login and includes a fix of the “empty custom fields list” issue.
Vladimir
KeymasterWooCommerce v. 3.4.6. had a bug, due to which even superadmin at WP multisite saw only ‘customer’ role. That bug was fixed by WC developers now. Only shop_manager role is limited by ‘customer’role by default. WooCommerce offers custom filter ‘woocommerce_shop_manager_editable_roles’ which allows to change this default behavior without any version rollback or any kind of a hack applied to WooCommerce source code.
This filter is documented here and mentioned at this topic too.I think having this solution in the mind there is no need in any intervention to this issue from User Role Editor Pro.
20/11/2018 at 13:49 in reply to: Author is just allowed to post in one category – but gets "Cheating Uh?" message #5294Vladimir
KeymasterHi Tom,
I made another test with ‘author’ role and can not repeat a described issue.
Is it possible to get access to a backup copy of your site (files except wp-content/uploads) and database created with UpdraftPlus plugin?
If Yes, then share .zip with support [at-sign] role-editor.com via DropBox or similar service.
I install and test such copies at my local development environment only.Vladimir
KeymasterThanks for the clarification. I repeated the described issue. I will investigate it and work on a fix.
Vladimir
KeymasterLicense key activation is not related to this issue.
Check if roles list is empty (not empty) at the “Users” page “Change role to:” drop-down list and at the “Role:” at some (not yours) user profile page.
I suppose your main site may lose roles record somehow.Vladimir
KeymasterDescribe what restrictions are applied for a role which have an issue with custom fields.
Vladimir
KeymasterMay be it is a some issue with caching plugin, if you use one?
Vladimir
KeymasterIt’s possible to show for a user just his own posts at wp-admin. Use for that “Own data only” option, presented by “Edit posts/pages restrictions” add-on.
Vladimir
KeymasterCustom fields created by different authors are available between those users by default. If you have more than 30 custom fields list may be limited by 30 items by default. There may be fields with special protection, which will be unavailable for the ordinal users without special permissions. Read this post for more details.
Vladimir
Keymaster@curtin-webteam, thanks for letting me know.
Vladimir
KeymasterThanks for suggestion. It makes code more universal. I accept it with a little addition to remove a beginning slash from a resulting value, if it’s there:
private static function get_page_path_from_url() { $url = substr( untrailingslashit( parse_url( $_SERVER['REQUEST_URI'] , PHP_URL_PATH) ), 1); $home_url = basename( untrailingslashit( parse_url( home_url(), PHP_URL_PATH ) ) ); $path = substr( $url, strlen( $home_url ) ); if (substr( $path, 0, 1)==DIRECTORY_SEPARATOR) { $path = substr( $path, 1); } return $path; } // end of get_page_path_from_url() -
AuthorPosts