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!
I've added a simple SQL-driven table to a page, but the search mechanism does not seem to work.
https://blog.proracquetballstats.com/index.php/pb-rankings-from-db-womens-pro-combined/
This is a simple example. However anything I type into the search bar returns no rows.
How does this search work and what is it searching for by default? is this a database-driven search or is it searching the table after it has been retrieved and displayed on the wordpress page?
Any help is appreciated.
Hi Todd
Thank you for reaching out to us.
If your MySQL-query based wpDataTable doesn’t work correctly with server-side processing, probably this is happening because wpDataTables server has problems with parsing of the query and building new queries dynamically (rarely happens, but does sometimes). To avoid this please prepare a MySQL view (a stored query), which will return the data that you need, call it e.g. “view1” and then build a wpDataTabled based on a simple query like “SELECT * FROM view1″.
Please note some this when working with the server-side processing feature:
Hi all; i have discovered the root cause here; it is the presence of a databasename.tablename in my from clause. By eliminating that in my queries, i'm able to get searching done.
Thanks Blazenka for pointing me in the right direction.
You are most welcome, I am glad to hear you were able to resolve the issue
If there is anything else we can assist you with please don't hesitate to open a new ticket.
Have a wonderful day!