The Forum has been Updated
The code has been upgraded to the latest .NET core version. Please check instructions in the Community Announcements about migrating your account.
changelog:
RC2 to RC3 July 4th
autoclean issue fixed
RC1 to RC2 status
*Banned users are now logged once more
*couple admin_ipgate.asp tweaks to ban dates
*dbs files fixed (I hope I got them all)
*logs have the ability to clean themselves after set amount of time (Yay!)
*various admin page tweaks
*Various CaSE SensItivE Fixes
*bug in inc_ipgate with cookies fixed
*Proxies-Shaggy may have fixed this one, his code is in use in inc_ipgate.asp
*Date issue using European date format fixed
no db changes between 2.3.4 to 2.44
Download at
http://www.snitzbitz.com/mods/details.asp?Version=All&mid=194
or
http://www.gpctexas.net/ipgate_v244.zip
Features/Improvements
-Paginated Logs
-Ban by username, ipaddress, and ipaddress subnet
-You can ban by either means above. If you decide to use a browser cookie, a cookie will be placed on the users computer which flags them by their status. If that user switches names or ip address, the cookie flags them and bans them. If their ip address or username is different, a new ban record is inserted to auto ban the new username and ip address. At this time, no on off switch available for the new auto ban feature.
-You can add a list of banned pages that all users whos status is set to blocked access, can not access.
-Cookies will expire based on the end date you specify when you ban someone. Once a cookie is on their machine they are flagged until the cookie expires. A cookie expire option has been added to help alieviate accidental range bans. Remember to expire a cookie for a week before deleting a ban.
-You can log all ips or only those specified to watch in the database.
-Admin ban prevention improved
-Works with Access, MS SQL, and My SQL
Support for mod should be asked in the mod implementation forum. Always test mod on a test copy of forum before implenting it live. Remember to backup your files/db before upgrading
<
RC2 to RC3 July 4th
autoclean issue fixed
RC1 to RC2 status
*Banned users are now logged once more
*couple admin_ipgate.asp tweaks to ban dates
*dbs files fixed (I hope I got them all)
*logs have the ability to clean themselves after set amount of time (Yay!)
*various admin page tweaks
*Various CaSE SensItivE Fixes
*bug in inc_ipgate with cookies fixed
*Proxies-Shaggy may have fixed this one, his code is in use in inc_ipgate.asp
*Date issue using European date format fixedno db changes between 2.3.4 to 2.44
Download at
http://www.snitzbitz.com/mods/details.asp?Version=All&mid=194
or
http://www.gpctexas.net/ipgate_v244.zip
Features/Improvements
-Paginated Logs
-Ban by username, ipaddress, and ipaddress subnet
-You can ban by either means above. If you decide to use a browser cookie, a cookie will be placed on the users computer which flags them by their status. If that user switches names or ip address, the cookie flags them and bans them. If their ip address or username is different, a new ban record is inserted to auto ban the new username and ip address. At this time, no on off switch available for the new auto ban feature.
-You can add a list of banned pages that all users whos status is set to blocked access, can not access.
-Cookies will expire based on the end date you specify when you ban someone. Once a cookie is on their machine they are flagged until the cookie expires. A cookie expire option has been added to help alieviate accidental range bans. Remember to expire a cookie for a week before deleting a ban.
-You can log all ips or only those specified to watch in the database.
-Admin ban prevention improved
-Works with Access, MS SQL, and My SQL
Support for mod should be asked in the mod implementation forum. Always test mod on a test copy of forum before implenting it live. Remember to backup your files/db before upgrading
<
Postet den
Thank you ... as always! <
<
Postet den
Ok it seems working, but ...
where is used strIPGateTyp (there was an incongruence between strIPGateTyp and strIPGateType..) variable that is inserted by dbs in config_new? It was used in inc_ipgate in previous versions , is it useful or we can delete it?<
where is used strIPGateTyp (there was an incongruence between strIPGateTyp and strIPGateType..) variable that is inserted by dbs in config_new? It was used in inc_ipgate in previous versions , is it useful or we can delete it?<
Postet den
Im thinking it might have been a typo will look through and make sure.<
Postet den
I think you can safely remove it. I dont see it used anywhere anymore. That variable was ported into strIPGatelog which now can be set as 0, 1, 2 which is the different logging levels. Before strIPGatelog and strIPGateTyp both referenced logging from the original author, in this release I merged them to keep my sanity.<
Postet den
ok thank you!!<
