Hello Moskms.

Sorry for the inconvenience.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, along with FTP credentials, so we can debug the plugin and see what's going on  

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Thank you for your input, Wilhelm, but this is not related to Elementor Pro. We all have it, and the latest version of wpDataTables has been tested in the latest version of Elementor and Elementor Pro and the majority of popular page builders.

The issue is coming from elsewhere. Try purging cache on your site, or if you're still having an issue, open your own private ticket where you can share the credentials I requested from Moskms, and we'll gladly check it out.

Hello again Moskms

Can you please go to ..wp-content/plugins/wpdatatables/integrations/page_builders/avada/class.wdtavadaelements.php and on the bottom of that file, on line 180, change this code:

function is_fusion_builder_active()
{
    if (is_plugin_active('fusion-builder/fusion-builder.php') &&
        function_exists('fusion_is_element_enabled') &&
        class_exists('Fusion_Element'))
    {
        new WPDataTables_Fusion_Elements;
    }
}
add_action('init', 'is_fusion_builder_active');

To this:

function is_fusion_builder_active()
{
    if (!function_exists('is_plugin_active')) {
        include_once(ABSPATH . 'wp-admin/includes/plugin.php');
    }    
    if (is_plugin_active('fusion-builder/fusion-builder.php') &&
        function_exists('fusion_is_element_enabled') &&
        class_exists('Fusion_Element'))
    {
        new WPDataTables_Fusion_Elements;
    }
}
add_action('init', 'is_fusion_builder_active');

If that doesn't help, please provide us with a temporary wp-admin (Administrator) user, and FTP access credentials, so we can debug the plugin, and see what's going on.

Just remember to enable the PRIVATE response.

You're welcome, Morten

I'm glad to have been of service.

We've released v4.0.1 in the meantime, which resolves this issue without the need for custom coding - if anyone runs into a similar issue with v4.0.