Global Elements in Avada Display in Default Language

Overview of the Issue

After translating a post that contains global elements from the Fusion Builder in Avada theme, content appears in the default language instead of the translated language.

Workaround

This issue is fixed in Avada 7.2. Updating solves it on your site, so you only need this workaround if you can’t update yet.

Edit the wpml-compatibility-plugin-fusion-global-element-hooks.php file found in the wp-content/plugins/sitepress-multilingual-cms/compatibility/fusion_builder/ folder and add the following code:

add_filter(
	'the_content',
	[ $this, 'translate_global_element_ids' ],
	self::BEFORE_ADD_GLOBAL_ELEMENTS_PRIORITY
);

… just after this code:

public function add_hooks() {
	add_filter(
		'content_edit_pre',
		[ $this, 'translate_global_element_ids' ],
		self::BEFORE_ADD_GLOBAL_ELEMENTS_PRIORITY
	);

Still Seeing This Issue?

If updating doesn’t fix it, ask a support question and we’ll look into it with you.

Ask a support question

All known issues