Hi,
thanks for your question, and sorry for the trouble.
I’m not exactly sure what your desired use case is here. Can you maybe give me an example?
Currently, the tables to indeed get an auto-incremented number as the table ID, except if they are imported from the full TablePress JSON format which can contain a pre-defined table ID that will then be used (unless it’s already taken).
Regards,
Tobias
We normally do an import of 100 tables and those 100 tables are used on multiple posts.
Sometimes, we even re-use the same tables for our newer posts.
Allowing us to custom create the table id would make everything more organized.
Example: table id=vanilla-cakes, table id=chocolate cakes.
In future when we got another post on vanilla cakes, we can easily link the table to the new post.
Right now, after our import we manually change each table id to something more recognizable instead of table id 2213, 1659, etc.
Hi,
I see what you mean. Unfortunately, I can’t think of a good way to set the table ID manually after a regular import (as the CSV format for example would not offer a way to store the ID).
Changing the ID manually is the only solution that I can think of here. Sorry 🙁
Regards,
Tobias
How about allowing us to call the table via the table name instead of table id?
Hi,
unfortunately, that won’t be possible 🙁 Not only is the table name not unique, it’s also stored in a different location of the database, so that it’s basically part of the table data and meta data. That can’t be queried without first knowing the ID though 🙁
Regards,
Tobias
