Child theme should be able to seed parent theme blueprint

Need Help
#1

Hello,

I’m working on a project that use parent / child theme.

The parent theme have some blueprint associated with it under seeds/blueprint folder inside the parent theme.

When I add a new child theme with the parent theme above, the logic would be to also inherit blueprint and being able to seed child theme with parent theme blueprint.

Instead of that, in my backend, when I click in “manage” button of my child theme, I don’t have the “seed content” option.

To get it (and so, to be able to seed my theme), I have to copy the seed folder of my parent theme to the child theme, and so, I loose the interest of parent / child theme inheritance.

Is it by design, if yes, why ? or is it a bug ?

Thank you

#2

Hey @Zmove

It is an oversight, for sure. I have made a note of this in our internal tracker.

Thanks!

#3

@daftspunk Thank you very much

#4

I’m also having this issue. Any news on when a fix might happen?
Thanks.

#5

Since this is affecting multiple users, I recommend contacting the helpdesk about it: Contact Us - October CMS

The themes now can use blueprints natively, so you don’t need to seed them. Technically this should be checked for child theme support also.

#6

Hi all,

Following up on this one: child theme support for blueprints has been fixed and will be included in the v4.4 release.

What’s changing:

  • Theme blueprints are now inherited. Blueprints in a parent theme’s blueprints/ directory are picked up automatically when a child theme is active. They resolve by handle, show up in the backend navigation and work with the page finder. If the child theme defines a blueprint with the same UUID, the child version wins.

  • Seed content is inherited too. The “Seed Content” option now appears for a child theme when the parent has a seeds/ directory, and seeding imports the parent’s blueprints, data and translations. A child theme with its own seeds/ directory uses that instead.

For new projects we recommend placing blueprints in the theme’s blueprints/ directory rather than seeding, since these are used directly without an import step.

Thanks @Zmove for the original report and everyone for the patience here.

1 Like