Forum Replies Created

Viewing 4 replies - 31 through 34 (of 34 total)
  • Thread Starter tomdekok

    (@tomdekok)

    Perhaps, this is fun too! ??

    Thread Starter tomdekok

    (@tomdekok)

    Great!

    Well, what do you expect… It’s winter and it snows! :)))

    Thanks for the plugin and the update ??

    Tom

    If the above doesn’t do anything, then this might be the reason:

    Translated versions of WP seem to have a different way of defining language.

    Before, in wp-config.php language was defined like this: “define (‘WPLANG’, ‘nl_NL’);”

    But now it is defined like this: “define (‘WPLANG’, ‘nl’);”

    Since WP e-commerce checks the language of WP to see which one to load, it doesn’t find the correct syntax and remains English, hard coded.

    If you want to change the language of WP e-commerce, you’ll have to change “define (‘WPLANG’, ‘nl’);” to “define (‘WPLANG’, ‘nl_NL’);” (or whatever your language code is. This means that WP itself will move to English again, since it doesn’t recognize the language code now. ??

    Perhaps renaming the language files of either correct setting will solve that, don’t know. But at least this is solved now beyond doubt ??

    Thanks,
    Tom

    Hello all,

    For those that are searching for a way to change the language for wp e-commerce, here’s how:

    1. Go to the /language directory for the wp e-commerce plugin.

    2. Create a new directory in it named “backup”, for example.

    3. Move all files in the /language directory to the backup directory, EXCEPT:

    a. the EN-en.php
    b. the MO and PO files for your language.

    That’s it!

    I have been searching for a way to change the language for half a day, until by accident I moved the language files that I needed back to the /language directory, after moving all other files away. That did it.

    I have no idea why this has not been documented, but to be very honest, since the developers sell docs and support, it seems they like to make a buck on these problems, instead of helping with these basic settings. Might not sound friendly, but considering the many, many people with this problem and no solution available, I cannot think of any other reason. Even a readme file in the directory would have helped many.

    For the .php files in the directory, they are no longer used and are there for compatibility reasons. The EN-en.php file that is left in the directory is called in the code but not used. I have removed everything in it and tested it, but it’s also only there for compatibility reasons.

    All the above works for the 3.6 and above versions.

    Good luck!
    Tom

Viewing 4 replies - 31 through 34 (of 34 total)