martincomputerguy

ashish020786: While I appreciate your posting your solution on YouTube, your video just shows you selecting successive pieces of text, and it is so small I cannot read what you are doing.

Would you PLEASE simply post your solution as simple text HERE in this forum and EXPLAIN what steps you are performing?

@flizzywp Could you tell us which link-checker plugin you recommend? I’m a bit lost among the choices.

If you’re not permitted to do that here, feel free to take a look at my profile and contact me via my website listed there.

Thanks!

Martin

Ah ha! I figured out the problem.

I was actually using: <td>{Fieldname}</td>
when I should have used: <td>{fieldname}</td>
because your plugin makes all field names LOWERCASE! That initial capital letter was causing the problem.

Your Demo DB is misleading because its fieldnames do have initial capital letters.

Here’s another undocumented tip: When importing a CSV file, the line endings need to be CRLF (Windows) not CR only (Macintosh).

Typo: I meant to write: “<td>{field}</td>” specifiers

Martin

I’m wondering the same thing.

Hello? <knock-knock>

Anybody home?

Please also note: My CSV files use regular (straight) double-quotes (ASCII 34 decimal/22 hex), whereas this www.ads-software.com support page has changed them all to curly (typesetter) double-quotes (ASCII 8220 decimal/201C hex & ASCII 8221 decimal/201D hex).

I appreciate your opinion, but I disagree. Do you never switch your phone or tablet from portrait to landscape? Never widen your computer’s browser window, or click the Maximize button?

Isn’t mobile responsiveness supposed to provide responsiveness?

How would I contact that library’s developers?

Ok, then is it reasonable to contact that library’s developers to ask about fixing this?

Hi Tobias–

Thank you so much for your fast response. Your support is amazing!

Two things:

1. As you suggested, I removed that parameter, which changed my shortcode from:

[table id=21 column_widths=”15%|15%|10%|10%|50%” responsive=”collapse” /]

to:

[table id=21 responsive=”collapse” /]

but (apart from the columns having relative widths that I don’t like as much as my “15%|15%|10%|10%|50%” proportions) the problem is unchanged: The table does not “recover” properly after “squeezing” then “expanding” the window width.

Have you seen this problem before?

Could it be caused by some kind of round-off error in the column width calculations?

What else can I try? Is there something about my table data that could be causing this? It’s just text.

2. Looking at your https://tablepress.org/faq/column-widths page, I’m a little confused. Wouldn’t options like “width: 100px” make my columns have fixed widths, which would defeat mobile responsiveness? Can I use options like “width: 15%” instead?

Update: I just tried this with “15%” etc., but the problem is unchanged.

Thanks!

Martin