[Resolved] Avada Conflict with Latest version of Views

[Author]

Posts

[kristofG]

Avada Theme style not loading when views is active.

[kristofG]

I was wrong, the View is indeed currently in use on hidden link

[Shane]

Hi Kristof,

I'm still going through this one for you.

So far I can say there isn't a direct conflict between Toolset Views and Avada because on a fresh install both work fine and all the styling loads.

Perhaps you can setup a fresh install on your end and see if you can replicate the issue as well. However i'm still investigating for you.

Thanks,
Shane

[kristofG]

what do you mean with a fresh install? from scratch or from the duplicator package?

[Shane]

Hi Kristof,

What I did was to install your theme and views only on a clean install to check if its actually a conflict between the two.

Currently they work fine together and the frontend displays fine when views is activated so I would like for you to setup a brand new site with just the theme and views only.

Thanks,
Shane

[kristofG]

Hi Shane, as it is currently a very busy time, we manage about 100 clients as a web agency, I won't be able to quickly set up a brand new site. However, I have just created a staging site with the WP Staging plugin and disabled all but the Toolset Views plugin. I notice that the layout is also broken on hidden link with the Avada Theme but it is rather ok with the Twenty Twenty One theme.

Any idea how to find out what the issue is between Avada and Toolset Views? It seems when I set the CSS Compiling Method
in the Avada Options to Database or Disabled (instead of File), the site loads fine, even with Views activated. However, File works fine, when I disable Views.

[Shane]

Hi Kristof,

I believe I found the css that is not loading or that is being blocked from loading, its the "fusion-dynamic-css-css" not being loaded.

What I've done is to escalate this ticket to our 2nd tier supporters so they can have a look to see if they can find anything that i've missed.

I'll report to you once i've gotten any updates from them.

Thanks,
Shane

[Shane]

Hi Kristof,

Thank you for the continued patience.

Our 2nd tier supporters were able to have a look at this one for you and were able to provide a workaround on this.

To resolve this issue go to Avada -> Options -> Performance and under "Dynamic CSS & JS" select Database for the CSS Compiling Method and save the setting.

Refresh your webpage and see if the issue still remains, if it does set the Dynamic CSS & JS settings for CSS Compiling Method to Turn Off and then hit save.

Please let me know if this works for you.

Thanks,
Shane

[kristofG]

Hi Shane,
as you can read in my previous reply, I also found that workaround.
But as this is a workaround, I am looking forward to a final solution.

[Shane]

Hi Kristof,

Thank you, it seems that from our 2nd tier supporters investigation, our views plugin disable dynamic css as there is a line in our views for it.

/**
	 * Force Avada css mode to inline instead of file, this solves the problem with caching
	 */
	private function set_inline_css_mode() {
		if ( ! defined( 'FUSION_DISABLE_COMPILERS' ) ) {
			define( 'FUSION_DISABLE_COMPILERS', apply_filters( 'toolset_disable_fusion_compilers', $this->is_disable_compilers() ) );
		}
	}

Another solution that was suggested was to use the hook below.

add_filter( 'toolset_disable_fusion_compilers', '__return_false' );

Add the above to your functions.php file and it should resolve the issue as it disables the function in our plugin that would disable the dynamic css.

Please let me know if this helps.
Thanks,
Shane

[kristofG]

My issue is resolved now. Thank you!
But why would you need to hook into the Avada CSS compilation in the first place? I find it strange that a plugin needs to alter a feature for a specific Theme.