- Issue created by @adambraun
- First commit to issue fork.
- Status changed to Needs review
over 1 year ago 10:39am 16 March 2023 - 🇯🇴Jordan Rajab Natshah Jordan
Facing the same issue.
Thanks, Adil for patch #5 - Status changed to RTBC
over 1 year ago 4:53pm 21 March 2023 - 🇧🇷Brazil elber Brazil
Hi I revised the patch.
It was applied cleanly.
Module keeps working
Issue has been fixed.
Moving to RTBC.
-
Rajab Natshah →
committed 4136e8de on 1.0.x authored by
Adil_Siddiqui →
Issue #3348151 by Adil_Siddiqui, adambraun: After upgrading to Drupal 10...
-
Rajab Natshah →
committed 4136e8de on 1.0.x authored by
Adil_Siddiqui →
-
Rajab Natshah →
committed 904106f9 on 1.0.x
Issue #3348151: Fix name of the Drupal.behaviors.sectionLibrary...
-
Rajab Natshah →
committed 904106f9 on 1.0.x
- Status changed to Fixed
about 1 year ago 7:26pm 29 June 2023 Thanks!
Also, I noticed there's no "1.1.x-dev" in the version dropdown for issues. Is that something you can add?
- 🇯🇴Jordan Rajab Natshah Jordan
I have no access permission to do that.
The creator of the module can do that for sure. - 🇨🇦Canada mark.labrecque Vancouver
I don't think this release took. I just updated to 1.1.1 and the error code state still exists. On top of that, for some reason the patch in here doesn't apply cleanly, I had to reroll it. We may want to re-open this issue
Automatically closed - issue fixed for 2 weeks with no activity.