-
Notifications
You must be signed in to change notification settings - Fork 106
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
Learn WordPress Content Error Report - Ticket #1113
Comments
I think a good way forward here is to create additional separate content about block theme capabilities in a child theme
|
Update, per WordPress/gutenberg#46554, child themes now inherit their parent theme's style variations. We might close this issue (and potentially file a new one for the items @jonathanbossenger mentioned in #1113 (comment)). |
Error ValidatedError was discussed by @ockham and @jonathanbossenger . Block child themes now inherit parent theme's style variations. Proposed FixClose issue and follow up with @jonathanbossenger recommendations as proposed by @ockham |
Thank you for the feedback. I'm closing this issue now and will follow up with Jonathan about opening a new issue for his other suggestions. |
I've submitted the content ideas above here: #1556 |
Error Description
There's currently no mention of Style Variations: A block theme's child theme will currently not automatically include the parent's Style Variations. To have them included, the child theme's author will have to copy the parent theme's
styles/
directory.Originally reported in WP.org support forums here. I've filed a Gutenberg issue to change that behavior (i.e. to auto-include the parent's style variations), but for the time being, it'd be good to explain how to include them manually.
Per discussion with @jonathanbossenger, we might want to review the behavior of child themes for other block theme capabilities (e.g. template parts of block patterns) and add instructions (rather than focusing on style variations only).
Error Report Checklist:
The text was updated successfully, but these errors were encountered: