Closed (fixed)
Project:
Views URL alias
Version:
3.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
1 Oct 2025 at 20:59 UTC
Updated:
27 Dec 2025 at 07:24 UTC
Jump to comment: Most recent
If we can make a 3.1.1 release, this module will be D11 compatible and recent bug fixes will be available.
Examining the repo graph, commits for the following issues have been made since the 3.1.0 tag:
These are all bug fixes or deprecations and not new features. That should qualify as a patch release. The last pipeline shows a phpcs error.
Get tests passing on 3.x and make a patch release to release these six issues that are fixed.
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
Comment #3
fathershawnComment #4
fathershawnThe referenced CR has the simple fix as moving these functions to the .module file. That seems appropriate for the scope of this issue.
Comment #5
fathershawnAdded a simple functional test that installs the module and verifies the settings page loads. Test passes in D10 and D11.
Comment #6
fathershawnComment #7
goldI'm very keen to get this landed as well.
This project doesn't appear to have a composer.json file though. I do my testing of MRs that touch the core_version_requirement for D11 compatibility by adding the project to the repositories and pulling that using composer. Without that composer.json though, it's not pulling the repo.
What am I missing? Is there another process for checking out an MR for projects without a composer.json?
Comment #8
goldEnded up checkout out the repo locally and testing that way.
Followed the very brief 2-step guide in the README to enable this on the /admin/content View. Added multiple nodes with various URL aliases. Filtering on the path works for me.
This is working as advertised on 10.5.4 and 11.2.5.
I'd consider this RTBC.
Comment #9
fathershawnAdded the composer.json noted in #7
Comment #10
manuel garcia commentedRe: https://git.drupalcode.org/project/views_url_alias/-/merge_requests/36/d...
Should we drop compatibility with D8 and 9? Late-upgraders will need to upgrade to D10 before going to D11 anyway.
Comment #11
rachel_norfolkDoing a little tidy on last couple of issues and yes, I plan to make a release
Comment #12
rachel_norfolkokay, happy with the MR
Comment #13
rachel_norfolkI’m not against doing that but it would be a “breaking change” and, therefore, 4.x release in my mind.
Comment #14
rachel_norfolkMerged the MR but keeping ticket open until I’ve made a release...
Comment #15
rachel_norfolkUrgh - curse this half-way house of drupal/gitlab - I pressed Merge without manually adding in the merge commit message from the contribution record. Now trying to decide if I want to do a
git commit --amend && git push --forceComment #17
rachel_norfolkI think we can mark this closed now. Thanks all!