Support » Plugin: Polylang » Is it possible to have multilanguage at the backend ?

  • Resolved miguelcortereal


    My next site will have a custom post type with a bunch of custom fields for registered users create posts.

    This will be done at the backend since it has all needed functionality to create and edit those posts by each user,

    For each type of user are defined roles and capabilities and everything seems working just fine, most of the backend is hidden so users only have access to what of their concern.

    Now the problem is: users may have different nationalities, so it should be provided different languages for backend.

    There are translations for theme and plugins, is there a way to get Polylang switching languages at backend ?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Chouby


    Yes there is an option in user profile.

    Using that option in user profile the backend languange changes.

    What is not changing to each language are the labels for name and description from those custom fields.

    I’m using Types plugin to create and handle those custom fields.

    Polylang strings translation settings strangely only include part of these labels for translation.

    I’ve managed to create a wpml-config.xml file with some of the labels fields using <admin-texts> but nothing get translated, neither the ones shown by types wpml integreation neither the ones included at wpml-config.xml

    The rest of backend is being translated, even other metaboxes with other custom fields for different purposes using at least one other plugin.

    Plugin Author Chouby


    You are right, user defined strings translations are not loaded on admin side. I just did not think to this 🙁

    I just uploaded a development version ( which should solve this.

    It’s breaking the site.

    To replace the old version by the one you made available, I’ve used at plugins options, deactivate and delete files.

    It deleted all plugin files and cleaned polylang data from database (didn’t expected it would clean database, BTW that’s good).

    Uploaded it all again and activated. Now it breaks the frontend

    Give an eye at this:

    Catchable fatal error: Object of class WP_Error could not be converted to string in /………………/wp-includes/formatting.php on line 1408

    Plugin Author Chouby


    It’s really strange that the update from 1.1.5 to provoques such an error. Could you look for a conflict with the theme or another plugin?

    Oh and yes if you proceed like this, you will delete everything. De-activating does not affect the database. Deleting removes all plugin data in database. All plugins should do like this. To update from one version to another one, you can just delete the plugin directory and upload the new one. This is the way automatic updates work.

    The error pointed previously upon activation of the version, shouldn’t be theme or any other plugin related.

    I’ve deleted the newer version, the same way i did before, deleting files and data and installed the previous 1.1.5 version. It resulted in the same error when loading any frontend page.

    Since backend was working, I reconfigured all polylang settings, posts pages, menus, media synchronization, etc.

    while doing this it started to work normally and the error was gone.

    Then deleted via FTP the previous version and uploaded the newer, it was ok too.

    My guess is, for some reason my database was messed at some point.

    Concerning the not translatable backend strings, that could be a resolved issue since I’m starting to see them translating.

    Plugin Author Chouby


    That will be hard to figure out why you got this error. Especially now it has disappeared. At least the initial issue is resolved.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Is it possible to have multilanguage at the backend ?’ is closed to new replies.