Free Technology Tutorials

Update: See comment by Network Solutions in comments area.

It seems Network Solutions and WordPress may not be playing well together and, as usual with tech geeks, they’re both pointing the finger at each other. I don’t have the time or interest to follow all the links on the net to figure this one out, but if you are hosting WP (or any other php app for that matter) on a network solutions, then you may want to do a little research on this one…here are a few links to get you started.

http://news.techworld.com/security/3221030/network-solutions-hacked-again-after-mass-wordpress-blogs-attack/

http://blog.networksolutions.com/2010/we-feel-your-pain-and-are-working-hard-to-fix-this/

and, of course, it could just be you

http://www.security-faqs.com/wordpress-vs-network-solutions-vs-you-who-is-to-blame-and-is-your-blog-at-risk-from-a-database-hack.html

Oh, and on another note…look Moodle devs…long lines of text in this post with no spaces that actually wrap…welcome to 2010…keep working on it…you’ll eventually get there

Are you getting bombarded with SPAM accounts being created on your WordPress blog? Well, there are several techniques to find and remove them, the more complicated involves creating and executing queries in the database, but one simple technique is available right in the WordPress admin. This video illustrates a simple technique for finding and deleting SPAM accounts from your WordPress blog.

Note: The following is made available under GPL from http://codex.wordpress.org/GPL. It has been edited significantly from its original form. There is no guarantee this information is accurate…use at your own risk.
—————————————————–

My WordPress blog has been hacked; or at least I think its been hacked. What do I do now?

The WordPress Exploit Scanner plugin can help detect damage so that it can be cleaned up. Other things you should do:

• Change passwords for all blog users, including your own, with a role higher than Subscriber
• If you upload files to your site via FTP, change your FTP password
• Change your web hosting control panel (such as Cpanel) password
• Completely remove all current WordPress core code and re-install the latest version of WordPress
• Make sure you are only using trusted plugins and themes–those from wordpress.org or a trusted commercial developer
• Remove all unused themes and plugins
• Make sure all of your plugins and themes are up-to-date–it’s best to install new, clean copies of each theme and plugin
• Update your security keys in wp-config.php
• Search your entire web-directory (public_html directory, not just the WP directory) to ensure no other files are infected
• Check directory and file permission on your server. Typically, directory permissions should be 755 and files should be 644, but this will depend on your particular server environment.

If all else fails, contact me and I will quote you a reasonable price for fixing your site for you…I only work on Linux systems with Cpanel, or an equivalent control panel.

In a default install of WordPress, each time you edit a post or page, WordPress will automatically save your previous posts/pages allowing the possibility of reverting to a previous version of that post or page. This is a cool feature, but it can get a little ridiculous when you have dozens of previous versions sitting below the post–and taking up space in your db. As you can see in the following screenshot, with just a couple of edits to this post, I’ve already racked-up 4 revisions…by the time I finish editing, I’ll probably have a dozen or so…

Each of those revisions requires a separate record in the db. So, although this is a cool feature, it can significantly add to db bloat.  If you don’t really care to have all those revisions sitting around, or if you want to limit the number, WordPress does provide an option to change the default behavior allowing you to either disable revisions completely or allowing you to limit the number of revisions saved. To make these changes you do need to edit your wp-config.php file directly…currently, there is no option for doing this in WP admin.

Disable Post Revisions

To completely disable the revisions feature, add (or if already present) edit the following code to your wp-config.php file. The word (false) disables this feature.

define('WP_POST_REVISIONS', false );

Specify the Number of Post Revisions

If you want to keep the revisions feature, but limit the number revisions saved, then use the same code as above, but change false to the number of revisions you want to keep. In the example below, WordPress will keep the latest 3 post or page revisions.

define('WP_POST_REVISIONS', 3);