Background of the issue:
I translated my website from Czech to Hungary using WPML. Everything seems to work fine, but any dynamic custom data from Metabox fields in my custom posts are not showing. Working CZ page: hidden link. Hungary translation: hidden link
Symptoms:
Dynamic data from Metabox fields is not showing on translated pages.
Questions:
Why is the dynamic custom data from Metabox fields not showing on translated pages?
I double-checked your settings on WPML, and everything looks good there. I suspect that the issue is related to how the elements are rendered on the pages, but I'm still not sure.
Furthermore, I tried creating a copy of your website, to analyze it locally, but it failed consistently after multiple tries. In this case, please create a staging version of the website, so I can test and verify information without compromising the live one. Please keep the same user there, so you don't need to share credentials again. Send me the link here, when done.
you can do whatever you need in this build. Even though its a live website, its a new one with 0 traffic yet. I got everything backed up and can safely restore it if anything goes wrong.
Primarily we need to resolve why this is happening, because we planned to translate multiple websites with WPML and I dont want to deal with this each time.
It took me a while to understand your implementation. Next time, if possible, please be more descriptive of the source and organization of information - this saves us many interactions.
I've noticed that you are using field values to populate the Bricks template used to create the Glazed Pergola post you brought as an example (that took some digging and a lot of time). These fields must use the corresponding value in Hungarian translation of the template. At the moment, they have the same value as the original (check the attached image).
I'm not sure where this field names come from and where they can be found, since this is a Metabox feature, but you need to find the corresponding Hungarian field name, so it renders correctly on translations.
I couldn't find any scenario exactly like yours, where the fields are created with Metabox and inserted via Bricks Builder. Also there weren't any conflicts, as the behavior was the same with all unrelated plugins deactivated. In theory, the setup is correct, and it should be working. I also checked internally.
I suspect there's a broader compatibility issue involving the 2 plugins + WPML.
To verify that, I've created a Sandbox (testing website), with WPML Setup in 2 languages: EN as primary and Hungarian as secondary (the language choice is not really important here). You can access it here:
hidden link
Please install Bricks, Metabox, create a custom field (make sure it has the correct settings to be translated), insert it with Bricks on a page, translate everything and let me know how it goes. Here, only the minimum is necessary, so only one field in a page is enough. Please do not import or create anything not directly related to the issue. It's just a test.
I know this takes some effort, so I really appreciate your cooperation on this matter. Thank you.
I installed the bricks theme and created simple post template and filled it with basic metabox fields, followed the metabox guidelines same as before on the live site and this time it worked as it should.
Unfortunately I have no idea why, because I did it the same way as before. But least we know it works...
I will try to migrate and translate the website one more time from scratch following the exactly same process for the 3rd time and pray it will work this time, there is no reason why it shouldn't..
At least we know it really should work thanks to the sandbox example. Thanks for that.
I will try to migrate everything once more later this week and I will report the results. Please don't close the thread until then.
I finally managed to solve the problem. At least mostly. I migrated and translated the entire website from scratch. The dynamic fields weren't displaying because I translated them before the taxonomies. You need to translate the taxonomies first, otherwise the data won't pair correctly. I don't understand why it works this way and it's pretty stupid, when I add new taxonomy, I have to then delete the translation a do it again to pair it properly.
I only failed to translate the FAQ page, where the same problem kept showing (dynamic field string name) even though it was just simple post.
It also happened that when translating custom posts that had urls like carbo-1, carbo-2 etc., the order of the translated posts got messed up and the urls didn't correspond. Why did this happen? I had to manually rename 90 posts so that the URL addresses would match.
