Some mandatory parameters are missing ("machine_name", "step") to generate a URL for route "entity.page.devel_load".

I have, so far traced the issue to an update to Devel. That is the change in the versioning repot where this issue starts.

Downgrading Devel to 5.1.2 has cleared up the issue.

I have not gone into the code to see what has changed and why this is happening as yet.

Hi,
I have exactly the same problem.
With admin/structure/page_manager I see the same error but if I go directly with admin/structure/page_manager/manage/home_page/general the I can work with my page.

In Devel 5.1.x, Devel wouldn't try to alter the entity info due to how Page manager has a custom link template for editing the Page entity.

Devel 5.2.x changes that logic to always generate a Devel link template for the devel-load route. The route parameters in the custom edit link for the Page entity do not align with what Devel expects which ultimately is what causes this exception.

The attached patch updates the page_manager_ui module to alter the link template used by devel-load (if Devel is present).

amanmansuri72 → made their first commit to this issue’s fork.

Hello,

I can confirm, this patch working for me.
THX mediabounds →

The patch is working fine, but it has one more issue not working on devel URL.

Please find the screenshot for further reference.

Same issue here, page manager ui is inaccessible.

#5 fixes the issue, I'm just not sure if it's the correct fix.

Had to add two more Devel-related routes to #5 for Drupal 10.2.6 / Page Manager 4.0.0-rc2.

if ($entity_types['page']->hasLinkTemplate('devel-definition')) {
    $entity_types['page']->setLinkTemplate('devel-definition', '/devel/page/{page}');
  }
  if ($entity_types['page']->hasLinkTemplate('devel-load-with-references')) {
    $entity_types['page']->setLinkTemplate('devel-load-with-references', '/devel/page/{page}');
  }

I got around this by uninstalling the devel module using drush drush un devel.

The patch in #5 works like a charm.

@l_langill: I don't think this was committed? So please don't change the status to "fixed"! Read https://www.drupal.org/docs/develop/issues →

Based on the feedback I'm setting this RTBC but the maintainers should please decide if this patch is an acceptable solution.

#WOrks for me

Not quite sure what I want to do with this, as it seems to be a problem with devel more than Page Manager.. I'd rather not put devel specific code in the PM ui.

FWIW, I was torn whether to submit a patch to devel or to page manager on this. Devel needs to be able to generate routes and makes a mostly reasonable, albeit broad, assumption about the format of the edit link template. This works in most cases...unless an entity type changes their edit link template to have additional route parameters like how page manager UI does.

So either devel has to have page manager specific code or page manager needs devel specific code to resolve this. Since page manager UI is altering the convention used by most entities for an edit link template, it seemed reasonable to have it also fix the devel route, if devel was present.

Agree with #18! Thanks for the summary.

Anybody → changed the visibility of the branch 3438993-some-mandatory-parameters to hidden.

Anybody → changed the visibility of the branch 3438993-some-mandatory-parameters to active.

@japerry: I agree with

Since page manager UI is altering the convention used by most entities for an edit link template, it seemed reasonable to have it also fix the devel route, if devel was present.

Do you also agree?

I prepared MR!34 based on #5 and #12 thank you!
Please review.

Page Manager UI is currently unusable with Devel enabled, so I think priority is still major, but I didn't set it higher again as of #17 FYI.

Static patch attached, if someone needs it in the meantime!
https://www.drupal.org/files/issues/2024-08-14/page-manager-3438993-MR34... →

FYI: Just tried the patch for my case and it fixes all the issues with devel.

Thanks, Latest patch works like a charm on the latest 4.0.0-rc3.

#patch24 worked great thank you

patch #24 worked great thank you

I agree with #18 and #23, and I greatly appreciate the patch#24 !

+1 RTBC

@japerry could you have a look at #23 maybe and tell us, if you'd be fine with that?