- Issue created by @nico.b
- Merge request !6711"More" link not taking default arguments into account ā (Open) created by nico.b
- Status changed to Needs review
about 1 year ago 7:17am 21 February 2024 The fix might be easy. Before #981870 ā , the code part mentioned above did only run if default_argument_skip_url was set to TRUE. Since that setting has been entirely removed, I believe that we can completely delete that code section (instead of always running it, as it is now).
Created an MR.
- Status changed to Needs work
about 1 year ago 5:19pm 21 February 2024 - šŗšøUnited States smustgrave
Thanks for reporting,
Will need a failing test to show the issue.
MR target should be 11.x as the current development branch.
- last update
about 1 year ago Patch Failed to Apply - šŗšøUnited States smustgrave
FYI no need to upload test-only patches. That feature is in gitlab now.
- Status changed to Needs review
about 1 year ago 3:38pm 12 March 2024 Thanks for the info, @smustgrave. Then the test documentation ā is probably not up-to-date yet ;)
I've added a test case in the MR and changed the target to 11.x.
Ok, seems like there was indeed an issue in 11.x making the test fail. I've merged a fix from 11.x and now all tests are passing again :)
Also the test-only changes show the failing test case, so this issue should now be ready for review.
- Status changed to RTBC
about 1 year ago 5:47pm 12 March 2024 - š®š³India adwivedi008
MR at #09 seems good to me, it also passes test cases over the pipeline.
Moving the issue to RTBC.@smustgrave Please review and share if any other change is required.
- š¬š§United Kingdom alexpott šŖšŗš
I'm pretty sure this issue is correct and the way š Skip default argument for view URL does not work and never has so it can be removed Fixed was implemented was incorrect. But before we merge this it'd be great if the people who work on that issue add a +1.
I think the fact that no test coverage is changed here proves that core actually had no test coverage of what they were changing in that issue.
-
longwave ā
committed 01176760 on 10.2.x
Issue #3422710 by nico.b, smustgrave, adwivedi008, alexpott: "More" link...
-
longwave ā
committed 01176760 on 10.2.x
-
longwave ā
committed b2450c97 on 10.3.x
Issue #3422710 by nico.b, smustgrave, adwivedi008, alexpott: "More" link...
-
longwave ā
committed b2450c97 on 10.3.x
-
longwave ā
committed 49063a57 on 11.x
Issue #3422710 by nico.b, smustgrave, adwivedi008, alexpott: "More" link...
-
longwave ā
committed 49063a57 on 11.x
- Status changed to Fixed
about 1 year ago 9:38am 25 March 2024 - š¬š§United Kingdom longwave UK
Whoops, in the original issue we got the condition the wrong way round.
Committed and pushed to 11.x and 10.3.x, backported to 10.2.x as an eligible bug fix. Thanks!
Automatically closed - issue fixed for 2 weeks with no activity.