- Issue created by @Cadencia
- Status changed to Closed: won't fixabout 2 years ago 6:02am 2 August 2023
- 🇮🇳India keshavv IndiaThis issue is already fixed. Please check with the latest code. 
 Thank you.
- Status changed to Needs workabout 2 years ago 6:11pm 4 August 2023
- 🇺🇸United States mlncn Minneapolis, MN, USAThis is a critical issue and warrants a release before deeming it fixed, please. 
- 🇺🇸United States MegaKeegManThis error still occurs in the 2.x-dev branch 
- Status changed to Needs reviewabout 2 years ago 4:51am 7 August 2023
- last updateabout 2 years ago 7 pass, 2 fail
- 🇮🇳India keshavv IndiaCreated patch for 2.xbranch from 3.x as it is already fixed there.
 Please review.
 Thank you.
- The last submitted patch, 6: 3378590-6.patch, failed testing. View results → 
- last updateabout 2 years ago 7 pass, 2 fail
- The last submitted patch, 8: 3378590-8.patch, failed testing. View results → 
- last updateabout 2 years ago CI aborted
- last updateabout 2 years ago 33 pass
- Status changed to RTBCabout 2 years ago 4:48pm 7 August 2023
- 🇺🇸United States MegaKeegManThanks very much, I have just tested the above patch (labeled patch 12 but in comment 11) and it appears to be working correctly on the 2.x branch. 
- Assigned to Grevil
- 🇩🇪Germany Anybody Porta WestfalicaThis is fixed in 3.x but due to the chances in CAPTCHA module, this now also needs to be fixed in 2.x 
- Issue was unassigned.
- Status changed to Fixedabout 2 years ago 2:20pm 9 August 2023
- 🇩🇪Germany Anybody Porta WestfalicaFixed, I'll tag a new 2.0.5 release. Thank you all! 
- Automatically closed - issue fixed for 2 weeks with no activity.