Before 6.7, we can place the properties file under webapp/locales, then web client load the plugin, it can find the proper properties file according to the locale value, but now, this mechanism seems not to be working any more.
The only way is set the resource file name and then place the resource file without locale in the name to the locales.
Just like the sample custom-object-ui, all the other samples are not working now.
<resources baseUrl="locales/"> <resource>com_vmware_samples_customobject</resource></resources>
Hi,
Here is how to declare localization resources in your plugin.xml
<resources baseUrl="locales/"> <resource>com_samples_myplugin</resource></resources>
Then you should have "locales" folder in your .war bundle where you should place your properties files. For example:
- com_samples_myplugin.properties (default properties bundle which is used when an unsupported locale is set)
- com_samples_myplugin_de_DE.properties
- com_samples_myplugin_fr_FR.properties
Regards,
Denis
Hi,
I have deployed some sample plugins on a 6.7 environment and it seems the localization is working fine on my side.
In order to investigate the issue, can you share more information about the client and version that you are using.
Any information about the client (build/version/type), about the plugin used (Flex/HTML/Hybrid) or any logs will help us.
Regards,
Denis
Hi,
I remember having some issues with the localization which were addressed in the next versions of the vSphere Client.
As a workaround for this version, can you try using a different browser or inserting "?locale=en_US" as a parameter in the URL and see if this helps.