Isolating the frontend translation strings | General Discussion | Support Forum


Please consider registering

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —

— Match —

— Forum Options —

Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Isolating the frontend translation strings
September 13, 2016
11:55 pm
Noriko Brubaker
Forum Posts: 9
Member Since:
August 18, 2016
sp_UserOfflineSmall Offline
(As suggested, I am reposting this from the Support Questions forum)


This is a nice plugin.  I have a question regarding translation.  

I would like to translate the frontend of this plugin to Japanese for my primarily Japanese audience, but would like to leave the backend in English.  For all of my other plugins I have been using another plugin, Backend Localization, which allows me to switch the backend translations to English while maintaining Japanese on the frontend (as selected in the general settings).  One thing that is very frustrating though is that AWCP is the only plugin that is not switching to English in the backend with the rest of the plugins.  This is a shame because I found some decent translations of the plugin (entire) that I would like to use because they would save me a lot of time, but I cannot use them if the backend stays in Japanese (those working on it from the dashboard can only ready English).  Might anyone here have ideas as to why the AWCP is not switching to English on the backend with the rest of the plugins and suggestions how I can correct it?

The best solution would be for me to figure out why AWCP is not working with the Backend Localization plugin, as this would allow me to make use of existing translations instead of having to create my own.  However, if this is not possible I will have to create my own translations (.po and .mo files) of only the frontend strings.  If I do have to take this approach it would be very helpful to distinguish the frontend strings from the backend strings in the origina .pot file.  I looked through the file, but it was hard to easily parse out the two sets of strings.  Are there any ways in which I might isolate the frontend strings from the backend ones?  Maybe there are markers to distinguish between them or the file itself is separated between frontend and backend strings in a way that is not obvious to me?

I would really appreciate some insight here.  Thank you!


October 27, 2016
3:25 pm
New Member
Forum Posts: 2
Member Since:
October 27, 2016
sp_UserOfflineSmall Offline

Hi Noriko,


did you figured out what are the front end files for translation?

It seems that I'm running into the same problem as yours. My whole back end is in English and I would like to have the front end in Spanish.


Cheers Amigoo

October 28, 2016
2:03 pm
New Member
Forum Posts: 2
Member Since:
October 27, 2016
sp_UserOfflineSmall Offline

I have added this plugin:

Admin Language Per User

But it does no solve the issue. Back end is now in English except AWPCP. 🙁 

It would be very appreciated to get a list what I have to translate manually to change my back end language.


Cheers Amigoo

October 29, 2016
4:08 am
AWPCP Support

Forum Posts: 5202
Member Since:
September 4, 2013
sp_UserOfflineSmall Offline

Hi Noriko and Amigoo,

Hope this documentation helps

Forum Timezone: America/Denver

Most Users Ever Online: 163

Currently Online:
22 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Johnny B: 140

godie: 120

kerdezo: 99

laburke: 94


salvig67: 84

rude: 72

purplepaula: 72


gery: 71

Member Stats:

Guest Posters: 31

Members: 37864

Moderators: 2

Admins: 2

Forum Stats:

Groups: 1

Forums: 4

Topics: 6942

Posts: 30939

Newest Members:

Karin Bandarq, ubugitof, digi, Patty, pirin, tennillle, caramenggugurkanjanin, siyanda, Biruqq, Jheyson

Moderators: awpcp: 7530, AWPCP Support: 5202

Administrators: wpengine: 0, awpcp: 298

Skip to toolbar