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!
Hi, I am sorry to bother again, this is not a pre-purchase questions but rather finding bugs in the plugin to make the plugin better.
[In wpdatatables 2.0.2]
So basically when you are trying to use foreign key but the column name in foreign table is not one word , for example, like 'contact name' stuff like that, then the foreign key inserting is going to fail. The workaround without changing the title of the foreign column name to single word is to make the change as below in this file:
/assets/js/wpdatatables/admin/table-settings/table_config_object.js
at line 635, change the display_header to orig_header, then the sql command will not fail.
You are welcome and where's my cookie? :)
Hi Issacchua,
Thank you for reporting this.
We spotted this bug already and we are working on a fix. Your proposition is good one and we will definitely consider implementing it when we checked all aspects.