Says its closed and fixed but its not
Can anyone help with the above issue? ^
Have you commented on the issue itself?
That's the best course of action if it says it's fixed, but isn't. That way the people who need to fix it will see
also, unless i’m missing something, that issue above (#100) is still open, not “closed and fixed”
This is also true 🙂
Can anyone think of a reason why setting my default spam protection in my yml wouldn't be getting applied? trying to use nocaptcha on ss4.4