Hi Corey,
Sorry for trouble,
Issues like this usually occur when there is a conflict either with the theme currently active on your website, or another plugin you have installed.
First if you can access settings of plugin in admin menu, you can try to turn off options “Include full bootstrap back-end” in Main settings of plugin and check is it working.
If that not help, can you please change the theme and see if the issue is resolved? If not, then please deactivate all other plugins except for our plugin, refresh the page where the issue is, and see if it is resolved (it should be). If it is, then start activating other plugins one by one, and after each activation refresh the page to see if the issue reoccurred. Once it does reoccur, you will have found the plugin causing the issue.
Unfortunately the issues like conflicts with third party plugins or themes are always possible due to the nature of WP.
Best regards.
@wpdatatables It is still happening on multiple sites with default Twenty twenty-one theme and no plugins active.
Hi Corey,
Unfortunately we can not tell more without further investigation on your website.
This is a public forum, so it is not recommended sharing credentials here.
Please go to our support system on this link and open Private Pre-purchase ticket where you will provide us temporary wp-admin 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 a third party.
I found the issue. We are using Composer (via wpackagist) to install the plugin. The problem is that WordPress plugin repository and wpackagist both see version 2.013 as the latest version instead of 2.1.5.
As you’ll see here: https://plugins.trac.ww.wp.xz.cn/browser/wpdatatables/tags and here: https://wpackagist.org/search?q=wpdatatables&type=plugin&search=
I’m not sure what can be done, perhaps removing the 2.013 tag as it appears to be a typo anyways.
Thank you.
Hi Corey,
I am glad that you find what cause the issue. Yes that was a mistaken update version in the past, and we will remove it from the repository in the next update.
Thank you for reporting this.
Thank you