As per title... this has been resolved in AMS 2.2.6
Note: Probably not something that anyone has run into yet as its a pretty rare case, nontheless, I found this yesterday when doing some house keeping on one of my development environments and tweaked the moderator log handler to deal with this...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.