- 🇺🇸United States joshf
Attached is a patch that will apply cleanly to the 8.x-1.3 version packaged by d.o.
- First commit to issue fork.
- 🇨🇴Colombia aldibier Manizales
I confirm patch #5 works to fix compatibility with Drupal 10.
- Status changed to RTBC
over 1 year ago 3:15pm 9 November 2023 - 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Balu Ertl → made their first commit to this issue’s fork.
- Merge request !1Issue #3286684 by joshf, jkamizato: Add support to D10 → (Merged) created by Balu Ertl
- Assigned to Balu Ertl
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Thank you @joshf, @jkamizato, @aldibier for your time dealing with this ticket.
- Issue was unassigned.
-
Balu Ertl →
committed 3c7623a6 on 8.x-1.x
Issue #3286684 by joshf, jkamizato: Add support to D10
-
Balu Ertl →
committed 3c7623a6 on 8.x-1.x
- Status changed to Active
about 1 year ago 9:00pm 13 February 2024 - 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
1. Accept automated patches until this issue is closed
Still leaving the ticket open to keep receiving possible further automated patches in the future.
- 🇺🇸United States dmundra Eugene, OR
Thanks @Balu Ertl, could you create a new release for the Drupal 10 version so folks can use that instead of dev branch?
- Status changed to Fixed
3 months ago 5:51pm 5 January 2025 - 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Thanks for everyone for their patience, here we go: 8.x-1.4 →
It’s worth noting a small UI improvement: following the convention of similar contrib projects (eg. config_export_ignore, config_export_json, config_devel, config_ignore, config_split, etc.), I’ve updated the package name on the Extend page from the rather generic “Development” to the more descriptive “Config” group:
Automatically closed - issue fixed for 2 weeks with no activity.