Tag: classipress upgrade

Version 2.9.3 is Now Available

  • 17 Comments

If you haven’t already noticed, yesterday ClassiPress v2.9.3 was released which is a general bug and security patch. There are no new features as we are saving those all for 3.0 which is due out towards the end of January (assuming everything goes as planned).

I felt it was important to fix several bugs in the 2.9 branch before taking ClassiPress to 3.0. When I first started working on 2.9.3 is was supposed to have only been a small release — mainly adding support for new PayPal currencies, fixing a mail function bug, and improving the discovery of the ad thumbnail image path. Well, I ended up spending many long days cleaning up and stabilizing the product which was much needed.

So should I upgrade or not?

That’s the question most of you existing customers will ask. To contradict myself from the previous blog post, “ClassiPress v2.9.3 Coming Soon“, I recommend all ClassiPress customers upgrade to v2.9.3 because of the fixes and small security issue. If you’ve done lots of customization and don’t want to redo them all after the upgrade, I recommend manually making the upgrade by looking at the changelog.txt included with the update.

Read more

Upgrading to ClassiPress v2.9.2

  • 11 Comments

Over the weekend a new version of ClassiPress was released bringing us to v2.9.2. For those of you who are still using v2.8, you’re sure going to love this update. It addresses many of the feature requests everyone thought was missing. If you haven’t already read about the new features, check out the ClassiPress Features page to understand all the new goodies you get for free.

If you are already using v2.9 or v2.9.1, the main difference (besides some bug fixes) is how the ad form works and looks. There were some people who were having trouble with the modal box form button (it just wouldn’t work) but others didn’t have a problem at all.

Myself and my developer spent many hours working with customers trying to troubleshoot and isolate the problem. We released one patch that fixed it for some, but I still was not satisfied until it was working for everyone.

Read more