Hi Ken,
thanks for your feedback, it is much appreciated!
I’m sorry to hear that you feel that the plugin is useless as of now, but I feel that you are mixing things up here. The “Custom CSS”, and especially how it is being applied to a table, is not actually a feature or invention of TablePress. Instead, CSS is more like a general styling language that is used in the web to style web pages, by giving commands to the web browser on how to render or style various elements on the page. All WordPress themes use it, and that’s where one common problem lies: Some themes also contain CSS styling commands for tables, which then can interfere with the CSS of TablePress, or with the CSS that one enters into the “Custom CSS” textarea. Additionally, styling tables (and especially the aspects of widths in tables) is one of the more complicated tasks. The reason is that tables, to some degree, respond differently to the commands. This can usually be seen in exactly the example code that you are using to make columns smaller. A table will never allow columns to be smaller than what their content demands, and thus it appears that your CSS code does not have an effect. In most cases, it is then possible to reduce the width by making inner margins and paddings smaller.
The issue about the table head row is likely a case where the theme CSS interferes with the styling, which is why you get that result.
To find out exact reasons and hopefully find code that is working, I’d really need to see the table. As you can’t publish a link here for privacy reasons, I’ll therefore contact you by email.
Regards,
Tobias
Hi,
just for everybody reading this:
After working with Ken directly, we found that his current theme contains a lot of CSS code that influences tables, and interferes with the “Horizontal scrolling” function that he needs for his table.
As there were other technical issues with fixing this directly, Ken will now look for another theme, that does not cause this trouble.
Best wishes,
Tobias
@kencooperjr:
In fairness and in the interests of launching future support topics, try simply describing your problem before making overly-dramatic, undue, inaccurate, and misleading judgements (e.g. “useless product”).
I understand that hours of debugging can be beyond frustrating but you’ll catch more flies with honey than vinegar when it comes to seeking support in general.
As a rule of thumb and as practiced by TobiasBg, whenever you experience an issue with a plugin, it’s a good idea to switch to WordPress’s default theme e.g. TwentyTen, TwentyEleven, TwentyTwelve etc.
Secondly, don’t publish your email address in support forums. Spammers will collect and archive your address and flood you with spam mail. Either bookmark the page or check the “Notify me of follow-up posts via email” checkbox whenever you post a topic or reply. ww.wp.xz.cn already has your email address. You don’t need to print it for developers or other users to email you.
Hi,
thanks for these words. They are very true. The advice about switching themes is very good, I’ve added it to the forums sticky post 🙂
Best wishes,
Tobias
