Problem/Motivation

Plan to track the roadmap for the release 8.x-1.5, mainly because of #3333995: Wrong RouteObjectInterface for Drupal 10

Comments

RenatoG created an issue. See original summary.

josephcheek’s picture

At risk of adding a comment just to say +1, I would love to see this. +1.

ericgsmith’s picture

Bumping to major since 1.4 does not work on Drupal 10.1.

It seems multiple duplicates of this bug will keep getting raised and it has been fixed on the dev branch for months. Can we please get a release?

greg boggs’s picture

Before we tag the release, we need someone to actually test the dev branch, try at least most of the pages that might be funky (/user, a page view, home, a taxonomy term, an edit form), and report back. It's quite common for base features to get broken in dev branch because each patch gets tested individually, but no one tests the entire module set once it's been merged in a complete release.

ericgsmith’s picture

Hi Greg,

Thanks for your quick response.

I understand the need for testing - but as it stands the bugfix for #3333995: Wrong RouteObjectInterface for Drupal 10 is the only item committed in the 8.x-1.x branch, which has been RTBC'd / comitted AND reported multiple times with the same fix. It is also a well documented change in line with the deprecation change record.

I take the request for a release in that issue, the duplicate patch in #3377635: Error: Class "Symfony\Cmf\Component\Routing\RouteObjectInterface" not found and the duplicate request to tag a release #3355491: Tag and release 1.5 as current stable version is broken for D10 as evidence this fix has been widely tested and needed.

I'll also open up a new issue to add some test coverage - I hope this doesn't block a 8.x-1.5 release but would give you more confidence in the fixes provided by the community.

#3354782: The core_version_requirement is incorrect could also be added as part of the release to fix the version requirement - but given that the current published release is unusable for Drupal 10 I would again suggest just getting the already committed fix tagged as 8.x-1.5 and a release out the door. It will surely be less admin than closing all these duplicates that will continue to come up.

finn lewis’s picture

Yes please, just testing an upgrade on a site that uses current_page_crumb and it breaks badly.

I'll run with the dev release for now, but a 1.5 release would be very much appreciated.

Thanks for all your work on this!

greg boggs’s picture

Status: Active » Fixed

Thanks for the testing!

greg boggs’s picture

Status: Fixed » Closed (fixed)

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