Geoblock Registration 1.3.0

[newimage]

newimage submitted a new resource:

Geoblock Registration 1.1.1 - Geoblock

Compatible XF Versions 2.x 2.1 Additional Requirements Phar extension for php must be enabled

This XenForo 2.1 addon provides Geoblocking capabilities for user registration...

Read more about this resource...

 

[axtona]

thanks to dear member @jessy updated Geoblock Registration with a new update entry:

changelog

• bugfix: don't try to uppercase a null iso_code
• php 8 compatibility fix: don't set a default parameter before non-default subsequent parameters
• slight re-arrange to order of code logic for EU checking - no point checking anything related to EU blocking if we don't have EU blocking enabled
• rename table to xf_geoblock_cache to adhere to resource standards
• addon now requires php 7+
• explicitly check for phar extension on install
• add legacy upgrade from XF 1.5 to Setup...

Read the rest of this update entry...

 

[axtona]

thanks to dear member @jessy updated Geoblock Registration with a new update entry:

changelog

This update only contains the latest composer dependencies, there has been no change to the addon code. Upgrading is optional.

Read the rest of this update entry...

 

[Zechariah]

thanks to dear member @Zechariah updated Geoblock Registration with a new update entry:

changelog

Minor bugfix to explicitly enforce admin permissions on admincp tools
updated icon
latest composer dependencies

Read the rest of this update entry...

 

[axtona]

A new update for Geoblock Registration 1.3.0 is now available for free download. Big thanks to the contribution from our member @axtona !

2026-09-05

bugfix: a failed database download could silently reinstall the previous database - PHP caches PharData objects by path and the download always used the same temporary filename, so a second update within one process re-extracted the first archive and reported success
bugfix: the "not configured" message in the admin control panel linked to #geoblockDatabaseUrl, an option removed in 1.1.0, so the link landed on the option group rather than the field
run enqueuePostUpgradeCleanUp() on upgrade...

Read the rest of this update entry...