some blocks look correct on the frontend, but empty in the backend.

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client reported that some blocks appeared correctly on the frontend but looked empty in the "edit page" view.
Solution:
We resolved the issue by performing several troubleshooting steps in WPML > Support > Troubleshooting. Here are the steps we recommend you try:
1. Remove ghost entries from the translation tables
2. Fix element_type collation
3. Fix WPML tables collation
4. Set language information
5. Fix post type assignment for translations
After completing these steps, please resave your Global language page and retranslate it. This should copy the selected fields to the translated language. Ensure you back up your data before proceeding.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.

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.

This topic is split from https://wpml.org/forums/topic/cannot-change-acf-custom-field-to/

Tagged: Bug

This topic contains 3 replies, has 0 voices.

Last updated by Daniel Borbas 9 hours, 4 minutes ago.

Assisted by: Kor.

Author	Posts
March 28, 2025 at 8:57 am #16871623
Daniel Borbas	Hi Kor, thanks a lot for looking into it! We have another issue, some blocks look correct on the frontend, but look empty on the "edit page" view - 1-minute video here where I explain, could you please advise about this, too? hidden link
March 31, 2025 at 7:59 am #16877842
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I've checked and I can see the issue you had there. Could you replicate the issue on our sandbox site here? hidden link . You can install the required plugins and themes to replicate the issue. Based on my observation, the first slider shows the selected cases, but on the subsequent sliders(repeater fields), cases are not selected as shown in the attached screenshot.
April 1, 2025 at 7:57 am #16881723
Daniel Borbas	Thank you for checking, Kor! I think the case studies are only populated when someone (me or the client) went in and manually added them. The set-up is pretty intricate, and I'm not the developer of this website, so I don't have the capacity to recreate it on the sandbox. But based on this, can't you report this as a bug to be fixed?
April 1, 2025 at 8:15 am #16881768
Daniel Borbas	I have another issue that is probably related to this one, could you please check here? hidden link Thank you! Daniel
April 2, 2025 at 5:29 pm #16888297
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for your response. I’ve reviewed the setup, and it looks like the Case Study Slider, which is a custom case study block, is also configured in the theme. I will need to escalate this further to our 2nd Tier Support and is it possible that you clone the site to another staging site so that we could use it for troubleshooting purposes?
April 4, 2025 at 3:39 pm #16898366
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your reply. I can't seem to import the duplicator copy to our cloudways server so that our 2nd Tier Support could check and troubleshoot it. Are you able to clone the site to a staging site on your server?
April 7, 2025 at 6:14 am #16902384
Daniel Borbas	Hi Kor, I unfortunately can't set up a staging site on my end - but why do I need to in the first place? I don't understand what the issue is: I have already provided the Duplicator archive, and you have successfully set up a local clone of the site. Why can't 2nd tier support do the same, or use your clone? Best, Daniel
April 7, 2025 at 6:23 pm #16905701
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your reply. Alright then, I will escalate this to our 2nd Tier Support with what I have and will come back to you once I've feedback.
April 8, 2025 at 7:03 pm #16910698
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. We still need more time to check on this and I will come back to you as quickly as possible.
April 9, 2025 at 6:53 pm #16915720
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thank you for your patience. I was able to resolve the issue by running some troubleshooting options in WPML > Support > Troubleshooting link. Here are the options I used: - Remove ghost entries from the translation tables - Fix element_type collation - Fix WPML tables collation - Set language information - Fix post type assignment for translations After running these options, I resaved the Global language page and then retranslated it. This action copied the selected fields to the translated German language. Could you please give this a try? Just make sure to back up your data before proceeding.
April 15, 2025 at 6:59 am #16931781
Daniel Borbas	Hi Kor, Thank you for figuring this out! I'm going to test this on a clone of the production website and will let you know if I run into any trouble. Best wishes, Daniel