Polylang and wpCasa

Some themes and plugins just work with Polylang. Others add functionalities to WordPress which need extra work to get a full multilingual experience. That’s, for example, always the case when the theme or plugin allows user defined strings. If you can translate them in the strings translations table, that means the plugin or theme author has made this extra work.

wpCasa is a WordPress theme framework dedicated to real estate websites. The authors were receiving a lot of request on how to make multilingual real estate websites. I myself had a support request fo wpCasa not latest than a week ago. So Simon Rimkus just announced a new extension to add multilingual support to wpcasa. And I am very glad that Polylang was chosen as the best multilingual plugin to make this happen.

Real estate is an international business. Therefore many real estate agencies run their websites in multiple languages. We get a lot of requests asking for the best solution to run wpCasa as a multilingual website and we used to recommend a few plugins. But some of them are complicated to install or to maintain. Others won’t translate the entire website (e.g. listing details, theme options).

After quite some research we found that the plugin Polylang is currently the best solution to create your multilingual wpCasa website. It is a very clean and easy-to-use plugin.

Visit the demo to see how it looks.


9 thoughts on “Polylang and wpCasa

  1. Frédéric

    I’m glad that wpCasa has got the multilingual feature, thanks to you.
    However, I have started to use WPML with wpCasa and now want to move to Polylang.
    So could you tell me about the process for the transition for my website (www.agenceducapdantibes.com) ?
    Thank you,

    1. Frédéric Post author

      I am aware that some people did this transition manually. That’s easily feasible as WPML and Polylang both use separate posts for different languages. However, if it is possible to do so for a small website with a few posts, it would be a huge boring task for websites with a lot of content.
      I am currently writing a new plugin which will automate the migration process. My goal is to have it ready for the end of the year. If you want to test it, I can send you a preview as soon as it is available.

      1. Frédéric

        Do you consider that a property entry as a post ? because I have 75 properties (+75 other entries for english version).
        I have however a very few blog posts and pages. If you recommend to use the script then I would be grateful.

      2. Frédéric Post author

        Yes properties are certainly custom post types. I don’t “recommend” to use the script. But if you can wait for a couple of weeks, accept to test it, and if it works, it will avoid you some boring tasks.

  2. Frédéric

    Hello Frédéric,
    I’d like to move to Polylang asap since I have a few issues of compatibility between WPML and wpCasa.
    So what do you mean by “huge boring task” during the switch ? Is there many actions to do per post ? If there is just a few then I can do it manually. So what are they?
    Also, if I install that plugin, is it a one way change ? I mean does it change the database so it will corrupt WPML ?
    Thank you,

    1. Frédéric Post author

      Activating Polylang (after de-activating WPML) should not corrupt WPML. Data are completely separate. However a database backup is always a good precaution. You will have to create your languages, setup your menus and language switcher. Then you will have to edit each page, post (whether it is a custom post type or not), category… to set the language and translations links. To set posts and pages translations links, you will have to use the post id (which you can easily find in the admin url when you edit it). You should be aware that as soon as you create a language, only contents associated to a language will be visible on frontend. Maybe you should test Polylang on a test site to see how it works before attempting anything on your live site.

Comments are closed.