Errors when changing the default home page from /welcome to another.

Ps.
I reinstalled a clean install of Droopler 5.0.10 - I didn't change the language or install any modules - I changed the default homepage to /home-page and got the same result. The homepage css is messed up. After restoring /welcome the css error remains with the effects described above.

I ran across this same issue with Droopler 5.0.11 after changing the default landing page from /welcome to /home-page in the DDEV instance.

Error: Drupal\Core\Render\Component\Exception\InvalidComponentException: [droopler_theme:html/root_path] Boolean value found, but a string or an object is required. The provided value is: "". in Drupal\Core\Theme\Component\ComponentValidator->validateProps() (line 231 of core/lib/Drupal/Core/Theme/Component/ComponentValidator.php).

Related issue, same error, "Boolean value found, but a string is required in..."
https://www.drupal.org/project/radix/issues/3419776 🐛 InvalidComponentException: [configuration.label_display] Boolean value found, but a string is required in ComponentValidator->validateProps() (line 205...) Active

Resolved this by making the change below
File Path: themes/custom/droopler_theme/components/html/html.component.yml

props:
  properties:
    root_path:
      Original type: string -> New type: ['string', 'boolean']

Related issue, same error, "Boolean value found, but a string is required in..."
https://www.drupal.org/project/radix/issues/3419776 🐛 InvalidComponentException: [configuration.label_display] Boolean value found, but a string is required in ComponentValidator->validateProps() (line 205...) Active

Resolved this by making the change below
File Path: themes/custom/droopler_theme/components/html/html.component.yml

props:
  properties:
    root_path:
      Original type: string -> New type: ['string', 'boolean']

After further investigation, in a new DDEV instance with Droopler 5.0.11, any page set as the new Default Front Page throws this error. Even changing to something else, then back to the previously working /welcome throws this error.
The change I proposed allows the new Default Front Page to load, but has the side effect of removing the Main Navigation bar at the top of said Default Front Page.
Continuing to investigate.

Thanks for reporting this. I added this on our next tasks list 🌱 [META] Priorities & next tasks - Droopler 3.x and 5.x Active

Not sure if it's related, but after setting the root_path type to ['string', 'boolean'], the main navigation is not being rendered anymore in the path, and it seems radix is being used for the front page instead of droopler

Any suggestions?