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

I know most of you are patiently waiting for v3.0 but there are a couple of important fixes that need to be addressed with the current 2.9 version. They primarily affect new customers who are having trouble seeing their image thumbnails or current customers who use international characters and/or some currencies.

If your primary language is English, USD as your currency, and your thumbnail images are working fine, then you don’t need to bother with the upgrade unless you really want to.

When I started working on 2.9.3 last week, I wanted to make some other updates but I decided it was best to hold off. Once you add new code, it changes the position of all the text that needs to be translated which results in .po language files getting all messed up. I didn’t want to create more work for those who use ClassiPress in another language besides English and with 3.0 due out in January, it just wasn’t worth the hassle.

Read more

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

I know you are all patiently awaiting for the release of v2.9 so I wanted to give you a quick update. First of all, this release is going to be the best ever for ClassiPress and will really take this theme to the next level. Many of the features you have been asking for will be included which I will talk about more later.

The main focus of this release has been to address a couple of things. Primarily to build in the most requested customer features submitted in our Feature Request forum and to better organize the underlying ClassiPress framework and code. When existing customers get the latest upgrade, you will notice how some files have been moved around and additional directories have been created. This is not an attempt to confuse you or make things difficult when upgrading but rather to organize ClassiPress more logically so additional growth and features will be easier to add.

Read more

Hello ClassiPress customers!

As you probably already know, ClassiPress v2.8 was released on April 6th and includes many new features and enhancements. Unlike previous updates, this version is quite different infrastructure-wise and requires ClassiPress customers to carefully migrate their current classified ads.

So why did we make the big change?
ClassiPress was originally built without using WordPress custom fields which in the long haul, limits the growth and potential of the ClassiPress product. Version 2.8 has since moved all non-description field information into custom WordPress fields. This is a huge change but will benefit you and your ClassiPress instance down the road so you can take advantage of several new and upcoming features.

Read more