- Issue created by @brandonburketticf
- Status changed to Fixed
almost 2 years ago 5:14pm 3 August 2023 After further inspection, it appears this issue was fixed between release 2.0.0 and development version 2.0.x-dev.
After further inspection, it appears that this issue was fixed between release 2.0.0 and development release 2.0.x-dev.
Automatically closed - issue fixed for 2 weeks with no activity.