- Issue created by @arunkumark
- Status changed to Needs review
about 1 year ago 5:28pm 20 April 2023 - Open on Drupal.org →Core: 10.1.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Status changed to RTBC
about 1 year ago 5:32am 21 April 2023 - 🇮🇳India keshav.k
Reviewed and tested the patch. Working perfect, Moving to RTBC
- 🇮🇳India Raveen Kumar
I got the same error. Please see attached. I Applied & tested the patch, & it worked fine for me. Thank You.
- Status changed to Needs review
about 1 year ago 5:48am 21 April 2023 - Open on Drupal.org →Core: 10.1.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - 🇮🇳India Raveen Kumar
@Keshav, Patch #7 seems to be working fine. Thank You.
- Status changed to RTBC
about 1 year ago 6:27am 21 April 2023 - First commit to issue fork.
- 🇮🇳India urvashi_vora Madhya Pradesh, India
Thanks everyone for contributing.
- Open on Drupal.org →Core: 10.1.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - @urvashi_vora opened merge request.
- Open on Drupal.org →Core: 10.1.x + Environment: PHP 8.0 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass -
urvashi_vora →
committed e4e90f1d on 2.0.x
Issue #3355438 by urvashi_vora, arunkumark, keshav.k, Raveen Thakur:...
-
urvashi_vora →
committed e4e90f1d on 2.0.x
- Status changed to Fixed
about 1 year ago 3:46am 27 April 2023 Automatically closed - issue fixed for 2 weeks with no activity.
