- Status changed to Needs work
almost 2 years ago 3:54pm 21 January 2023 - 🇺🇸United States crutch
on 9.5.7 patches not applying. Both vertical and horizontal tabs have this issue. We won't be able to use tabs at this point in time.
- Status changed to Needs review
over 1 year ago 3:04pm 14 April 2023 - 🇺🇸United States bnjmnm Ann Arbor, MI
re #37 testing should never require installing a contrib module like field_group. Any issue fixed in core should be reproduceable with just core, otherwise its an issue that should be filed with the contrib module. In this case it is a confirmed problem.
To reproduce, you need to have a field inside a vertical tab that can fail validation. Usually, required and similarly validated fields are not inside tabsets in core
The easiest way to reproduce IMO is apply 2911932-30-test-only.patch from #30, which already reproduces the problem for the purposes of testing. Enable the
form_test
module (must have$settings['extension_discovery_scan_tests'] = TRUE;
).
Then go to form-test/group-vertical-tabs and enter "bad" into the input in "Second group element", go to an different tab, then submit to trigger an error.
It not working === it does not switch to second tab, where the error isProblem Happening
https://youtu.be/kYnLIIWCQesProblem Fixed
https://youtu.be/Ydr06gybiFIRe #37
on 9.5.7 patches not applying. Both vertical and horizontal tabs have this issue. We won't be able to use tabs at this point in time.
That makes sense as patches are built for the most recent dev branch, which is currently 10.1.x. This can probably be made into a 9.x patch pretty easily - if you have success with that perhaps upload it here for users who may also need it.
- Status changed to RTBC
over 1 year ago 12:24am 16 April 2023 - 🇺🇸United States smustgrave
Thanks for the clarity @bnjmnm and the youtube links!
Did as you suggested and used the form_test module for testing.
Patch works great! - last update
over 1 year ago 29,200 pass, 1 fail The last submitted patch, 30: 2911932-30-test-only.patch, failed testing. View results →
- last update
over 1 year ago 29,281 pass, 1 fail The last submitted patch, 30: 2911932-30-test-only.patch, failed testing. View results →
21:25 18:40 RunningThe last submitted patch, 30: 2911932-30-test-only.patch, failed testing. View results →
- last update
over 1 year ago 29,300 pass, 1 fail The last submitted patch, 30: 2911932-30-test-only.patch, failed testing. View results →
- last update
over 1 year ago 29,300 pass, 1 fail The last submitted patch, 30: 2911932-30-test-only.patch, failed testing. View results →
- last update
over 1 year ago 28,497 pass - Status changed to Needs work
over 1 year ago 7:34pm 24 April 2023 - 🇫🇮Finland lauriii Finland
Cherry-picked to 10.0.x. Still need a separate patch for 9.5.x backport.
- Status changed to Needs review
over 1 year ago 2:58am 27 April 2023 - last update
over 1 year ago 30,323 pass - 🇮🇳India gauravvvv Delhi, India
I have attached the re-rolled patch for 9.5.x
- Status changed to RTBC
over 1 year ago 4:16pm 27 April 2023 - last update
over 1 year ago 30,323 pass - last update
over 1 year ago 30,300 pass, 2 fail The last submitted patch, 49: 2911932-49.patch, failed testing. View results →
- last update
over 1 year ago 30,323 pass - last update
over 1 year ago 30,326 pass - Status changed to Fixed
over 1 year ago 7:12am 5 May 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
over 1 year ago 1:44pm 25 May 2023 I'm using a module that makes the log message field in the 'information' tab of drupal core required ( https://www.drupal.org/project/require_revision_log_message → ) and ran into this issue. Was hoping that this patch would address the issue but it does not seem to. If anyone has the capacity to assist that would be appreciated