Skip Navigation

[Closed] Localization issue

The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.
This support ticket is created 11 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.

This topic contains 2 replies, has 3 voices.

Last updated by Amir 11 years, 11 months ago.

Author
Posts
#10905

I'm going to translate your plugin to czech - this is what Codestyling Localization reports about your plugin:

Loading Issue: Author is using load_textdomain instead of load_plugin_textdomain function. This may break behavior of WordPress, because some filters and actions won't be executed anymore. Please contact the Author about that.Textdomain definition: There are problems to find the used textdomain. It has been taken from existing translation files. If it doesn't work with your install, please contact the Author of this plugin.Textdomain definition: There are problems to find the used textdomain. It has been taken from existing translation files. If it doesn't work with your install, please contact the Author of this plugin.

#10962

Hi Tomas,

Is this actually causing a problem with doing the localization. We have localized the plugin to several languages without a problem.

The load_plugin_textdomain is just a wrapper around load_textdomain that handles locating the files in the plugin directory.

You can safely ignore this message from Codestyling Localiation.

Best regards,
Bruce.

#10975

Amir
Supporter

Types and Views load two textdomains, because they have some shared code. I'm pretty sure that this will confuse Codingstyle. There are .po files under embedded/locale/orig for Types and Views. If you translate them, save the resulting .mo file to embedded/locale and everything will work.

The topic ‘[Closed] Localization issue’ is closed to new replies.