WordPress recently released version 2.6.3 to address a serious security vulnerability in the snoopy library. It is important to note that AutoBlogged does not use the snoopy library to fetch feeds, and is not affected by this vulnerability. Nevertheless, we do recommend upgrading to version 2.6.3.

The easiest way to perform the upgrade is to download the files wp-includes/class-snoopy.php and wp-includes/version.php, replacing those already in your WordPress installation. We have tested with version 2.6.3 and have found no problems.

We are happy to announce that AutoBlogged v2.3 is now ready to download! Some of the updates in this version include:

• Improved user interface
• Many new features
• Many bug fixes
• Improved compatibility with other themes and plugins

Version 2.3 is loaded with new features, click here to see them all.

This really should be called version 3.0 but we thought we'd keep it as a minor upgrade so no one has to pay an upgrade fee!  What do we ask in return? Just that you all start participating more in the forums and keep on providing quality feedback!

You can download this update using your original 2.x download link. If you do not have this link, send us an e-mail at support@autoblogged.com and we can resend it.

We are committed to supporting our customers and improving AutoBlogged as much as possible, however we would like to request your help in reducing our support load so we can focus on adding new features!

If you run into problems with AutoBlogged, we suggest you try the following before creating a support ticket:

1. Try disabling plugins. Disable all your plugins to see if there is a conflict. There are thousands of plugins written by all levels of programmers and some simply do not play well with other plugins or with current versions of WordPress. If the problem goes away, add the plugins back one at a time until you find the culprit.
   
2. Try another theme. Some themes do not implement all features or they perform non-standard functions that we have not tested. Verify that the problem exists on any theme you use.
3. Keep updated. Before submitting a support ticket try updating to the latest version of WordPress and make sure you have the latest copy of AutoBlogged. You can always download the latest version using your original download link. Also, if you are using PHP4, we strongly recommend upgrading to PHP5 as we will soon be phasing out support for PHP4.
   
4. Check your feed. Try viewing your feed using the built-in feed viewer, validate it at www.feedvalidator.org, or download the XML and view it in a text editor. A surprising number of feeds out there simply do not follow the standards.
   
5. Check online help. You can browse the online help documentation at http://autoblogged.com/online-help/. You might also find the post template tester useful: http://autoblogged.com/docs/template-test.php.
   
6. Search the forums. A quick, search of the forums at support.autoblogged.com might turn up a solution. If you don't find it, you might want consider asking the question there so others might find an answer in the future.
   

If you still see the problem after these steps, we will do all we can to track it down. It is helpful if you give us as much information as possible and send your configuration if you feel comfortable doing so.

Here are some other tips to help you find solutions:

1. Try another host. If you have another web host available, check to see if the problem exists there also.
   
2. Search. Sometimes different plugins or scripts run into the same problems. A quick web search might turn up a solution.

We appreciate all the positive feedback we have received from our customers and we wanted to request some reviews. If you are happy with our product and a member of Digital Point, DNDorum, or NamePros forums, we ask that you post a quick review on one of these threads:

http://www.dnforum.com/f60/autoblogged-wordpres...
http://forums.digitalpoint.com/showthread.php?t...
http://www.namepros.com/scripts-for-sale/480617...