Separate front-end and back-end language strings

  • Resolved apollosk

    (@apollosk)


    8 years, 3 months ago

    Is it possible to split the language file into two separate files, one containing the front-end language stings (which are seen by the customer) and one containing the back-end language strings (which are seen by the admin)? I’d like to translate only the front-end in the local language and keep the back-end in English. Can this be achieved? Thank you in advance!

    • This topic was modified 8 years, 3 months ago by apollosk.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    8 years, 3 months ago

    Hey @apollosk,

    Hope you’re well.

    Actually, there is a WordPress trick about that. For example, when you install language files for MarketPress for other than English and set the site language to the same language everything will change along with frontend. But when you select your profile language to back English all your backend will return back to English without touching frontend.

    I hope that helps!

    Cheers,
    Oguz

    Thread Starter apollosk

    (@apollosk)

    8 years, 3 months ago

    Hi @wpmudev-support8,

    Thank you for your reply but it was not what I was looking for. I was wondering if there’s a chance to know in advance what language strings are used on the front-end so I can translate only those, because there’s no need to translate the admin part.

    Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    8 years, 3 months ago

    Hey @apollosk,

    Hope you’re well.

    Thanks for the extra information. There is no way to determine frontend texts only for language files. But I am still thinking the above way can solve the problem, you can translate whole plugin and still can use backend as English.

    But if you are trying to avoid translating backend time, I am sorry but it looks like not possible.

    Cheers,
    Oguz

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Separate front-end and back-end language strings’ is closed to new replies.