I just updated my site to 2.1.2 from 1.8.1 and installed Ban 2.0.1 (among other things) and am having some trouble restoring some custom functionality I had with the old site.
Back in the good old days
I would have the banned individuals redirected to a special page (
http://BlogDogIt.com/errors/BlogDogIt403.php[*1] ) This page would display their address and instruct them to click on the displayed IP to request removal from the ban list (since I tend to be heavy-handed with the IP Range blocks I have been known to block-out my friends on occasion)
I found that opening the "error" folder to
allow from all via .htaccess they were able to at least gain access to those scripts.
Nowadays however, no matter what I try I cannot get the redirect to do anything other than a refresh loop. I read the caution in /admin/plugins/ban/readme.html and have tried using the example "GO AWAY" html page but same deal. I have tried entering an address to another domain even, but cannot get past the refresh loop (which the readme.html typo-ly terms "refresh
look" - btw)
So I guess I am unclear as to exactly where should I place the custom 403 message on the site so it is not considered "one of our Geeklog Pages" so as to avoid the loop. I had thought if I could no longer run my php scripts (which I was thinking I could possibly white list them for access) then perhaps I could redirect to an off-site location using a meta refresh in the go-away page.
Any help would be appreciated - If I figure something out I'll let you know.
You found a bug!
I fixed it at
Github[*2]
Or you can open up functions.inc in a text editor in the plugins/ban/ directory and update line 713 too:
Text Formatted Code
echo COM_redirect($_BAN_CONF['page']);
What was happening was the ban configuration page value was not being used and just an empty variable was being passed which resulted in the loop.
Thanks for the report.
BINGO!
Hey, thanks for the prompt fix on this Laugh!
~~Patch applied~~
Once more a happy camper - me