We have a problem translating a button on our Avada website.
Our Avada button uses ACF data as a dynamic parameter for the url and content.
On the original language, everything works fine, but in the translated page, there is no href.
The ACF data is translated correctly, we can show that content using a text block with dynamic content, and it shows fine.
However, the "dynamic_params" attribute of the "fusion_button" doesn't seem to be translated correctly. The dynamic parameters are a base64-encoded: eg:
eyJsaW5rIjp7ImRhdGEiOiJhY2ZfdGV4dCIsImxpbmsiOiIiLCJmaWVsZCI6ImUtbWFpbF9hdXRldXIiLCJiZWZvcmUiOiJtYWlsdG86IiwiYWZ0ZXIiOiIiLCJmYWxsYmFjayI6IiMifSwiZWxlbWVudF9jb250ZW50Ijp7ImRhdGEiOiJhY2ZfdGV4dCIsImVsZW1lbnRfY29udGVudCI6IiIsImZpZWxkIjoidm9vcm5hYW1fYXV0ZXVyIiwiYmVmb3JlIjoiTWFpbCAiLCJhZnRlciI6IiIsImZhbGxiYWNrIjoiIn19
=>
{
"link":{"data":"acf_text","link":"","field":"e-mail_auteur","before":"mailto:","after":"","fallback":"#"},
"element_content":{"data":"acf_text","element_content":"","field":"voornaam_auteur","before":"Mail ","after":"","fallback":""}
}
But the advanced translation editor shows the element_content.before value of the decoded content, instead of the base64-encoded hash.
For the fusion_social_links shortcode, it shows the dynamic_params correctly as en encoded value.
The wpml-config.xml of Avada doesn't tell WPML to decode the attribute:
fusion_button
link
title
dynamic_params
I can't find any config that tells WPML to base64-decode the dynamic_params of the fusion_button shortcode.
Can you help us fix this problem?
Symptoms:
On the translated page, there is no href for the button, and the advanced translation editor shows the 'element_content.before' value instead of the base64-encoded hash.
Questions:
Can you help us fix the problem with translating the 'dynamic_params' attribute of the 'fusion_button' shortcode?
主题 “[關閉] Translating buttons with ACF parameters using Avada” 已关闭，不接受新回复。
