License Utilization in the File Manager For Dropbox | CodeConfig
CodeConfig File Manager for Dropbox logo

Integrate Dropbox

46
Getting Started
Purchase and License
Module Builder
File Manager
Settings
User Access
Media Library
Auto Synchronization
WooCommerce
Tutor LMS
Contact Form 7
Elementor Integration
Gutenberg Integration
Advanced Custom Fields
Troubleshoot
Others

License Utilization in the File Manager For Dropbox

This guide explains how license usage works at CodeConfig and how one license can be used across live, staging, development, and localhost environments.

Using One License for Live, Staging, Dev, and Localhost

By default, all CodeConfig products follow Freemius license rules that allow a single license to be used on one live (production) site along with any number of staging, development, or localhost versions of that same site.

Staging, development, and localhost environments do not count toward the license limit as long as the domain clearly indicates it is not a live site.

Domains Automatically Treated as Staging or Development

TLDs considered as dev or staging

  • *.dev
  • *.dev.cc
  • *.test
  • *.local
  • *.staging
  • *.example
  • *.invalid

Subdomains and hosting-based staging domains

  • local.*
  • dev.*
  • test.*
  • stage.*
  • staging.*
  • stagingN.* (SiteGround)
  • *.cloudwaysapps.com (Cloudways)
  • *.wpengine.com, *.wpenginepowered.com (WP Engine)
  • staging-*.kinsta.com, staging-*.kinsta.cloud (Kinsta)
  • *.instawp.co, *.instawp.link, *.instawp.xyz (InstaWP)
  • dev-*.pantheonsite.io, test-*.pantheonsite.io (Pantheon)
  • *-dev.10web.site, *-dev.10web.cloud (10Web)

Any localhost domain, with or without a port, is also treated as a localhost environment.

If a Dev or Staging Site Is Not Detected Automatically

If a staging or development site does not match any of the patterns above, the same license can still be reused.

  1. Deactivate the license from the Account page in the WordPress admin
  2. Activate the license on the desired site

No additional license is required.

Multisite Networks

For WordPress multisite setups, each subsite counts as a separate site by default. To activate a license across multiple subsites, the license must support that number of sites, or multiple licenses must be used.

Summary

  • One license covers one live production site
  • Staging, dev, and localhost sites are included
  • Automatic detection covers most common setups
  • Manual deactivation allows reuse if detection fails
  • Multisite networks require licenses based on subsite count