500 error after upgrading to moderation_dashboard 2.1.1 from 1.x

Well one different in the 2.x version is it doesn’t use panels anymore. Is the panels module being removed by chance?

Will also try to replicate

Just following up if you have anything from the logs?

So I tried to replicate locally again.

Installed 8.x-1.x of moderation_dashboard.
Switched to 2.0.x branch
Ran drush updb

>  [notice] Update started: moderation_dashboard_update_8102
>  [notice] views.view.moderation_dashboard did not exist module config was reimported
>  [notice] Update completed: moderation_dashboard_update_8102

The redirect route does change between the two branches
8.x-1.x is using 'page_manager.page_view_moderation_dashboard_moderation_dashboard-panels_variant-0'
2.0.x is using 'view.moderation_dashboard.page_1'

I did not run into a 500 error though.

I am trying to do the upgrade from 1.x to 2.x as well, but am running into the following issue, not sure if it is related:

 Do you wish to run the specified pending updates? (yes/no) [yes]:
 > 

>  [notice] Update started: moderation_dashboard_update_8102
>  [error]  Call to a member function delete() on null 
>  [error]  Update failed: moderation_dashboard_update_8102 
 [error]  Update aborted by: moderation_dashboard_update_8102 
 [error]  Finished performing updates. 
Failed to run drush updb: exit status 1

Patch contents removed at request of poster.

Yea I'm not taking 1.x down anytime soon just won't be putting any work (major issues excluded) into it. Especially since panels has been marked no further development.

Added a validation condition before deleting the items.

Another confirmation that our site ran in to this while upgrading. Took a long time to track down that this was the cause so I can't confirm that the patch in #13 solves the issue when first encountered but I can confirm that running the code after the delete in the update hook fixed our issue.

drush eval "\Drupal::service('config.installer')->installDefaultConfig('module', 'moderation_dashboard')"

Will go ahead and merge this at lest.

Not sure what happened there.

Upgraded to 3.1 for Drupal 11 , but 500 error after login is still there

What This Fix Does
Prevents the "Route 'view.moderation_dashboard.page_1' does not exist" error (HTTP 500 on login)
If the route doesn't exist, the exception is caught and the redirect is skipped
No service definition changes required
Minimal code change
This is the minimal fix that handles the missing route without adding dependencies or view checks. The error should now be resolved, and login will work even if the moderation dashboard route doesn't exist.

The previous Patch was only solving the 500 error but it was not redirecting the correct mod_dashboard page .

Problem
After the upgrade, the moderation dashboard uses Page Manager, but ResponseSubscriber.php still references the old Views route view.moderation_dashboard.page_1, which no longer exists.
Solution
Updated ResponseSubscriber.php to use the path directly (/user/{user}/moderation/dashboard) instead of the non-existent Views route.
Changes made:
Replaced Url::fromRoute('view.moderation_dashboard.page_1', ...) with Url::fromUserInput('/user/' . $this->currentUser->id() . '/moderation/dashboard')
This matches the path defined in the Page Manager config (page_manager.page.moderation_dashboard.yml)