Unfortunately there is nothing we can do about the spinner thing with the plugin's builtin features but maybe you can do something to increase the loading speed of the table.
How you create the table can have much to do with the loading speed. For example Excel files generally work slower than CSV-files, or even Google Spreadsheets; this format will work only up to a certain limit (no exact limit, but 3000-5000 cells is a good example).
When your data set is larger than a couple of thousand rows, it can’t effectively be loaded in the page. It first reads the data from the source, and then prints out the complete table data on your page; so, as the row count grows, it makes both the page generation time on server side and the page load and initialization time on client side, slower and slower. If your host has a certain memory or timeout limit defined for PHP scripts, it can ‘break’ the page, because the script would try to allocate more memory than it’s allowed.
So if your table is large, it is much better to port it to a different format, or – even better – to MySQL table (you can use “Create a table by importing data from data source” to import your Excel file to MySQL).
If you can provide us a link to the front end where you placed your table so we can have a closer look at the spinner behavior?
Hi, when a search is being performed, the circle spinner icon thing,
1) is in the middle of the results page
2) if multiple records are already being displayed, you can't SEE the spinner?
what can be done to improve the UX for when searching or results are loading?
thanks
Hi Larry
Thank you for reaching out to us.
Unfortunately there is nothing we can do about the spinner thing with the plugin's builtin features but maybe you can do something to increase the loading speed of the table.
How you create the table can have much to do with the loading speed. For example Excel files generally work slower than CSV-files, or even Google Spreadsheets; this format will work only up to a certain limit (no exact limit, but 3000-5000 cells is a good example).
When your data set is larger than a couple of thousand rows, it can’t effectively be loaded in the page. It first reads the data from the source, and then prints out the complete table data on your page; so, as the row count grows, it makes both the page generation time on server side and the page load and initialization time on client side, slower and slower. If your host has a certain memory or timeout limit defined for PHP scripts, it can ‘break’ the page, because the script would try to allocate more memory than it’s allowed.
So if your table is large, it is much better to port it to a different format, or – even better – to MySQL table (you can use “Create a table by importing data from data source” to import your Excel file to MySQL).
If you can provide us a link to the front end where you placed your table so we can have a closer look at the spinner behavior?