New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WordPress Importer Support #17
Comments
Hi @jeremyfelt! Thanks for opening this ticket as a reminder! I haven't put that much thought and time into WordPress Importer support yet, given that TablePress has its own export/import system as a workaround here (mentioned in the link that you posted). I'm however very open to adding such support! Using |
BTW, you might be interested in this TablePress Extension, which adds a "Debug" tab to TablePress, that shows some more internal information, and allows for easy editing of the |
During export, add the table IDs for the exported `tablepress_table` posts into a pseudo post meta field. During import, use those table IDs to restore the mapping from table ID to post ID in the `tablepress_tables` WP Option. See #17.
Hi @jeremyfelt! |
No way! That is fantastic! I was just showing this repo to our open lab this morning and I had forgotten about the issue. Thanks @TobiasBg! |
No problem, @jeremyfelt :-) And thanks for spreading the word about the plugin! |
Hi @TobiasBg!
I'm running into this issue with TablePress and have been poking around to see if there's a good approach to regenerating the table ID associations.
The table data is inserted fine in posts and postmeta during import. Because of the missing
tablepress_tables
option, it does not show in the standard TablePress display. It does show if I go directly toedit.php?post_type=tablepress_table
.I could see hooking on
wp_import_insert_post
to regenerate the data. I could also see having a "regenerate" or "flush" option that triggers and entire rewrite oftablepress_tables
. This could be useful in a case where that option is accidentally deleted for some reason as well.Before I dig further—is this something that you could see supporting in the future? And have you given any thought to approach if so?
Thanks!
The text was updated successfully, but these errors were encountered: