- Issue created by @simon-p
- πΊπΈUnited States jcontreras
This was an old issue fixed in 2.1.2, I ran a test and did not have that issue.
Are you sure you are on version 2.1.2 or 2.2.0 and _not_ in 2.1.1? - π¨π¦Canada simon-p Vancouver
Thanks for the quick reply.
Yes, can confirm using module version 2.1.2 and Drupal 10.3.13 as in screenshots.
- πΊπΈUnited States jcontreras
Try updating the module to 2.2, run database updates, clear the cache, and see if that fixes the issue.
- π¨π¦Canada simon-p Vancouver
Great, thanks, that did the trick.
Working as expected now.
Automatically closed - issue fixed for 2 weeks with no activity.