hi franki.

ISOCOM?

It sounds just an issue that xoops.org sets the Protector too sensitive.

Just set them "Sanitizing" or "None".
"Action if an isolated comment-in is found"
"Action if a UNION is found"

This is not a problem of Protector but the site.
Claim it to the administrator of the site.


And, Protector has already moved into "DBLayer Anti SQL Injection".
Both "ISOCOM" or "UNION" were older and useless way, now.