Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Europe/Madrid (GMT+01:00)

Tagged: 

This topic contains 3 replies, has 0 voices.

Last updated by Marcel 9 hours, 24 minutes ago.

Assisted by: Marcel.

Author Posts
November 18, 2024 at 9:58 am #16413909

danielJ-8

Background of the issue:
For the translation of a website, I am using a Translation Memory platform called Phrase that connects directly with WPML through a connector. Everything works fine and all post types can be translated, except for one called 'Centers'. There is another custom post type, which is built the same way, called 'Activities', that can be translated with no issues. I tried creating a custom XML file but I'm not sure how to do it.
Customer support from Phrase say they cannot help any further because this is a WPML configuration issue.

Symptoms:
In the Phrase folder for content available for translation, 'Activity Items' and the taxonomy for 'Centers' called 'Centers categories' are available, but there is no folder for the post type 'Centers'.
Take a look at this video:
hidden link

Questions:
Could you give me some hints about what can I do to make the 'Centers' post type available for translation?
Maybe configuring the custom XML file for the 'Centers' post type?
Or maybe reseting all translations for that CPT...
I can give you access to the site if you wish.
I really hope you can help me with this. Thanks!

November 18, 2024 at 5:10 pm #16416097

Marcel
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Madrid (GMT+01:00)

Hi,

The custom post type is already enabled for translation through an XML configuration, which is why you're seeing the "lock" icon in the settings.

I recommend first testing whether the content can be translated using the standard method. You can do this directly on the CPT by clicking the "+" icon or via WPML -> Translation Management. Once this works, we know if the issue is related to "Phase" which I'm not familiar with.

Best regards,
Marcel

November 18, 2024 at 6:11 pm #16416288

danielJ-8

The XML configuration is not enabled because there is NO lock icon in the settings. You see the lock icon beside other CPT, but not on the one I'm talking about.
Please see image attached.
I cannot use the standard method because I need to centralize everything inside Phrase.
How can I set up an XML configuration for that CPT?
Please help me.

Settings-‹-Claror-—-WordPress-11-18-2024_07_08_PM.png
November 19, 2024 at 8:28 am #16417994

Marcel
Supporter

Languages: English (English ) German (Deutsch )

Timezone: Europe/Madrid (GMT+01:00)

Hi,

Thanks for the information.

I cannot use the standard method because I need to centralize everything inside Phrase.

I understand. However, this method is intended as a quick test to confirm the CPT translation is functional. Once verified, you can delete it.

You can make the CPT translatable as described here, but I suspect it may not have an impact since WPML already has it enabled for translation.

The settings are identical on "1", which is the first option "Translateable".

        
           [custom_posts_sync_option] => Array
                (
                    [post] => 2
                    [page] => 2
                    [attachment] => 1
                    [wp_block] => 1
                    [vc_grid_item] => 1
                    [mc4wp-form] => 1
                    [wp_navigation] => 1
                    [wp_template] => 1
                    [wp_template_part] => 1
                    [popup] => 1
                    [popup_theme] => 0
                    [cookielawinfo] => 1
                    [acf-field-group] => 0
                    [thegem_pf_item] => 1
                    [custom_css] => 0
                    [customize_changeset] => 0
                    [oembed_cache] => 0
                    [user_request] => 0
                    [wp_global_styles] => 0
                    [thegem_qf_item] => 1
                    [thegem_title] => 1
                    [thegem_footer] => 1
                    [center] => 1
                    [wpcf7_contact_form] => 1
                    [equip] => 1
                    [thegem_gallery] => 0
                    [thegem_team_person] => 0
                    [thegem_client] => 0
                    [thegem_testimonial] => 0
                    [vc4_templates] => 0
                    [thegem_news] => 1
                    [tribe_venue] => 1
                    [tribe_organizer] => 1
                    [tribe_events] => 1
                    [tribe_rsvp_tickets] => 1
                    [ticket-meta-fieldset] => 1
                    [tribe_wooticket] => 1
                    [events] => 1
                    [acf-post-type] => 0
                    [acf-taxonomy] => 0
                    [totems] => 0
                    [product] => 0
                    [product_variation] => 0
                    [shop_order] => 0
                    [shop_order_refund] => 0
                    [shop_coupon] => 0
                    [shop_order_placehold] => 0
                    [tribe_rsvp_attendees] => 0
                    [tribe_tpp_tickets] => 0
                    [tribe_tpp_attendees] => 0
                    [tribe_tpp_orders] => 0
                    [tribe-ea-record] => 0
                    [deleted_event] => 0
                    [patterns_ai_data] => 0
                    [acf-ui-options-page] => 0
                    [wp_font_family] => 0
                    [wp_font_face] => 0
                )
                )

What I notice here is that the CPT "Activities," which you mentioned as functional, appears to be missing. It seems "Activities" has not been created as a standard CPT, as it does not show up in the provided WPML debug information. In contrast, "Centers" is a regular CPT like Posts, Pages, Products, or Events, but "Activities" is not. Could you clarify how "Activities" was created? This might show why "Centers" is not working on Phase.

Best regards,
Marcel