|
| |
| |
| |
|

|
| Wordpress, PHP, MySQL hints, advices, reviews, plu |
| WordPress, PHP, MySQL, general WEB development and security articles, reviews from experienced web developer. Free plugins, code samples download. |
| Language: English |
| RSS Feeds for this Blog |
|
Statistics |
| Unique Visitors: 0 |
| Total Unique Visitors: 2680048 |
| Visitors Out: 461 |
| Total Visitors Out: 9153 |
|
|
|
| |
|
|
| |
|
| WordPress 3.3.1 Security Update |
| 2012-01-03 20:16:12 |
WordPress 3.3.1 is available. Version 3.3.1 is a security update and fixed 15 bugs. While I not met any bugs in version 3.3 myself (and you?) I have updated my blogs as soon I got message about this security update (it fixes a cross-site scripting vulnerability that affected version 3.3) available. The same thing is highly recommended for other WordPress blog owners....
|
| |
|
| Internet Explorer and JavaScript copyright problem |
| 2011-12-31 05:01:45 |
Yes, that was the former and noisy for almost every web developer browsers compatibility issue. There are no any problem with FireFox and Google Chrome. The only Internet Explorer (I tested versions from 6.0 to 8.0) automatically replaces '©' part in the '©_from_user_role' URL parameter name inside JavaScript code to the copyright © sign. That's invalid role name inserted into WordPress database and the whole user roles and capabilities list crashes as a result....
|
| |
|
| Show to author his posts comments only |
| 2011-12-25 09:40:35 |
When authors of your blog click 'Comments' menu item in WordPress backend they see all comments by default, not only from theirs posts. Yes it's not possible to do something with such comments (any actions are blocked in case are not a post author) but what the sense to see on all this mess and search comments from your posts to moderate inside full comments list? I think you agree, there is a little sense, if nothing at all.
Do you wish to show for your authors comments from theirs posts only?...
|
| |
|
| User Role Editor 3.3 is published |
| 2011-12-10 08:00:56 |
I published today version 3.3 of "User Role Editor" WordPress plugin. What's new in this version?
- New role can be created as a copy of other existing one.
- You can hide/show deprecated capabilties (level_1 - level_10).
- Users with "Administrator" role are not shown to other users with "list_users" capability.
- Plugin data cleanup is added - plugin options will be automatically deleted if you delete plugin via WordPress link.
- Some code enhancements are applied, e.g. optimization and using of WordPress API instead of self-written routine....
|
| |
|
| Phishing email to steal PayPal account |
| 2011-12-02 23:08:46 |
Checking email today morning I got warning about my PayPal personal information change. 1st thought which I should have: "Oh, my God! Someone compromised my PayPal account. I should go there and check, as fast as possible. Oh, I see paypal link right here in email text. Click it, input login credentials to check my account...". Can you have such thoughts in similar situation? I think you can. Do not hurry. This is very important at such moment - do not make stupid things. Scammer wait you will go this way and act by his scenario. Do not become a victim....
|
| |
|
| activate_plugins WordPress capability |
| 2011-11-25 23:43:39 |
Information about it at WordPress Codex is very brief: "Allows access to Administration Panel options: Plugins". But according its name this capability should allow at least activate plugins and may be something more. Where we can get right information about WordPress if not at WordPress's core source code? I made little investigation and wish to share with you its results in this post.
Summary: activate_plugins capability on the top of the mountain really gives user access to "Plugins" and "Installed Plugins" menu items of WordPress admin back-end menu system and let him activate/deactivate plugins one by one or applying bulk action to the set of selected plugins.
Let's look together under the WordPress hood and see on examples of WordPress 3.3 core source code how it's realized....
|
| |
|
| WordPress admin menu permissions |
| 2011-11-14 10:29:25 |
WordPress admin menu items access is restricted by special permissions or so-called capabilities. When you build new WordPress user role, it's useful to know what menu item is restricted by what capability. It is necessary knowledge to add/remove admin submenus from user role via adding/removing correspondent capability.
If you have some PHP knowledge and you are curious enough, you will find the most part of WordPress admin menu definition, including its capabilities, at WordPress core source code. But what to do, if you are not PHP developer? Even me caught myself that it is too tedious open wp-admin/menu.php file and find right piece of code every time in order to get needed capability name for the admin menu item to use it in own plugin or answer on plugin's user or site visitor questions. Why do not document this? That's the reason of this post was written. I hope it will be useful not for me only.
Look at the table below for the list of WordPress 3.3 admin menu items capabiliti...
|
| |
|
|
| Install latest NVIDIA driver on Ubuntu |
| 2011-11-06 02:13:11 |
Do you love your Ubuntu box? I’m too. Being loyal Ubuntu user, earlier or later you will meet with such scenario: you’ve bought powerful NVIDIA graphics card, inserted it into your PC box and tried to boot Ubuntu. What’s the <censored>?! Your new graphic card isn’t recognized by your loving Ubuntu box. It just hasn’t [...]...
|
| |
|
| WP Sanitize WordPress plugin review |
| 2011-10-29 23:55:42 |
I thought, how's that possible with size 2 Kb only to check security vulnerabilities? May be it uses some web service for that? What critical data plugin sends to external site then in order to make security test? So I went through the code and discovered that there is no any real or potential vulnerabilities checking in the current version of plugin. May be WP Sanitize plugin is still in developement? According to its site vibethemes.com author plans to add some new features for this plugin. If such, plugin description should include this information. Not all WordPress blog owners can look inside PHP code and check the real plugin functionality....
|
| |
|
| |
 |