Hi,
thanks for your post, and sorry for the trouble.
I understand what you mean with that Trash feature, which would indeed be a nice thing to protect against accidental deletion of tables.
However, I don’t understand the reason/problem about the IDs incrementing.
TablePress treats table IDs as unique, in the sense that a table ID that was used already will not be given to a newly added or imported table.
So, for example, if you create tables 1, 2, and 3, and then delete table, the next table will still get ID 4. That way, we can prevent that the data in that table shows up in posts/pages that (by accident) still have the Shortcode for table 2.
Can you please explain where exactly that is causing problems? Also, deleting a table in TablePress will remove it from the DB permanently, without entering the DB manually.
Regards,
Tobias
When I move from local which is a DEV to LIVE in order to make sure that all my changes are made I delete all pages, posts, forms, and tables and re-import.
Everything works fine, except when importing tables. It creates a new unique ID and with that ID it creates a short code with that ID. It does not keep the short code. So it will break the tables on the pages the short codes are on.
https://stage.ucomm.wsu.edu/list-of-administrators/
Hi,
how exactly are you importing the tables? If you choose the “JSON” format, the tables will be exported and imported with their existing IDs, so that those won’t change, i.e. your Shortcodes won’t break.
Regards,
Tobias
Yes, I am using JSON because the other formats did not seem to import, missing headers server 500 error. JSON is the only import that would work.
Hi,
ok, that sounds really strange, and I have never heard of such an issue before. I have no clue how the different file formats can cause HTTP server errors like that…
So, even with the JSON import, your table ID’s are not matching?
Regards,
Tobias
