Over the holiday I released a new plugin called WP Feature Disable. This new plugin is designed to help put a little more control in the hands of the user to disable certain features of the WordPress platform that may be unnecessary or undesirable for a specific installation. While it currently only provides 5 options, more will be added as the plugin continues to evolve. » Read the Rest
Update:
AWeber Registration Integration version 1.2.8 was released tonight fixing a few concerns with the unique function naming methods to help avoid conflict with other plugins which might use similar functions. Also addressed were some of the issues surrounding the Opt-In display feature.
A big thanks goes out to Jim G. and Roger E. for their help identifying some bugs and wonderful suggestions! » Read the Rest
Administrative Options
Every once in a while you come across a feature or two that at the beginning seems really neat, but after a little while you realize things could run smoother or more efficiently if that feature wasn’t there. WP Feature Disable is the saving grace when it comes to getting rid of certain WordPress features. The idea is not to disable or harm the blog, but to simply help it be more efficient, use less database space, or simply hide so-called ‘nag’ screens. Turning features on and off is as simple as clicking a check-box and to make things better, nothing is permanent in case you decide you want that feature back later! » Read the Rest
Well it seems to be that time again to update your WordPress blog to fix two security vulnerabilities that were found in the previous 2.8.5 version. Most of you out there who use WordPress as your own personal blog and do not allow any of your registered users to post are not really affected by this. It seems that the vulnerabilities can only be exploited by registered and logged in users with posting privileges. Like usual though, no one says it better than the fine folks over at WordPress… » Read the Rest
Update for November 2nd, 2009:
Well after a receiving a note from James C. today mentioning BlueHost has again changed their policy on the domain privacy offerings, I decided to stop over at the BlueHost website and check it out for myself. After looking at the product breakdown I noticed that domain privacy was yet again marked as included, as it previously was before my July 21st post below. Seeing this certainly put a smile on my face but I was still unsure just how far this carried over since the domains on my account did not reflect this same change. Opening up a quick Live Chat window had my questions answered in less than 2 minutes (unheard of with my experience elsewhere). The response I got as to what domains the free privacy did, and did not, apply to was this: » Read the Rest