Problem/Motivation

While running drush updatedb I have faced the following error:

>  [notice] Update started: daterange_compact_update_10001
>  [error]  Route "entity.daterange_compact_format.canonical" does not exist. 
>  [error]  Update failed: daterange_compact_update_10001 

Steps to reproduce

I am updating Drupal Core to 10.3, which might be the cause of the issue.

Proposed resolution

Remove canonical URL from the daterange_compact_format annotation, as it does not exist.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mauriciopieper created an issue. See original summary.

mauriciopieper’s picture

Status: Active » Needs review
mauriciopieper’s picture

StatusFileSize
new705 bytes

I have created an MR for this and here is a patch to avoid using the MR diff.

dpacassi’s picture

Receiving the same error when updating the database after updating Drupal core + contrib via Composer.
This patch fixes the issue.

joevagyok’s picture

Status: Needs review » Reviewed & tested by the community

Reviewed and tested. Moving to RTBC.

dunx’s picture

StatusFileSize
new54.4 KB

Also reviewed and tested. Admin screen now working as expected.

daterange_compact date format page screenshot

  • 52e02ca6 committed on 2.1.x
    Issue #3512773 Remove incorrect canonical URL from entity type...
erik.erskine’s picture

Status: Reviewed & tested by the community » Fixed

Committed, thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

dunx’s picture

Would be good to get credit for testing the fix. I'm not a dev - identifying, documenting and testing is how I contribute back to Drupal.

joevagyok’s picture

I agree, I always give credits for reviews and manual tests.

erik.erskine’s picture

Fixed, and thanks for your help :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.