Handling of non-numeric table IDs

  • Resolved actronab

    (@actronab)


    3 years, 2 months ago

    Hello,

    I created two tables and used non-numeric IDs for more semantic markup.

    E.g. I named the tables “adults” and “children”. I am not sure, if I’m supposed to do that, but I did not encounter any problems yet. Is it okay to use text as ID?

    However, the interface seems to be optimized for numeric IDs. The ID column in the view that lists all existing tables is very narrow, for example (at least on my small screen). Furthermore, when I view the table preview, the shortcode in the introduction is cut off:

    Um die Tabelle in eine Seite, einen Beitrag oder ein Text-Widget einzufügen, kopiere den Shortcode [table id=adult und füge ihn im Texteditor ein.

    It should be [table id=adults /], not [table id=adult. This could cause problems, if users rely on the text. Not a big deal for me, but maybe you could improve handling of non-numeric IDs by giving the IDs a little more space.

    Kind regards,
    Bernd

Viewing 1 replies (of 1 total)
  • Plugin Author TobiasBg

    (@tobiasbg)

    3 years, 2 months ago

    Hi,

    thanks for your post, and sorry for the trouble.

    Yes, it’s perfectly fine to use text strings as table IDs! Indeed, I often recommend it for better organization and management of tables!

    The issues with the interface are not directly related to the text strings, but to the length of the IDs. Essentially, this is the result of how TablePress needs to override some of the WordPress default CSS (in the list of tables), and how text fields calculate their lengths (it’s not really possible to have the text field adjust to the size of its content).

    Regards,
    Tobias

Viewing 1 replies (of 1 total)
  • The topic ‘Handling of non-numeric table IDs’ is closed to new replies.