I have just come across with a weird possible bug in Shibby’s Access Restrictions.
It seems that the command to Activate / Deactivate the rules (command “rcheck” triggered by a cronjob) only works as it should if the rule number is up to 31. More precisely the rules are activated fine but not deactivated if the rule number is higher than 31.
Trying to make a long story short of how I found out the issue.
I had several Access Restrictions rules, some of them are just to avoid some clients...
Shibby Access Restrictions (possible) bug
It seems that the command to Activate / Deactivate the rules (command “rcheck” triggered by a cronjob) only works as it should if the rule number is up to 31. More precisely the rules are activated fine but not deactivated if the rule number is higher than 31.
Trying to make a long story short of how I found out the issue.
I had several Access Restrictions rules, some of them are just to avoid some clients...
Shibby Access Restrictions (possible) bug