Hey everyone!
With the holiday season upon us, we want to share our upcoming working hours:
- New Year: Our team will be off on January 1st and 2nd. We’ll be back on Friday, January 3rd, to respond to any messages received during this time.
- Weekend: As usual, we don’t work on weekends, so January 4th and 5th will also be non-working days.
- Orthodox Christmas: Our office will be closed on Monday and Tuesday, January 6th and 7th for the holiday.
After that, we’ll return to our regular schedule and assist you as quickly as possible.
In the meantime, you can explore our documentation for Amelia and wpDataTables. You'll find tons of helpful resources, including articles and handy video tutorials on YouTube (Amelia's YouTube Channel and wpDataTables' YouTube Channel), which might just have the answers you need while we’re away.
Thanks a bunch for your understanding and support!
Warm regards and happy holidays!
TMS
The search functionality of wpDataTables on the backend presumably uses some sort of AJAX function - when you have typed something, the results of that search query are automatically displayed.
Annoyingly, this means that you can only view the first page of results for that search query. When you go to the next page, the search parameter is empty and results are no longer filtered.
Is there any way around this, or is there any feature update to resolve this?
On the fly results from search is a good idea but functionality is sacrificed as a result.
Hello Mike
Ajax is used for manual and large MySQL query-based tables. Since large tables (over 2.000 rows) with server-side processing turned can't be properly used, this is mandatory for all tables above 2.000 rows. If you create a table linked to an existing data source (Excel, CSV, Google Spreadsheet, XML, PHP, and JSON), you would not be using Ajax for filtering, sorting, search, and pagination, but instead all data would be loaded at once, and split into pages within a table using JavaScript.
Manual tables don't have an option to turn off Server-side processing, but MySQL query-based tables do (if the table has less than 2.000 rows). If the table has more than 2.000 rows, the Server-side option will be turned on automatically, to prevent page crashes.
Either way, I can't replicate the issue you're describing. Please check out our documentation for the large MySQL query-based table, that consists of around 2.5M rows. When I enter a term in the search field and switch between pages, the search term is saved. Also, when I use filtering and switch between pages, the search term is also saved. Please check out the attached video, to see how it behaves on our documentation.
wpDataTables is a WYSIWYG (What You See Is What You Get) concept-based plugin. This means that the table should look the same both in the back-end and in the front-end. So, the behavior of our table on the front-end and in the back-end should be the same.
Can you please record your screen, and show us what you mean?
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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 Aleksandar,
Thanks for the input - i think i might have provided an overly complex explanation.
When you have more than 10 tables in wpDataTablets the list of tables is paginated.
You can do a search using the search box - Search for items... - however this generates results for the search term once you stop typing (which is a little annoying).
If the results returned total more than 10 tables/rows you cannot see the results beyond the first page of results.
E.g. if your search returns 20 results, you can only see the first 10 results as when you use the pagination to go to the second page of results the search query is not carried across
Hopefully that makes a little more sense.
Oh, I understand Mike, thanks for clearing that up.
I forwarded the ticket to one of our developers, so he can take a look.
I hope he'll be able to find a way and resolve this, either by moving the search value into the 2nd page, or by changing the behavior of the function, so it's not a live/dynamic search.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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
Awesome, thanks very much - its actually quite frustrating that if you don't type fast enough the search commences, so simply removing the auto search would likely be best, then I can type in the full text i need to search for, before then physically pressing the "search" button.
Hello again Mike.
We got a hotfix, but it needs to be tested before it's included in the update of the plugin. Please download the attached file, and replace files on these locations:
wp-content/plugins/wpdatatables/source/class.wdtbrowsechartstable.php
wp-content/plugins/wpdatatables/templates/admin/browse/pagination.inc.php
wp-content/plugins/wpdatatables/source/class.wdtbrowsetable.php
wp-content/plugins/wpdatatables/templates/admin/browse/table_list.inc.php
wp-content/plugins/wpdatatables/assets/js/wpdatatables/admin/browse/wdt.browse.js
Replace the files with the ones attached to my response, and let me know how it works.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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
Thanks for this, Mike, I shared it with our developers.
If there's anything else we can do for you, please let me know.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
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
Having a separate backend identifying table name would be beneficial.
For example I want the table name to appear on the front end, but I also want another table identifying name not to appear on the front end.
This is because I have a lot of translated tables in non-English languages but, if I translate the table name (which appears on the front end) its a lot harder to distinguish what the table name is.
Hi MIke
If I understand correctly you would simply like to hide the table name on the front-end for individual tables? We have that feature available for all table types, simple tables included, and it's located under the Display tab
You can add a text block on the page where you placed the table and name it whatever you like and still have the wpDT table name say something different without displaying it to the public.
If I misunderstood can you please give us some details on what you would like to achieve so we can try and find you the best solution or you can add it as a feature suggestion on this page.
Features are pushed up on our "to-do" list when there are a lot of customers requesting those features, so having your vote as a customer can be beneficial to this feature being developed sooner.