Claudia999 Posted October 5, 2022 Share Posted October 5, 2022 It's not so important but I have already searched for it several times... I can't translate the word (h1) "Settings" on settings page. Am I looking in the wrong place? Link to comment Share on other sites More sharing options...
opentype Posted October 5, 2022 Share Posted October 5, 2022 (edited) Just use the Quick Translation tool and edit it on the front end. Normally, I would prefer the View Word Key mode, but there are many pages of language strings that are returned for the language key “settings”. Edited October 5, 2022 by opentype Link to comment Share on other sites More sharing options...
Marc Posted October 5, 2022 Share Posted October 5, 2022 The language string itself in terms of this one is "settings". However as mentioned, changing this using quick translation will be the simplest here. There are guides on translations you may find helpful to you And Link to comment Share on other sites More sharing options...
Claudia999 Posted October 5, 2022 Author Share Posted October 5, 2022 14 minutes ago, opentype said: but there are many pages of language strings that are returned for the language key “settings”. Yes, I know them all 🙂 All of them are translated but it doesn't change this one. Link to comment Share on other sites More sharing options...
Marc Posted October 5, 2022 Share Posted October 5, 2022 Have you tried this with the quick translation tool? Link to comment Share on other sites More sharing options...
Daniel F Posted October 5, 2022 Share Posted October 5, 2022 There are probably 3rd party strings with the same key Link to comment Share on other sites More sharing options...
Claudia999 Posted October 5, 2022 Author Share Posted October 5, 2022 13 minutes ago, Marc Stridgen said: The language string itself in terms of this one is "settings". It's translated but not in frontend. Just now, Daniel F said: There are probably 3rd party strings with the same key Yes, there is another 3rd party string "settings". It's translated too, but in frontend on settings page is no change. Link to comment Share on other sites More sharing options...
Marc Posted October 5, 2022 Share Posted October 5, 2022 Have you tried this with quick translation? We could do with getting an answer to that first of all Link to comment Share on other sites More sharing options...
Claudia999 Posted October 5, 2022 Author Share Posted October 5, 2022 10 minutes ago, Marc Stridgen said: Have you tried this with quick translation? We could do with getting an answer to that first of all I tried both - first in ACP, then with "quick translation". No change. (And I'm confused about "This will affect only your account". I want translate "settings" for all users.) Link to comment Share on other sites More sharing options...
Daniel F Posted October 5, 2022 Share Posted October 5, 2022 The "This will only affect your account" means the quick translation feature (the ability to change the phrases), and not the changed language strings:) Claudia999 1 Link to comment Share on other sites More sharing options...
Marc Posted October 5, 2022 Share Posted October 5, 2022 It will enable quick translating only for your account (nobody else will be able to translate things themselves). It sounds like something isnt quite right there. What exactly is happening when you use quick translate? Edit: Apparently Daniel is quicker than me today 😄 Link to comment Share on other sites More sharing options...
Solution Daniel F Posted October 5, 2022 Solution Share Posted October 5, 2022 And once again, you can't translate it because of "Yes, there is another 3rd party string "settings". " The plugin author will have to change the key Claudia999 1 Link to comment Share on other sites More sharing options...
Recommended Posts