Add a Test/Development Domain Option to License Activation

Currently, when working on a development or staging site, I need to:

Activate the license on the test domain

Complete development and configuration

Deactivate the license

Reactivate it again on the live domain

This back-and-forth process can become cumbersome during active development.

In addition, not all Pro features are available until the license is activated. When migrating a site, this means I must activate the license on the development domain in order to fully configure and test all Pro functionality. This adds additional workload and complicates the migration process.

There is also some uncertainty around how many times a license can be moved between domains, which makes the process feel slightly risky during extended development cycles.

Why This Would Be Helpful

Smoother Development & Migration Workflow – Developers typically build and test on staging environments before going live.

Full Access to Pro Features During Development – Essential when migrating galleries or rebuilding layouts.

Reduced Administrative Friction – Eliminates repeated activation/deactivation cycles.

Greater Transparency & Confidence – Removes uncertainty about activation limits.


Suggested Implementation Options

Allow one additional “Development” or “Staging” domain per license.

Automatically detect common staging patterns (e.g. dev., staging., localhost).

Offer a temporary secondary activation (e.g. 30 days) for migration purposes.

Or allow full Pro functionality on non-public/local domains without counting against the primary activation.

This improvement would make the licensing system more developer-friendly and significantly streamline migration workflows.

Thank you for considering this request. I greatly appreciate the ongoing development of Balbooa Gallery and the work your team puts into the product.