[Plugin: WP-Table Reloaded] Table edit screen crashes a Chrome tab and freezes Firefox

Hi,

thanks for your post.

Yes, such a table likely is too big.

There is no theoretical limit on the table size, but as you can calculate easily, your table needs over 28.000 textfields to hold the data. This simply is too much for the browser on an average computer.

For this table, you should definitely look into a custom solution, based on PHP and a mySQL database.

Best wishes,
Tobias

Hi Tobias, thank you for your nice plugin.

Effectively I’m using an Intel Core i7, 4GB Ram, that’s more than an average box so there should be something to be optimized, on the front end there’s a little lag/cpu peak on page loading but all that data is finally displayed and sort/filter functions are quite fast.

On the backend it behaves as said, probably because of additional controls and editing features engaged for each cell all the time.

I’ll try to import a smaller table to finally see what’s on the edit panel, maybe a paging feature is missing from it?

Otherwise if there’s something heavy on the JS side I could try to optimize it, I’m quite an ace with it.

Have a nice week end!
Alessandro

Hi Alessando,

yes, that is more than an average machine, but again, 28.000 text fields (with JavaScript applied to it) is also more than average ??

On the frontend, this is not an issue, because there are no text fields to be displayed.

Yes, a paging feature would be handy on the “Edit” screen as well, but unfortunately, I’m unsure how this could be implemented, due to the used internal data format. It is not really easy to only show and then save parts of a table with that, unfortunately.

The main JavaScript on the “Edit” screen is the autogrowing text fields. You can disable that on the “Plugin Options” screen, to see if that helps maybe. But again, long term, you should definitely look into a solution that is based directly on a database.

Regards,
Tobias

Hi Tobias,
Turning off cell autogrow and confirm on exit options didn’t solved the problem, so I’ve reduced the CSV file to see what’s the practical limit and found that Google Chrome crashes the tab at around 950 rows, while firefox freezes for many seconds but finally becomes available again with about 3000 rows.

There’s no problem for me, your cool application suits my needs in it’s current development status, as re-import function comes in handy to update data, thanks for sharing it!

For future architectures, yes, we all need to keep scalability in mind and notice that most of the best web applications are all about data chunking.

Best wishes,
Alessandro

Hi Alessandro,

thanks for testing nice, it is good to know those values!

I will see what I can change for better scalability in the future. For that, it likely won’t be enough to change the “Edit” screen, there will also be changes to the data format needed.

Best wishes,
Tobias

Hi Tobias,
If found out that if you make the data to show up in the backend (edit table view)in a simple table rather than massive number of texfields it doesnt crash the browser that easily. I tried to force the plugin to show the table in that manner but could not make it to output it in the site. Any simple fix for that?

All the best mate!

Hi,

no, sorry, I don’t really have a fix for this. If is of course possible to show a table without textfields on the “Edit” screen, but one would lose the actual edit functionality then, which does not exactly serve the point… ??

For large tables, it might be the best to edit them in Excel and then re-import the data from a CSV file.

Best wishes,
Tobias