Hi Neil,
thanks for your post, and sorry for the trouble.
Yes, unfortunately, something like this can happen with big tables, due to the large number of table input fields on the page. These will cause some browsers to slow down, as they have trouble managing that large number of fields.
So, yes, having fewer fields on the “Edit” screen will help tremendously. If your table has hidden columns that will never be necessary, it is better to delete them, to reduce the number of fields.
Also, could you please try this again in a different browser? I recommend Google Chrome here, as that has a very efficient internal engine for this.
Regards,
Tobias
Hi Tobias
Ok … thank you. I will delete a table and recreate with fewer columns to see what the result is. As for Chrome … this is the browser I was trying it on!
Regards
Neil
Hi Neil,
yes, that will be the best way to proceed then. Also, make sure that Chrome has as much memory available as possible, i.e. try to close other browser tabs and other programs that are running.
If that does not help, there’s maybe another work around: Instead of editing the tables in TablePress, you could edit them in e.g. Excel and then re-import them into TablePress after making changes, choosing to replace the existing version of the table.
To make this better in the future, I currently working on reducing the number of input fields by re-modeling the “Edit” screen. I hope to have that available in an upcoming version.
Regards,
Tobias
Hi Tobias
Ah … we are getting there. It is still quite slow but it does eventually get there … patience is required.
Please view the following link as this is the one I have changed so far …
http://www.peakandfellwalking.co.uk/peaks/peaks-by-category/birketts/
Two points from the changes I have made …
1) The table is now not responsive (it was before) as the columns extend beyond the edges of the webpage.
2) The new search boxes at the bottom of the table are not in the same colour scheme as the rest of the table and the boxes are blank rather than showing the name of the column.
Kind Regards
Neil
Hi Tobias
The above mainly relates to the support question “Search A Column Not The Whole Table”
Regards
Neil
Hi Neil,
good to hear that you can edit tables at least a little bit better now.
For the second part, that’s for the problem in http://ww.wp.xz.cn/support/topic/search-a-column-not-the-whole-table , correct?
This is related to the styling of the new search fields. By default, they have fixed width and the footer uses the default styling of the table. To change that, please add this to the “Custom CSS”:
.tablepress tfoot th {
background-color: #383838;
padding: 3px;
}
.tablepress tfoot th input {
width: 100%;
}
To give them the column names, just repeat the respective column name in each column’s footer cell (my previous post about adding an empty new last row was slightly incorrect here).
Regards,
Tobias
Hi Tobias
The styling of the search boxes is now fixed … thank you.
The responsive issue has now gone away. All I did was get rid of underscores (which came across from the csv file) in the name titles!
Regards
Neil
Hi Neil,
very nice! That’s great to hear 🙂
Yes, those underscores prevent the browser from doing word-wrapping, which could then lead to this wrong behavior.
Best wishes,
Tobias
I ran into the slow/unresponsive issue as well – on Chrome. In Internet Explorer it’s working fine. Just an FYI, not sure why that would be.
Hi,
yeah, the latest IE has gotten better with this in the last months. So, people who are affected by this should definitely test on different (up-to-date) browsers.
Regards,
Tobias
Hi Tobias
Just to confirm IE is lots faster. Thank you poeghostal.
Regards
Neil
Hi Neil,
thanks for that. Looks like I’ll have to check out other browsers more often 🙂
Best wishes,
Tobias
