- Required WordPress version checking is moved to plugin activation hook and is not called every time when plugin is executed.
- Administrator can now exclude non-core (custom) capabilities from his role. It is useful if you need to fully remove some capability as capability deletion is prohibited while it is used at least one role.
- bbPress compatibility issue is fixed: capabilities created by bbPress dynamically are excluded from the capabilities set in User Role Editor to not store them in the database as persistent WP roles data or user capabilities.
- Additional roles are assigned to user without overriding her primary WordPress role and bbPress role.
- Changing WordPress user primary role at user profile doesn’t clear additonal roles assigned with User Role Editor earlier.
For the 1st glance, “Post views stats” plugin does its work honestly, quickly and effectively. But after looking inside plugin source code I changed my opinion. Let me explain, why it was happend.
Just look on the list of security issues which WordPress 3.5.1. release addresses:
- A server-side request forgery vulnerability and remote port scanning using pingbacks. This vulnerability, which could potentially be used to expose information and compromise a site, affects all previous WordPress versions.
- Two instances of cross-site scripting via shortcodes and post content.
- A cross-site scripting vulnerability in the external library Plupload.
Are you still waiting? Go-go-go! Go to your WordPress update center, and press update button. Do not forget to make files and database backup before update, of course.
Detailed information is available at WordPress News page.
New feature “multiple roles” selection is realized. You can assign to user more then one role now. If role1 has capabilities A and B, but role2 has capability C, but you need to give user all three A, B, C capabilities, there is no need to create new 3rd role with all those A, B, C capabilities included. Just assign to the user role1 and role2 simultaneously. As the result user will get the combination of capabilities from both those roles.
While playing with a new developed stuff I discovered the bug, which could be critical in some conditions.
Existing WordPress permissions system doesn’t allow to realize such model. Yes, WordPress prohibits author to edit or delete posts and items of other authors, but she still see all that stuff. It’s slightly inconvenient, isn’t it?
“View Own Posts Media Only” WordPress plugin includes a set of useful hacks (don’t panic that’s just a legal code snippets, nothing from the dark territory of hackers, crackers and other malware manufactures) to offer you desired features, I wrote above.
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.
Is your WordPress blog opened for new user registrations? If “YES”, then you are familiar with a lot of users registered every day. But the most of those users do not login, do not make posts. It seems that there are no real users behind such registrations. All these contacts like:
- “yqvcevsjc (firstname.lastname@example.org)”,
- “ymmoncmn7 (email@example.com)”,
- “www.cheap-some-best-and-beautiful-garbage.com (firstname.lastname@example.org)”, etc.
are SPAM registrations obviously. These fake users at WordPress database cost you a time to delete them, create the mess from your lovely users list, so you (and me together with you) have strong desire to Stop SPAM registrations. Do You?