Postponed
Project:
Drupal core
Version:
main
Component:
Olivero theme
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Mar 2023 at 00:00 UTC
Updated:
19 Aug 2026 at 09:29 UTC
Jump to comment: Most recent
Comments
Comment #3
mstrelan commentedSome observations.
The first issue I ran in to was this error:
Twig\Error\SyntaxError: An exception has been thrown during the compilation of a template ("We found an unexpected slot that is not declared: [content]. Please declare them in "search-form.component.yml".") in "olivero:search-form". in Twig\Environment->compileSource() (line 524 of /data/vendor/twig/twig/src/Environment.php).What is a slot? Where do I find information on slots? After some poking around I eventually realised it refers to
{% block content %}in the twig template. I had a look at the schema and found slots next to props with the same schema so I added slots to my yaml file. Since it takes the same schema as props I just copy/pasted that directly and left only thecontentproperty. That lead to the following error:OK, so it can only be a string, what's the point declaring its type if it can only ever be "string"?
The next thing I wondered, do I really have to pass all the variables from one twig to another? And do I need to declare the props for title_prefix, title_suffix, attributes, etc? I've declared them all, but opted not to pass them from the original twig files as that seems to happen automatically.
The final challenge I faced was that the order of the CSS files that were loaded had changed. This meant that the primary button hover/focus/active styles were taking precedence over the custom styles for the search submit button. For now I've added explicit hover/focus/active styles for this button, but it seems we could also just remove the
button--primaryclass.I also added a
@todocomment in the MR wondering if there is a better SDC way of doing this:$variables['content']['actions']['submit']['#theme_wrappers'] = ['input__submit__header_search'];Comment #4
e0ipsoThis is great feedback! Do you mind if I quote you in the SDC MR so we can talk about it there?
Comment #5
mstrelan commentedNo problem at all. I also raised a number of issues against cl_server and sdc_examples modules, but these are less relevant for core.
Comment #7
e0ipsoUnblocking this after SDC got merged into Drupal core.
Comment #9
gauravvvv commentedComment #10
e0ipsoI added some comments and suggestions in the MR.
Comment #13
quietone commentedThe Olivero theme was approved for removal in #3590816: [policy, no patch] Deprecate Olivero and move to contrib.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3595082: [meta] Tasks to deprecate the Olivero theme and the removal work in #3595085: [meta] Tasks to remove the Olivero theme.