Hi Leonardo,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

I tried to reproduce this with the Lite Version of the Element Pack , but can not replicate it.

I got the latest wpDataTables premium installed along with latest free Elementor and this latest free Element Pack Lite version, and I can still see my foreign key Relation options.

You can download my Video here.

1. Can you please send me the files from your Elementor and Element Pack Pro installations, so that I can install it here and we can try to reproduce it again?

You can upload the entire Plugin/Add-on Folder to weTransfer and just send me a download link.

2. If you can also confirm which version of wpDataTables are you using?

If it's premium, do you have the latest 6.2.1 wpDataTables installed?

3. And if you can also send us Administrator Access to your Website, so that we can try to isolate it directly on your Site, too.

Please provide me a temporary WP-admin (administrator) user for your website where this happens, 

as well as FTP credentials 

so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

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.

Hi Leonardo,

Thank you for sending us the Plugin's files of the Pro version.

Now with this Pro version I am able to reproduce this conflict on my Site.

I will just leave a short Video demonstration on this download link, to have it at hand.

We passed this to our developers. They will do their best to try and debug this conflict.

For now, you would have to keep the elementpack pro plugin disabled if you need our Foreign Key Relations to work until we try to debug it.

I will keep you posted on the progress.

Thank you for your patience.

Hi Leonardo,

We have the fix for this conflict.

Our developers will do their best to try to add this fix in one of our future updates, but I can't guarantee it, since there is a lot of testing to be done before it gets added.

-

In the meantime, we have a workaround fix with a small code edit of our Plugin.

Here are the steps, if you wish to try this yourself.

Use FTP or your Hosting File Manager, or the Plugin File Manager, and find this JS file in the following path :

..\wp-content\plugins\wpdatatables\assets\js\wpdatatables\admin\table-settings\main.js.

If you have our latest wpDataTables version 6.3.1 installed, this piece of code should be around line 823 :

$('div.wdt-foreign-key-block').show();

Or you can search for it via CTRL+F.

Add this under that line :

$('div.wdt-foreign-key-block').removeAttr('hidden');

So now it should look like :

Save the change, and one last step.

Please disable this option in your Main wpDataTables settings/Custom JS and CSS/Use minified wpDataTables Javascript.

Refresh your Table and now this conflict with the 'Element Pack Pro' should be fixed.

It works on our Websites, we can now see the Foreign Key Relations.

Let me know if that fixes the issue on your Site, it should.

Important to note :  For the time being, before our developers add a fix in the future, at each update, you would need to repeat that code edit of our JS file to work around the conflict.

 We don't have an ETA on when the fix will be available, but please keep a lookout on our wpDataTables changeLog.

It will be stated there during updates which bug fixes have been implemented at each update. If they create a fix in between updates, I will make sure to send it to you.

-

If you need us to edit this code for you, you can send me the URL of your Site, administrator user credentials and FTP Credentials.

Just make sure to send is as a PRIVATE reply for security reasons.

Thank you.