Macarlos1

[Macarlos1]

Hi

Hmm strange. If it wouldn’t be in the relevant directory, I think that I wouldn’t be even able to see any translation updates partially as I do now. It seems like the problem is in some other area.

Let me try to finish translation first and produce *.mo files again. If that won’t help I’ll get back to you.

As per this threat. Please kindly keep it open, or if not possible – close it and I’ll open a new one if that won’t help either.

Thank you!

Karl

[Macarlos1]

Hi again,

Just wanted to let you know that it works.

Thank you for great support!

[Macarlos1]

Hi,

I’ve followed your instructions and it seems like it helped a bit as there are more sentences which I was able to translate now, though – on the other hand – there are still some parts that are in English despite of these actions.

If you look on screenshot “1”, there are some phrases that actually changed after translation.

In screenshot “2” and “3” however, there are still these which I’m not able to translate even if I delete and recreate each .po .mo and .pot file in appropriate location (as suggested by yourself) and set permissions to 777. All of these sentences I’m referring to at the moment (cause there might be more in other places) which are *untouchable*, are located in bottom section of profile page on my website.

I’ve searched through all of plugin translations in loco translate, and the only place all of these sentences exist is sweetdate theme .po and .mo.

Any idea what might be wrong here?

[Macarlos1]

Hi,

It seems like it works only partially. I mean, it allows me to translate sentences which were already uploaded along with the theme. There was about 10% of .po and .mo files already translated into Polish and when I’m making any updates they are visible on my webpage after I click save button and reload my webpage. For other sentences which doesn’t have a translation yet it doesn’t work for some reason. I’m translating the sentence, click save, reload my web page and the words are still in English.

Any clue on why this might be?

Example of that failed translation upload in the attachment.

[Macarlos1]

Hi k3m,

I’ve got a similar issue currently. My translations of Sweetdate theme are not appearing on the webpage. Could you let me know what have you done to solve your problem?

[Macarlos1]

Sorry to be a pain – my questions comes simply out of lack of knowledge…

Where can I find the place that would allow me to set up my values for these two fields?
Also – are there any other settings I should be aware of, to make this solution to work?

[Macarlos1]

I’ve made the updates as per your advise, though it seems like nothing has changes.

Please login to FTP and verify my update.

functions.php file that was updated is in the following location:

/wp_1/wp-content/themes/sweetdate/functions.php

The function was added to the very bottom of the file. I don’t have too much knowledge on PHP in particular, so it might be that I’m doing something wrong.

The other file as per your advice has been uploaded to: “/wp1/wp-content/themes/sweetdate/custom_buddypress/kleo-bp-search.php”

Current screenshot of webpage search field in attachment.

(?) Please also check line number 4 of the script – probably the word “Mężczyzna” should be updated as “Mężczyzną”. (?)

[Macarlos1]

In rush I’ve forgotten to establish access via IP’s from outside my country.
Credentials already sent should be working now. Could you still have a look, please?

[Macarlos1]

OK – I have set up the accounts you can use.

Couple of comments regarding Loco Translation plug-in that you should know. I’ve managed to made some translations of “BuddyPress” plug-in already and the updates are appearing on the webpage immediately. For Sweetdate theme it seems like *.po and *.mo files are in the wrong FTP location, so please keep that in mind if you make any updates. I wasn’t able to figure out where they should be placed.

The goal is to set each “Jestem” (English: “I am a”) field as:

Mężczyzną
Kobietą

and each “Szukam” (English: “I am looking for”) field as

Mężczyzny
Kobiety

Please let me know if you need anything more from my end. Also, thank you in advance for your efforts – it’s much appreciated.

FTP:
Server name: http://ftp.macarloslv.nazwa.pl
User name: macarloslv_kupidi-test
password: @Seventhqueen@

Wp-admin:
web page address: kupidi.pl
wp-admin address: kupidi.pl/wp-admin
login: kupidi-test
password: @Seventhqueen@

[Macarlos1]

I will work on it. Please keep this post open – I’ll get back to you as soon as I have one.

[Macarlos1]

Hi Andrei,

Thanks for your answer. The issue is a bit more complicated (yet solvable in my opinion), as there is no common wording to satisfy the need of this search in current configuration. Unlike in English, the forms of words in Polish are changing under different circumstances as you’ve mentioned. If functionality of these two fields is not separated to provide different outcomes, then the entire experience will going to be a bit odd. Since this is the number one feature which is going to be used by all potential users, I cannot afford it to look unprofessionally I’m afraid.

The split should work as follows.

Field – “I am a:”, (Polish: “Jestem:”) – needs to allow to choose only:

Mężczyzną
Kobietą

And the other one – “I’m looking for a”, (Polish: “Szukam:”) – has to give the following as the outcome:

Mężczyzny
Kobiety

Thanks!
Karl

[Macarlos1]

Hi Radu,

Yes, thank you!

Karl

[Macarlos1]

Hello Again Team,

I’ve apparently managed to solve the problem for myself. There is one very helpful too available on below webpage.

http://jsonlint.com/?reformat=no

Thank you anyway.

[Author]

Posts