Whenever you do an update customized options are almost always lost.
You can avoid having most customizations lost during updating by simply permissioning the file 444 as read only, then the update cannot over write your customization(s).
In some cases doing this will cause the auto update to fail, in this case you then want to FTP the update to the server which still preserves your customizations.
In rare cases it may still be necessary to over write your customizations to get the full effect of the update.
all due respect but you are missing the point and facts.
You did NOT protect your custom files before doing the update therefore the translation is lost and you will need to redo the translation. That is a fact unless you have it backed up somewhere?
and I suggested that in the future you permission the custom file or translation 444 read only so that it cannot happen again in the future.
It's not the first plugin i translate, and domain mapping can't be updated automatically, so i updated it manually, and i did not lost my translations, that are already on my server.
Then i have translated again plugin, and upload it again, and it's not working.
First I only mentioned earlier about automatic updates etc. because of their relation to using the read only 444 permission.
So your real problem if I understand correctly :-) is that you translated the new version of the plugin, uploaded the new translation, and it is not showing up as translated?
have you cleared your browser cache?
are you using cache in your WPMS and if so have you cleared that too?
Believe it or not I am really just trying to help you figure out what has gone wrong or where the problem is :-)
In addition, an attempt to help you so that you do not have your customizations over written during updates which is not always possible ..... but possible most of the time :-)
I think i have located where the problem come from.
I have uploaded domain-mapping.php form version 3.0.5 and i can see my translation, with domain-mapping.php from 3.0.7 version, it's not working.
domain-mapping.php:869
I have replaced
$domainmap_dir = trailingslashit(WPMU_PLUGIN_URL);
by
$domainmap_dir = trailingslashit(WPMU_PLUGIN_DIR);
And it's working now.
After checking our WPMS installation and the domain mapping files - I can see that the previous version of the languages translation was named domainmap.mo and the new version has named the file domainmap-en_US.mo
Therefore it is my opinion you need to rename your old translated file domainmap.mo to the new name domainmap-en_US.mo and it should work :-)
GREAT job and I am happy to hear that you got this worked out :-)
As you can see I had found a discrepancy in the naming of the files protocol that I thought was jamming you up - and you found another possibility that works for you which is the most important thing :-)
It does look to me like it should be WP_PLUGIN_DIR and not WP_PLUGIN_URL. Let me seek clarification from the dev on that so we can get a fix if necessary.
Can you move your domain mapping plugin to /wp-content/plugins/domain-mapping and network activate it - then place your translation in the languages directory within that directory (may be best to download the latest version of the plugin again and upload the domain-mapping directory to your server).
- you'll have to delete the domain-mapping.php file from your mu-plugins directory before you network activate it from the plugins page.
Responses (16)
Support Kangaroo — 15th January 2012 #
Greetings puccino :-)
please clarify what translation text was translated?
for a post, a page, or content? for what please?
Joe :-)
Member — 15th January 2012 #
Translation of domain ampping plugin
Support Kangaroo — 15th January 2012 #
Greetings puccino :-)
I am sorry to hear that but it is expected.
Whenever you do an update customized options are almost always lost.
You can avoid having most customizations lost during updating by simply permissioning the file 444 as read only, then the update cannot over write your customization(s).
In some cases doing this will cause the auto update to fail, in this case you then want to FTP the update to the server which still preserves your customizations.
In rare cases it may still be necessary to over write your customizations to get the full effect of the update.
Joe :-)
Member — 15th January 2012 #
I updated via ftp, i have translated the plugin, and it's still in english.
Support Kangaroo — 15th January 2012 #
Greetings puccino :-)
all due respect but you are missing the point and facts.
You did NOT protect your custom files before doing the update therefore the translation is lost and you will need to redo the translation. That is a fact unless you have it backed up somewhere?
and I suggested that in the future you permission the custom file or translation 444 read only so that it cannot happen again in the future.
What do you not understand about this?
Joe :-)
Member — 15th January 2012 #
It's not the first plugin i translate, and domain mapping can't be updated automatically, so i updated it manually, and i did not lost my translations, that are already on my server.
Then i have translated again plugin, and upload it again, and it's not working.
Support Kangaroo — 15th January 2012 #
Greetings Puccino :-)
aha! now we are getting somewhere :-)
First I only mentioned earlier about automatic updates etc. because of their relation to using the read only 444 permission.
So your real problem if I understand correctly :-) is that you translated the new version of the plugin, uploaded the new translation, and it is not showing up as translated?
have you cleared your browser cache?
are you using cache in your WPMS and if so have you cleared that too?
Believe it or not I am really just trying to help you figure out what has gone wrong or where the problem is :-)
In addition, an attempt to help you so that you do not have your customizations over written during updates which is not always possible ..... but possible most of the time :-)
Joe :-)
Member — 15th January 2012 #
I think i have located where the problem come from.
I have uploaded domain-mapping.php form version 3.0.5 and i can see my translation, with domain-mapping.php from 3.0.7 version, it's not working.
Member — 15th January 2012 #
domain-mapping.php:869
I have replaced
$domainmap_dir = trailingslashit(WPMU_PLUGIN_URL);
by
$domainmap_dir = trailingslashit(WPMU_PLUGIN_DIR);
And it's working now.
Edit : i think it's a typo ?
Support Kangaroo — 15th January 2012 #
Greetings Puccino :-)
I think I have the answer :-)
After checking our WPMS installation and the domain mapping files - I can see that the previous version of the languages translation was named domainmap.mo and the new version has named the file domainmap-en_US.mo
Therefore it is my opinion you need to rename your old translated file domainmap.mo to the new name domainmap-en_US.mo and it should work :-)
Joe :-)
Support Kangaroo — 15th January 2012 #
Greetings puccino :-)
GREAT job and I am happy to hear that you got this worked out :-)
As you can see I had found a discrepancy in the naming of the files protocol that I thought was jamming you up - and you found another possibility that works for you which is the most important thing :-)
Joe :-)
Member — 15th January 2012 #
Now we need to hear dev about it, if it's a typo or not.
Sales & Support Pro — 16th January 2012 #
Hiya!
It does look to me like it should be WP_PLUGIN_DIR and not WP_PLUGIN_URL. Let me seek clarification from the dev on that so we can get a fix if necessary.
Thanks,
Phil
Support Chimp — 23rd January 2012 #
Hey guys.
Language translations in the new version of Domain Mapping can be added to:
wp-content/plugins/domain-mapping/languages/
There is some information about PO files in WP:
http://codex.wordpress.org/Translating_WordPress#Translating_With_Gettext_Tools
and
http://codex.wordpress.org/User:Skippy/Creating_POT_Files
Hope this helps.
Member — 24th January 2012 #
Yes, but it seems there is a typo on domain-mapping.php:869
Developer — 24th January 2012 #
Can you move your domain mapping plugin to /wp-content/plugins/domain-mapping and network activate it - then place your translation in the languages directory within that directory (may be best to download the latest version of the plugin again and upload the domain-mapping directory to your server).
- you'll have to delete the domain-mapping.php file from your mu-plugins directory before you network activate it from the plugins page.
Become a member