The "dashboard" parameter was not converted for the path

Facing the same issue, when installing from the UI

Troubleshooting:

• Working in LAMP - physical with no VM
• Facing the issue in DDEV version v1.24.0

• drupal-cms--LAMP.txt →
• drupal-cms--DDEV.txt →

→

-

Thanks! I am reproducing this. Assigning to myself to investigate.

Update: I tried the steps to reproduce on a composer create-project drupal/cms:1-rc1 codebase. It worked there. But it consistently fails with the git clone.

So there's your workaround for now: use the 1.0.0-RC1 zip file, or composer create-project, to set up the code base. (That's if you just want to try out Drupal CMS. You only need to use the git clone if you intend to contribute code to this project.)

Will continue to poke at this to see why the git clone is broken.

A little romp with git bisect showed that this was broken by, of all things, 📌 Figure out how to handle the site timezone Active .

I am not sure why; I suspect it's because core's timezone.js tries to make a sneaky AJAX request, which is probably warming some cache somewhere that shouldn't be. (Maybe it's building the router table, and the recipe system doesn't request a router rebuild, even though it definitely should.)

The workaround is to make the timezone selection thing visually hidden, rather than changing it to a hidden field. I think that's an acceptable workaround. Just need to figure out how to write some test coverage so we can prevent this from regressing again.

I tested it, @rajab natshah tested it, and I think we're happy here. I can't add test coverage for this because it will not be reproducible with JavaScript disabled (assuming the problem is triggered by the AJAX request to set the timezone, which I'm about 98% sure is the cause of the problem). So hopefully a detailed comment in the code is enough to prevent this from regressing.

Merged into 1.x, thanks for reporting and testing this!

So for a relatively non-technical user who has downloaded and installed the release candidate as promoted, and got this error, what can I do to get my site working?

I'm now seeing at https://drupal-cms.ddev.site/admin: Error: Call to a member function getPath() on null in drupal_cms_installer_theme_registry_alter() (line 286 of profiles/drupal_cms_installer/drupal_cms_installer.profile).

That is a known, but unrelated problem that has its own issue: https://www.drupal.org/project/drupal_cms/issues/3493710 🐛 Running the installer leads into a wsod Active

I am still getting error after installation at
https://drupal-cms.ddev.site:8443/admin/dashboard/welcome?check_logged_in=1

The "dashboard" parameter was not converted for the path "/admin/dashboard/{dashboard}" (route name: "entity.dashboard.canonical")

@rushikesh raval, make sure you try again with the latest version of the installer from https://new.drupal.org/drupal-cms/release-candidate. Does it still persist?

I see the same error using the latest zip archive from https://new.drupal.org/drupal-cms/release-candidate

Welp, I guess it regressed. Wonder what did it! It's too bad I couldn't add test coverage before; maybe that's what's needed here.

I am having trouble reproducing this, but I have a theory.

Due to something that went wrong while releasing RC1 (hi, Murphy's Law!), it is possible to have a 1.x-dev release of the installer, while having 1.0.0-rc1 releases of the recipes, in the same code base. Normally this should never happen, and indeed, when we tag RC2, it won't.

But try this:

1. Edit composer.json and change all the constraints on drupal/drupal_cms_WHATEVER to 1.x-dev.
2. Run the following:
   

   ddev drush sql:drop -y
   ddev composer update
   ddev launch
   

3. Go through the install again.

Do you still get this problem?

@phenaproxima I have Tried the step given in #22.

But still same issue.

When try to access other pages

The website encountered an unexpected error. Try again later.

Error: Call to a member function getPath() on null in drupal_cms_installer_theme_registry_alter() (line 286 of profiles/drupal_cms_installer/drupal_cms_installer.profile).
Drupal\Core\Extension\ModuleHandler->alter() (Line: 434)
Drupal\Core\Theme\Registry->build() (Line: 276)
Drupal\Core\Theme\Registry->get() (Line: 88)
Drupal\Core\Utility\ThemeRegistry->initializeRegistry() (Line: 69)
Drupal\Core\Utility\ThemeRegistry->__construct() (Line: 314)
Drupal\Core\Theme\Registry->getRuntime() (Line: 194)
Drupal\Core\Entity\EntityViewBuilder->getBuildDefaults() (Line: 157)
Drupal\Core\Entity\EntityViewBuilder->viewMultiple() (Line: 123)
Drupal\Core\Entity\EntityViewBuilder->view() (Line: 134)
Drupal\Core\Entity\Controller\EntityViewController->view()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 593)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 183)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 709)
Drupal\Core\DrupalKernel->handle() (Line: 19)

        "drupal/drupal_cms_starter": "1.x-dev",
        "drupal/drupal_cms_analytics": "1.x-dev",
        "drupal/drupal_cms_accessibility_tools": "1.x-dev",
        "drupal/drupal_cms_ai": "1.x-dev",
        "drupal/drupal_cms_blog": "1.x-dev",
        "drupal/drupal_cms_case_study": "1.x-dev",
        "drupal/drupal_cms_events": "1.x-dev",
        "drupal/drupal_cms_forms": "1.x-dev",
        "drupal/drupal_cms_news": "1.x-dev",
        "drupal/drupal_cms_person": "1.x-dev",
        "drupal/drupal_cms_project": "1.x-dev",
        "drupal/drupal_cms_seo_tools": "1.x-dev"

I have changed above lines and added 1.x-dev then removed vendor, composer.lock, and web/core. After that I have executed

    ddev drush sql:drop -y
    ddev composer update
    ddev launch

Still I am getting the same error. My choice Blog and News option from first screen.

Hi,
I have Installed Drupal CMS ^11.1-rc1. Encountered 'The "dashboard" parameter was not converted' error on /admin/dashboard/{dashboard} during welcome page redirection, but drush cr resolved it temporarily. Will debug further for a permanent fix.
Thanks!

have also executed ddev drush cr

It gives following output and after that refreshing page. Its working.

In EntityTypeManager.php line 139:
                                           
  The "block" entity type does not exist.  
                                           

Failed to run drush cr: exit status 1

RC2 was released yeaterday. Try creating a new project with that and see if this persists?

Created project with RC2 still problem persist. It works after ddev drush cr. as per comment #27

I found two warning message in admin/reports/dblog

1. The "field_block:node:page:field_content" block plugin was not found
2. The "extra_field_block:node:page:links" block plugin was not found

Yeah, the extra warnings are a known thing, but aren't related to this.

Yes, I have just post here this error for your information.

But still same issue continue.

It working fine in Apache+PHP8.3+Postgresql on Linux. But in DDEV we need to use ddev drush cr after installation.

There have been some really interesting developments over in 🐛 Running the installer leads into a wsod Active . Our current prime suspect (hah!) is a stale container hanging around in the cache.

I'd say let's keep this bug postponed on that one. When that one is fixed, we'll see if this problem persists.

The other issue is in, so on the latest 1.x...does this still happen for you?

If not, let's mark this one closed as a duplicate. :)

This issue also fixed. I have reviewed & Tested