Hi,
thanks for your post, and sorry for the trouble.
Both of these problems are most likely caused by both TablePress and the “Ultimate Tables” plugin being activated. They both use the same JavaScript library, but Ultimate Tables uses and old and outdated version. Due to that, these features can break.
Can you therefore please try again after deactivating Ultimate Tables?
Regards,
Tobias
Tobias,
Thanks so much for your response. It totally fixed my problem and I am not sure I would have found it without your help. The only reason I had Ultimate Tables activated is because I was trying to do something else that I thought I could not do with TablePress. I found that answer last week and so no longer need two table plugins.
That being said I have another question if you don’t mind. I am trying to decide the best option for me for my table data to work on a phone/tablet. I have tried several solutions and am trying to decide which one I like best. I have tried your responsive table plug in but I am not sure that is my preference.
I found a website that offers a mobile solution with some code. The code is:
‘@media screen and (max-width: 640px) {
table {
overflow-x: auto;
display: block;
}
}’
And, the website link is: http://exisweb.net/responsive-table-plugins-and-patterns
Is this something that would work in the table press plug in? I tried inserting the code in the Custom css section of table press and changed: table above to .tablepress but it didn’t seem to do anything.
Can you offer some insight? Thanks again for your help.
Tobias,
One more alternative…I also found this query/plug in for stacking my table when on a phone…can this be used with the TabelPress plug in and if so, how/where?
http://johnpolacek.github.io/stacktable.js/
Thanks again for the help.
Hi,
good to hear that deactivating the other plugin helped! 🙂
Using that stacktable.js script is not that easy, I’m afraid. You would basically have to load that JS file in your theme and add the initialization code as well.
For that other approach, for which you found that CSS code, I actually suggest a very similar thing (pretty much the same, just a slightly different implementation): https://ww.wp.xz.cn/support/topic/responsive-tables-scroll-only?replies=6#post-5511954
Regards,
Tobias
Tobias,
I clicked on the link but it takes me to your scroll wrapper. I have tried that and unless I am doing something wrong I did not think it was the same thing as the media screen option…here is what the table looks like when finished with the media screen:
http://exisweb.net/wp-content/uploads/2013/09/vert-table.jpg
Thanks…
Hi,
yes, my link would “only” add the scroll wrapper. The CSS code that you posted also does that, however (it should actually work as-is in the TablePress “Custom CSS”).
The solution from the image link in your last post would require other code, and from what I can see, it would also require special HTML markup, which is not yet possible with TablePress, unfortunately 🙁
Regards,
Tobias
Tobias,
I assume that means I would leave the code to read: table and not change it to .tablepress, right???
Hi,
you could actually do that. Changing it to .tablepress is probably safer, as the code would then only apply to TablePress tables and leave all others unchanged.
Regards,
Tobias
Tobias,
Sorry for the delay in getting back to you but I have been experimenting with a lot of options and also searching through your forum where you have answered other questions quite nicely. Anyway, I just wanted to let you know that all items seem to be working for now and I was able to use some ideas from your other responses that work very nicely for my tables. As it turns out, I don’t think I am going to need to use your extensions and am able to do what I need within the CSS pages by using some of the ideas in the other Q&A from your forum.
Thanks again for all the help and insight…it is much appreciated!
Hi,
that’s great news, thanks for the update!
Good to hear that my previous replies are helpful here! 🙂
Best wishes,
Tobias
P.S.: In case you haven’t, please rate TablePress here in the plugin directory. Thanks!