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.

So v2.9.2 now has the sliding jquery form which is actually the original one CP used (what v2.8 uses). It will be the supported ad form going forward so it’s highly recommended you upgrade from any flavor of 2.9 to 2.9.2 immediately. If you’ve made any changes to your CP theme, I advise you to bring them over into v2.9.2 instead of trying to upgrade your existing v2.9 or v2.9.1.

View the changelog.txt file included in the download and you’ll see the exact changes and files affected. The /classipress/classifiedform directory has also been removed and replaced with process_form.php and post-form.php in the CP root which is how v2.8 was structured.

Upgrading from v2.9 or v2.9.1

1. Download and unzip v2.9.2. You can get the latest version by clicking on your original e-junkie email link. If you deleted or lost the email, contact me and include the email address you used to purchase CP (your PayPal email address). Please don’t be lazy and actually look for the original email first before contacting me.
2. Put your site in maintenance mode. Download and install this plugin if you don’t already have it.
3. Turn off any WP Cache plugins such as WP Super Cache (if applicable).
4. Rename your existing ClassiPress theme folder to “classipress_OLD”. This will essentially turn off your CP theme and use the default WP theme.
5. FTP only the v2.9.2 “classipress” folder into your themes folder. Also FTP the contents of the “plugins” folder to your WP plugins folder. Skip if you’ve already got the latest plugins.
6. Now go and activate v2.9.2 from within WordPress. You will see two that look exactly the same. Pick one and activate it. If it says v2.9.2, then you selected the correct one. If not, activate the other one.
7. Step through your CP config, settings, and payment pages and save each one. Your settings will still be the same as what you previously had before (except maybe the color scheme).
8. View your site and try submitting a new ad. You will notice the form is different than what you previously had.
9. If everything looks ok, then delete your test ad and turn off maintenance mode. Activate your cache plugin (if applicable).
10. If you were using CP in a different language (i.e. using a .mo file), you will need to update your classipress.pot and regenerate a .mo file. Read below for more details.

Upgrading from v2.8, v2.8.1, v2.8.2

This upgrade will be a little more involved for those who are using the 2.8 version series. The good news is there are a lot more features and benefits in the latest release. If you haven’t already read about them, check out the ClassiPress Features page to understand all the new goodies you get for free.

1. Follow the first 7 steps above.
2. When you get to step #7, make sure to review the new options on each of the ClassiPress admin pages. You will see lots of new features which will need to be setup and saved. If this isn’t done correctly, you will have problems with the ad submissions. CP admin pages (configure, settings, payment) must be saved first.
3. There are three new pages you need to setup to create the dashboard, profile, and ad edit functionality. Detailed instructions can be found within the install guide in the “User Dashboard & Profile Setup” section. Please read it carefully before asking for support. Most questions asked are because people didn’t read everything.
4. Now continue with steps 8-10 listed above.

ClassiPress in your language

If you are already using ClassiPress in a different language you will need to update your .po and recreate your .mo file. There is new text in v2.9.2 that needs to be translated and some text has moved to different lines. If you do not do this, your upgraded CP will not translate the text properly and look funny on your site.

Once you receive the new v2.9.2 .pot file, you need to open your existing translated .po file (i.e. pr_PR.po) in POEdit and select the “Update from POT file” option under the “Catalog” menu. Point it to the v2.9.2 .pot file and PoEdit will show you what text is new and needs to be translated. After you have translated the new text, save the project and then it will create your new .mo file. Overwrite your old .mo file in your /themes/classipress directory and look at your site.

Questions or comments

If you have any support or upgrade questions, please post them in the online support forum and NOT the comments section below. You can use the comments section below for general remarks or to thank me for spending my entire weekend preparing the upgrade for my customers.

I am sure you will enjoy this update as it addresses the most popular requests from everyone. ClassiPress has come a long way since it’s inception last year and you can expect it to evolve even further!

Don’t have a .po or .mo file for your theme or plugin yet? Follow these steps on how to generate your first WordPress .pot file. Another good article with resources about how to translate WordPress into your language is located here.

So what the heck are those .mo, .po, and .pot files anyhow and why are they included in my download?

Well, the files aren’t really important if English is your primary language but if you want to have WordPress, a WordPress theme, or even a plugin localized in your native language then those files are golden.

• .mo stands for Machine Object
• .po stands for Portable Object
• .pot stands for Portable Object Template

The file that you want is ideally a .po file since it’s the raw editable text scraped from the entire WordPress theme/plugin. The .mo file is the compiled export of the .po file which is used by WordPress.

Here are the steps to translate/localize a .po or .pot file into another language

1. Download a gettext file editor like poedit and install it.
2. Open the English .po file that came with your WordPress theme or plugin with poedit. If you only got a .pot, just rename it to .po and open it in poedit.
3. Now go through and translate all the text one line at a time in the bottom box.
4. Then “File” => “Save as” to your desktop or a folder on your computer. This will output a .po and .mo file.

As you can see from the screen shot below, the top part of the file contains the entire list of text that needs to be translated. Each line represents a place within the WordPress theme or plugin that stores the text. If you click on different lines, you’ll notice the section below displays that exact line of text. What’s even cooler is if you right click on any line, you’ll see a file name and line number like “comments.php line 121″. That is the exact place in the theme or plugin where this text is being used.

Now here’s where you need to pay attention. The blank box below that is where you will type in your translations. So in the screen shot I translated “Page not found” into Spanish by typing in the correct translation in the box below.

Important Note: Some text characters need to be converted into html entities otherwise they will not display correctly. A very common example is a word containing an apostrophe or single quote (‘) which needs to be replaced with ' — for example, Chloe O’Brian should be written as Chloe O'Brian. Kind of strange I know but that’s just how the parser works. For a complete list of html entities, visit W3Schools.

One other thing worth mentioning. PoEdit might give you an error related to “% comments” while you try to save the file (usually when you have a K preceding it like in German, “% Kommentare”). Usually if you just ignore the error, it will save fine. I will try and fix that comment translation issue in the next release.

After you start making updates, you’ll notice the upper right portion of the file will begin to fill in. Once you finish the translation (make sure to save often), you will have your final raw file.

Now that you’ve completed your translations, you can plug-in your file and see if it works. The .po file is your editable file which you can always load back up in poedit and update. The important file is the .mo file. This is what WordPress will use and if it’s for a new theme like ClassiPress, it needs to be placed in the /wp-content/themes/classipress directory.

I also forgot to mention that the naming of your .mo files is very important and must match the desired locale otherwise it won’t work. The naming convention is based on the language code (e.g. pt for Portuguese) followed by the country code (e.g. _BR for Brazil). So, the Brazilian Portuguese file would be called pt_BR.mo. See the complete list of language codes and country codes to find your exact locale.

You will also need to make a change to your WordPress wp-config.php file (located in your WP root directory) with the correct language codes like the example below. If you don’t have a WPLANG entry then create one.

define ('WPLANG', 'pt_BR');

Assuming you’ve made all these changes, you should now be able to reload your WordPress theme and see it in your native language! If it’s not working, chances are you didn’t use the correct naming conventions for your .mo file or in your wp-config.php file. If you see part of your site translated you either didn’t translate the entire .po file or the .po file wasn’t completely translated correctly in the first place.

So if you recently purchased ClassiPress and a language pack file (.mo) is not available for your native language, you should follow the steps above and create your own. ClassiPress is designed to work with virtually any language so just take the included .po file and translation away! Make sure to contact me and send over a copy so others can download your language pack. You will get full credit for the work and a link back to your site in return.

How to Update an Older .POT File

If you’ve previously translated an older version of ClassiPress and upgraded your site to the latest version of ClassiPress, you’ll notice the translation file no longer works correctly. This is due to the fact that the ClassiPress code has changed and the old .mo language file can no longer find the text locations.

Before I explain how to update your old language file to include the latest text to translate, I wanted to go behind the curtain and show you how it works. The .POT file is essentially a mapping of which text should be replaced in what file. It keeps track of this by file names and line numbers. When the ClassiPress code changes, it moves the line numbers so the .MO file can no longer find the original text to translate. To better understand what I’m talking about, open the .POT file with a text editor. You’ll see a bunch of readable lines that look like this:

#: 404.php:24
msgid “Whoops! Page Not Found.”
msgstr “Whoops! No se pudo encontrar la pagina.”

The first line tells the language processor what file (404.php) and line number (24) the text to be translated is located on. The “msgid” is the actual text that needs to be translated and the “msgstr” is the new translation (in this case, Spanish). Pretty easy once you understand how it works, huh?

Ok, so let’s talk about how to update your old ClassiPress.POT file.

1. First open your old existing translated .POT file (i.e. pr_PR.po) in POEdit. “File” => “Open”
2. Next you’ll need to compare it with the new .POT file. Do this by going to “Catalog” => “Update from POT file” and select your new .POT file.
3. Now PoEdit will show you what text is new and needs to be translated. It should also update any other changes that have been made.
4. After you have translated the new text, save the project and then it will create your new .MO file.
5. Overwrite your old .MO file in your /themes/classipress/ directory and look at your site.
6. Also make sure you’ve activated the latest version of the theme (the one that the new language file came with)

Now that should be it. Once you know how to work with existing .POT files, doing the updates can be really easy.