Skip Navigation

[Resolved] WP Views extension breaks Avada Fusion Builder & Fusion Slider

This support ticket is created 6 years, 10 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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 1 reply, has 2 voices.

Last updated by Luo Yang 6 years, 10 months ago.

Assisted by: Luo Yang.

Author
Posts
#592067
Screenshot at Nov 22 13-01-47.png

I am trying to get the latest version of Avada theme Fusion Slider and Fusion Builder to work with the latest version of WP Views. Both slider and backend fusion builder elements starts working immediately after disabling the WP Views plugin.

I've reinstalled both WP Views, Avada Theme and WordPress: unfortunately this did not resolve the issue.

Link to a page where the issue can be seen: hidden link homepage: Fusion Slider is loading infinite

I expected to see: The slider content

Instead, I got: The slider loading infinite

#592374

Hi,

The problem you mentioned above is abnormal, in case there are other compatibility problem in your website, please check these:
1) deactivate other plugins and switch to original Avada theme, and test again
2) Enable PHP debug mode, copy and paste the debug logs here
PHP Debugging
In case you think that Types or Views are doing something wrong (what we call a bug), you should enable PHP error logging. Again, edit your wp-config.php file and add the following:

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
This will produce a file called ‘error_log.txt’ in your WordPress root directory. Make sure that the web server can create and write this file. If it cannot, use an FTP program to create the file and make it writable to Apache (normally, user www-data).
https://toolset.com/documentation/user-guides/debugging-types-and-views/
3) If the problem still persists, please provide a database dump file (ZIP file) of your website in below private detail box, I need to test and debug it in my localhost, thanks

This ticket is now closed. If you're a Toolset client and need related help, please open a new support ticket.