Please Help it doesnt work :(

Resolved queeneve
(@queeneve)

11 years ago

Here is what I did

1- Installed and activated Loco
2- Installed Wp User front end plugin
3- manage Translation and chose Arabic Language from the drop down list
4- Selected wp user front end plugin
5- Translated some strings and checked the language folder in the plugin folder has 766 permission (so it is writable)
6- I clicked on Save then Sync
7- Checked the content of the website , nothing changed

I tried many times but it never worked , I even installed a clean wordpress but still doesnot work so that means no conflict with another plugin

please help

https://wordpress.org/plugins/loco-translate/

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

Thread Starter queeneve
(@queeneve)

11 years ago

Seems here is the problem ,

Plugin does not declare a “Text Domain” .. Loco has guessed “wp-user-frontend”

I read your reply on this topic https://wordpress.org/support/topic/i-translated-the-plugin-but-the-language-does-not-change?replies=4

but I still dont understand how to do it , if you dont mind could you please tell me in another way how to solve this problem

Now I have 3 files
wp-user-frontend-ar.mo
wp-user-frontend-ar.po
wp-user-frontend.pot

How to use them ?

Thanks
Plugin Author Tim W
(@timwhitlock)

11 years ago
The Text Domain for this plugin is wpuf.

Automatic text domain detection is unreliable in Loco Translate, because there are too many non-standard ways a plugin can be set up. I intend to fix this at some point if possible, but for now your choices are to wait for improvements or alter the plugin to make it compatible.

Two (or three) things should be done to make this particular plugin compatible, but this will alter the plugin, so the author should make these changes and publish an update (otherwise you risk losing your changes).

1. Declare the text domain headers in wpuf.php, like this:
```
/*
Plugin Name: WP User Frontend
Text Domain: wpuf
Domain Path: /languages/
...
*/
```
2. The file languages/default.po isn’t a proper language template file. It should really be a POT file called languages/wpuf.pot

3. (optional)
The plugin uses load_textdomain to load translations which means it won’t load your files if they’re in the global languages directory (which they should be). The author should use load_plugin_textdomain instead.

This should make the plugin compatible. I’ll reopen this ticket if it doesn’t.
Thread Starter queeneve
(@queeneve)

11 years ago

Thanks for your quick helpful response it is now working fine only the optional step as I dont know how to do it and the coder is not active , will this affect the plugin in case no updates happened in the future or it is ok like that

Thanks again for your help

Plugin Author Tim W
(@timwhitlock)

11 years ago

If there are no updates in future then you might be safe saving your translations inside the plugin. Of course you can’t guarantee whether there will be updates or not.

Just make sure you back up your changes and watch out for plugin updates. If it does get updated, you’ll have to restore your changes back in.

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

The topic ‘Please Help it doesnt work :(’ is closed to new replies.