Indeed, this is a new error and it's breaking aspects of my site.
Visit https://podcastindustryinsights.com/ and you'll see the number of podcasts is not animating. That's because of WPDT. If I disable WPDT, the JS error goes away and this number properly animates.
One of the engineers responded privately saying that they've isolated the issue and will add it to their queue for fixing. We can watch https://wpdatatables.com/help/whats-new-changelog/ for when it's fixed in an update. I'm hopeful it will be in the next patch, which would be 7.0.2. But we'll see.
We have the first version of the fix for the Elementor bug. I am attaching the fix here, and we will write all the details with the instructions how you can apply it.
Our developers isolated the issue, and they'll add it to their queue for fixing.
We don't have an ETA on when the fix will be officially added to an update, 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.
We do have the first version of the fix now, our developers made it work on multiple Test websites, and a couple of users report it works for them - so it should work for you - but this is still being tested by our QA Team until official release as a new update.
If you wish to try this fix right now, here are the instructions.
Please find this JS file via FTP on your Hosting WordPress folder, the path is :
Upload this edited JS file we attached to the ticket, and overwrite the old JS file.
Clear the cache of your Site, refresh the page(s) where the issue was and check, it should be fixed.
Let me know how it goes.
If you need us to apply this JS fix for you - Please open a new private ticket from your Ticksy account, and send us the URL to your Site, along with an Administrator user credentials and FTP credentials; So that we can remote in and fix it for you. Just make sure it is either a PRIVATE ticket or in a private message, for security reasons.
Yes, this did fix the issue, but man was it frustrating to clear the cache because the version number in the URL params was making it difficult. I eventually found and edited WDT_CURRENT_VERSION (to "7.0.1b") in config/config.inc.php and that helped my cache finally clear.
I am sorry, but this subject of that specific way of clearing the cache goes above my level of knowledge.
This could be very helpful for our other users - in case if they encounter the same issue, so could you elaborate in more details/steps, what kind of cache issue happened on your Site, and how you edited the WDT_CURRENT_VERSION (to "7.0.1b") in config/config.inc.php in order to finalize that cache purge in the end?
Of course, you don't have to go into all these detailed steps, but it could help other users, if there is any guide online, etc, to start them in the right direction/ to be aware of, if they encounter the same cache issue, etc.
Sure thing. Web apps will often add version numbers when they load assets, like JavaScript, CSS, and images. This bug in WPDT is in the Elementor JavaScript file, for which you provided a fixed version. Replacing that file on my server with the patched one would still not load the new version because either my browser or some caching on my site kept seeing the old version in the URL, like "file.js?v=7.0.1," so it would not load the new version. By editing config/config.inc.php in WPDT, I could change the line that defined WDT_CURRENT_VERSION to "7.0.1b" instead of "7.0.1," and that change the linking to "file.js?v=7.0.1b."
But this will all be a moot point when this fix is included in a released update.
I don't know when this started—maybe with 7.0/7.0.1—but I'm now getting this console error on my site:
Uncaught ReferenceError: elementor is not defined
at wdt-custom-elementor-js.js?ver=7.0.1:3:9
Indeed, this is a new error and it's breaking aspects of my site.
Visit https://podcastindustryinsights.com/ and you'll see the number of podcasts is not animating. That's because of WPDT. If I disable WPDT, the JS error goes away and this number properly animates.
Was this ever resolved? We're running into the same issue on our end on multiple websites.
Hi, Megan.
One of the engineers responded privately saying that they've isolated the issue and will add it to their queue for fixing. We can watch https://wpdatatables.com/help/whats-new-changelog/ for when it's fixed in an update. I'm hopeful it will be in the next patch, which would be 7.0.2. But we'll see.
Hi guys,
We have the first version of the fix for the Elementor bug. I am attaching the fix here, and we will write all the details with the instructions how you can apply it.
Our developers isolated the issue, and they'll add it to their queue for fixing.
We don't have an ETA on when the fix will be officially added to an update, 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.
We do have the first version of the fix now, our developers made it work on multiple Test websites, and a couple of users report it works for them - so it should work for you - but this is still being tested by our QA Team until official release as a new update.
If you wish to try this fix right now, here are the instructions.
Please find this JS file via FTP on your Hosting WordPress folder, the path is :
..wp-content/plugins/wpdatatables/integrations/starter/page-builders/elementor/js/wdt-custom-elementor-js.js
Upload this edited JS file we attached to the ticket, and overwrite the old JS file.
Clear the cache of your Site, refresh the page(s) where the issue was and check, it should be fixed.
Let me know how it goes.
If you need us to apply this JS fix for you - Please open a new private ticket from your Ticksy account, and send us the URL to your Site, along with an Administrator user credentials and FTP credentials;
So that we can remote in and fix it for you.
Just make sure it is either a PRIVATE ticket or in a private message, for security reasons.
Attached files: 7.0.1 wdt-custom-elementor-js.zip
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Yes, this did fix the issue, but man was it frustrating to clear the cache because the version number in the URL params was making it difficult. I eventually found and edited WDT_CURRENT_VERSION (to "7.0.1b") in config/config.inc.php and that helped my cache finally clear.
Hi Daniel,
I am sorry, but this subject of that specific way of clearing the cache goes above my level of knowledge.
This could be very helpful for our other users - in case if they encounter the same issue, so could you elaborate in more details/steps, what kind of cache issue happened on your Site, and how you edited the WDT_CURRENT_VERSION (to "7.0.1b") in config/config.inc.php in order to finalize that cache purge in the end?
Of course, you don't have to go into all these detailed steps, but it could help other users, if there is any guide online, etc, to start them in the right direction/ to be aware of, if they encounter the same cache issue, etc.
Thank you for letting us know, in either case.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Sure thing. Web apps will often add version numbers when they load assets, like JavaScript, CSS, and images. This bug in WPDT is in the Elementor JavaScript file, for which you provided a fixed version. Replacing that file on my server with the patched one would still not load the new version because either my browser or some caching on my site kept seeing the old version in the URL, like "file.js?v=7.0.1," so it would not load the new version. By editing config/config.inc.php in WPDT, I could change the line that defined WDT_CURRENT_VERSION to "7.0.1b" instead of "7.0.1," and that change the linking to "file.js?v=7.0.1b."
But this will all be a moot point when this fix is included in a released update.