We're Moving to a New Support Platform – Starting June 1st!
We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.
You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.
While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.
We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.
Thanks for your continued support and trust – we’re excited to bring you an even better support experience!
When inserting multiple parameters in a JSON URL and separating them with the ampersand (&) symbol, the & symbol is being replaced with "amp;" and any parameters beyond "amp;" are ignored.
As a temporary workaround, I edited the URL directly in the content field inside the wpdatatables database table and replaced the "amp;" instances with just an ampersand symbol.
I believe this is a bug.
Hi, Chris
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.
-
Thank you for reporting this, we will check with our QA Team if they can reproduce this issue on our Test sites,
in order to confirm if this behaviour is a bug, and to see what should be the default behaviour.
-
I will let you know if we need any additional detail from your end.
Just to check, do you have the latest plugin version 5.3 ? Thank you
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
Hi, Chris
Our developers have already implemented a fix for this behaviour - they just confirmed that for us.
Can you please check, if you don't have the latest version 5.3 , can you please update your plugin?
Updating the plugin to the latest version
And make sure to purge cache on site.
If you still have the issue with the latest version, then most probably the WP user that you are logged in as while editing/making the table does not have the 'unfiltered_html' capability enabled/allowed.
If that's the case, you can double-check if that user has this capability "enabled/allowed" and it should work with version 5.3 ?
Thank you
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
Hi Milos,
Awesome, this resolved the problem and I can confirm that updating to version 5.3 fixed this issue. I appreciate the quick work from you and the dev team to patch.
I did not have to make any changes to the unfiltered_html capability - simply updating to 5.3 resolved it.
Much appreciated.
Chris