This user has no favorite topics.
Favorite Forum Topics
Forum Topics Created
|WPML and ACF not working as it should||2||5||2 months, 3 weeks ago|
| I can not cancel local translation jobs|
|2||5||2 months, 3 weeks ago|
|WPML + ACF using the default wordpress backend (no classic translation editor)||2||6||1 year, 3 months ago|
|Fields do not show up on translated pages in second language||2||4||1 year, 5 months ago|
|Table rate not showing on English version||2||2||1 year, 5 months ago|
|3rd language related products locked, but not showing products||2||4||1 year, 6 months ago|
|Too many redirects error or logged out when switching language in WP admin 1 2||3||22||1 year, 6 months ago|
|Split: Is it possible to get two sets of data (both languages) through Google analytics with the Monster Insights plug-in?||2||5||1 year, 7 months ago|
| Woocommerce product images not copying|
|2||5||1 year, 8 months ago|
| Payment text not translating and problems viewing the english version|
Once you have defined a string in the WooCommerce settings for the multisafe string, you go to the Admin Strings screen (via the link at the bottom of String Translation) and search inside the admin strings for the custom field of the description for the Multisafe Plugin settings for each payment option.
You have to register the string in String Translation and translate it from there, saving the translated string.
For this to appear and be registable, in WPML > Translation Management > XML Configuration you need to added the xml for these custom fields.
You may follow this example and use the corresponding strings for each payment:
<wpml-config> <admin-texts> <key name="woocommerce_multisafepay_maestro_settings"> <key name="description" /></key> <key name="woocommerce_multisafepay_mastercard_settings"> <key name="description" /></key> <key name="woocommerce_multisafepay_sofort_settings"> <key name="description" /></key> etc..... </admin-texts> </wpml-config>
For each new activated multisafe option you need to add a pair of entries that will be similar to the model:
Then paste that to the list of admin strings, save the XML and visit the page WPM > Themes and plugins localization. This will save that.
Then you go to String Translation and the translated versions will show in the frontend.
|2||8||1 year, 8 months ago|
|Duplicate entire site to language||2||2||1 year, 8 months ago|
| Split: Problems viewing the english version in woocommerce shop|
Site uses URLs in domains.
|2||5||1 year, 8 months ago|
|Product attributes are not editable||3||6||1 year, 10 months ago|
| Language switcher not working for archive page|
You can translate the slugs in a new CPT type following these steps:
When you create a custom post type with the plugin CPT UI (which is not fully compatible with WPML), you have to set the option "Rewrite" to "True" and put the URls of the default language in the "Custom Rewrite Slug" field.
To be able to translate the slug this field needs to contain a slug. If you want to use the default slug you can copy that there.
You can set the custom post field to be translatable in WPML. If the slug does not appear right away, publish a post in the default language and then check if the language metabox at the bottom shows the option to make that post translatable and put itfrom there.
Now check that you can translate the slug in WPML > Translation Management > Multilingual Content Setup and translate the slug. The problem here is that if this does not show correctly online, you need to enabled the same in String Translation.
If that does not work for any reason, there is the option to register the slug as an admin string in String Translation.
You have to go to String Translation and click at the bottom of the page to get to the admin strings screen.
There you search for the options that have the custom post type's custom rewrite slug. You should find them in the cptui_post_types.
You may also uncheck the "name" options for your custom types and custom taxonomies so you won't translate them by mistake as they should have the same value for all languages or you can get problems with the URLs.
Select the custom url and a label if you want and then scroll down to the bottom of the screen to apply. This will register the strings in String Translation.
In String Translation now you can search for the custom rewrite slugs that you just registered. Look for them under the "admin_texts_cptui_post_types" domain.
Translate the strings according to your needs and mark the translations as completed.
When it comes to translating custom taxonomies slugs, there are limitations of WordPress itself to translate the slugs for custom taxonomies in different languages. So the best option here is to use them like you do now or to use a neutral slug.
|2||12||1 year, 10 months ago|
|Custom fields not showing on some pages||2||4||1 year, 11 months ago|