This thread is resolved. Here is a description of the problem and solution.
Problem:
Views by default disables the Avada CSS and JS compilers to create files for dynamic theme styles (they are inlined instead), but the client doesn't want that.
Solution:
When Avada is active we have now added a setting for this at Toolset > Settings.
This support ticket is created 6 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
We understand that some clients may not want to and are adding the ability to disable disabling the Avada compilers. The work looks complete, but from the internal tickets its not clear when the update should be available, I'm asking now for clarification, and I'll update you soon.
Disabling the Avada CSS and JS compilers was required for adding Avada theme options to Toolset templates, and if you choose to re-enable them then Avada theme options set on Toolset templates won't work reliably.
I updated layout and activated the compiler setting.
But my problem still exists that it does not work with my change to "wp_enqueue_style" ....array( 'avada-stylesheet' ) );... works. .....array( 'fusion-dynamic-css' ) );.... does not work. And I need this to have my css be loaded after the avada dynamic css.
Got this from here: hidden link
And it works perfectly fine until views is activated.
I tested this and the setting to use the Fusion Compiler is only available when using Layouts, not when just using Views, so Views goes ahead and disables it and inlines the dynamic stylesheet in the header, which means when you try to enqueue your stylesheet dependent upon it the dependency is missing and your stylesheet isn't enqueued at all.
I'm escalating this so my colleagues can take a closer look. It may be possible to use some hook to disable disabling the Fusion compiler ahead of a fix to the options page, but I'll need clarification on that.
I edited your Avada settings (Avada > Theme Options > Advanced > Dynamic CSS & JS) to use Files (otherwise there is no fusion-dynamic-css file which your code to modify enqueuing the child theme CSS uses).
I edited the functions.php of your child theme to re-instate your enqueue code.
Now when I visit the front end and inspect the page source I see that the child theme style.css is loaded *after* the Avada dynamic CSS file, which I think is your intention.
