Posts Tagged ‘capability’
bbPress User Role Editor conflict fix
Friday, January 4th, 2013
bbPress, popular WordPress plugin realizing forum functionality on the base WordPress framework and, as themselves say “WordPress way”, introduced enhanced role model starting from version 2.2. bbPress users, who use “User Role Editor” (URE) WordPress plugin to manage blog user roles, suddenly discovered that URE shows bbPress roles with almost all capabilities turned on, even for minimal ‘Blocked’ and ‘Spectator’ roles.
URE showed bbPress roles quite well before the bbPress version 2.2. update. What’s happened?
Let’s look. WordPress stores its roles data the way, that only active capabilities stored into the role.
URE showed bbPress roles quite well before the bbPress version 2.2. update. What’s happened?
Let’s look. WordPress stores its roles data the way, that only active capabilities stored into the role.
edit_theme_options capability for WordPress user
Friday, September 28th, 2012‘edit_theme_options’ capability seems to be self-explained. It’s primary purpose is to provide access to WordPress front-end theme options changing.
On practice, if you have ‘edit_theme_options’ capability, then you have access to the ‘Appearance’ menu at WordPress admin back-end and to its menu items: “Themes” (select a theme for your WordPress front-end) and “Menus” (edit menus supported by your selected theme). Customize theme header image, background color, etc. section and ‘Widgets’ menu items require ‘edit_theme_options’ capability also.
How it is realized? How often and at what places WordPress uses/checks this user capability – ‘edit_theme_options’ in order to decide give current user permission to edit theme options or prohibit access to such functionality? Let’s check this together. We will make a quick look into WordPress version 3.4.2 core source code and comment its related fragments.
update_core capability for WordPress user
Sunday, August 5th, 2012
Codex gives us nothing about update_core capability for WordPress user, except WordPress version of its appearing in the code – 3.0. I suppose according to its name, that
WordPress update_core
capability is used to decide, if user can update core WordPress file using built-in WordPress upgrade feature or not. What do you think?
Thoughts are just thoughts, while they are not confirmed by practice and strong experiment. Thus, I decided to check this obviouse guess, satisfy my curiosity and investigate, how and for what purpose WordPress uses update_core capability really. Result of my little investigation will be shown to you below.
The only last will win – You!
Tuesday, July 10th, 2012But you are not glad. You are not happy. What the reason? You are angry on all those new blogs owners. They do, what they want. They change, what they wish. They should make good posts only! Why all of them are administrators of their blogs? The Administrator should be only one – You. Only One will Win – You! The biggest thing, what you may allow to your WordPress managed network blogs owners – be the editors on their blogs.
That’s a joke, of course. But some time, somewhere… What to do, if text above describes your situation somehow? Don’t worry, try “Win Only One” WordPress plugin. Just setup and activate for Network. It will help you transparently. Your problem will be resolved in the full silence.
User Role Editor version 3.7 is published
Saturday, June 23rd, 2012User Role Editor WordPress plugin version 3.7 is published at June 23rd, 2012. What’s new?
– ‘Select All’, ‘Unselect All’, ‘Inverse’ buttons were added to the from for more convenient capabilities management while role editing.
– Role and capability name could be started from digit, and underscore ‘_’ character. Hyphen ‘-‘ character could be included into such name too.
– Old versions used ‘edit_users’ capability to check if show/hide ‘User Role Editor’ menu item under ‘Users’ menu. Starting from version 3.7 ‘administrator’ role is checked. Existed inconsistency, when non-admin user with ‘edit_users’ capability saws ‘User Role Editor’ menu, but got ‘Only Administrator is allowed to use User Role Editor’ error message, was removed.
– Bug fix: if you work with WordPress admin via https, URE will use https instead of http, as it made in older versions.
As new text was added to plugin main form, translations for all languages wait for updates. Former and new translators are welcome!
[nothankyou]
Capabilities set for Custom Post Type
Sunday, June 10th, 2012Yes. Custom post type may have custom capabilities set defined and it could be fully different from the standard post capabilities set.
What variants do you have?
1st, – use plugin which can manage not just custom post types, but custom capabilities set for those custom post types too. Good example is Custom Post Types UI WordPress plugin. I used it myself long time at my personal Russian language site FiNovel.com. Inspite of little quant of “Works” reviews at WordPress plugins repository page, I confirm – it works.