-
Notifications
You must be signed in to change notification settings - Fork 21
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
production category IDs don't match local env #85
Comments
What do you think of the idea of creating a custom It could essentially just do a slug -> id lookup and then wrap the core block. Though I'm not sure how easy that is, given that it's a JS block not dynamic. |
🤔 , I think that'd work, and it sounds like a good solution. Definitely worth exploring 👍🏻 |
I'm going to close this because the |
currently you have to manually update
term_id
in your localwp_terms
andwp_term_taxonomy
for the front page templates to work, b/c the have the production IDs hardcodedthe WRX from #10 doesn't have include category IDs because we exported specific post types rather than "all content"
we could update our export/import process to use "all content", but remove stuff we don't want later on. we'd probably have to hack together something that applies
can_export => false
to all the post types we don't want, though.publish
post statusAlternatively, we could query by category slug if WordPress/gutenberg#36785 if resolved
The text was updated successfully, but these errors were encountered: