Skip to main content

Upgrade Guide

This guide provides a conservative upgrade process for Extendy GeoShield. Always follow any release-specific notes supplied with your addon package.

Before you upgrade​

Before replacing addon files:

  1. Back up the WHMCS database.
  2. Back up the existing modules/addons/extendy_geoshield/ directory.
  3. Confirm you have administrator access to WHMCS.
  4. Confirm the WHMCS daily cron is healthy.
  5. Review any release notes supplied with the new version.

Do not modify WHMCS core files as part of an Extendy GeoShield upgrade.

Update the addon files​

Replace the existing Extendy GeoShield addon files with the files supplied for the new version:

modules/addons/extendy_geoshield/

Keep the directory name as:

extendy_geoshield

Do not remove the addon database tables during an upgrade.

Activation and schema readiness​

Extendy GeoShield activation prepares missing addon schema, default settings, and email templates in an idempotent way.

If the release notes for your version require reactivation or another WHMCS-supported admin action, follow those release notes. Do not invent or run manual database migration commands unless they are provided by Extendy for that release.

Deactivation preserves addon data, but deactivation is not required purely to delete or reset data. Do not deactivate with the expectation that it will remove tables or settings.

Post-upgrade checks​

After updating files:

  1. Open the Extendy GeoShield addon admin page.
  2. Confirm the page loads without errors.
  3. Review Settings and confirm key values such as Addon Enabled, Alert Mode, GeoIP Provider, Client IP Source, and Retention.
  4. If provider credentials are configured, run GeoIP Provider Test Connection with a public test IP.
  5. Confirm the Login Events page loads.
  6. Perform a controlled client login test in a safe environment.
  7. If email alerts are enabled, verify email delivery only with a controlled test Client Account.
  8. Confirm WHMCS cron continues to run normally.

Data preservation​

The upgrade process should preserve:

  • addon settings;
  • encrypted provider credentials;
  • login event records;
  • Smart Mode known countries;
  • trust token records;
  • Extendy GeoShield email templates.

Do not manually drop addon tables during an upgrade.

If something goes wrong​

If the upgraded addon page does not load or validation fails:

  1. Stop further changes.
  2. Preserve logs and the current addon files for review.
  3. Restore from the verified file/database backups if needed.
  4. Contact Extendy support or your implementation partner with the safe error details.

Do not include provider credentials, raw trust tokens, database credentials, session data, or other secrets in support messages.