FAQ: Development Licenses

Which domains qualify for development licenses?

The following generic domains are currently whitelisted for development licenses: localhost, modmore, 127.0.0.1

You can also use any domain that ends with the following top level domains: *.dev, *.test, *.loc, *.local, *.localhost, *.project

To top it off, we also allow the following subdomains to install free development licenses: dev.*, develop.*, stage.*, staging.*, local.*, test.* , demo.*, next.* (Note that a subdomain is the 3rd level. For example stage.site.foo is valid, but stage.foo is not)

MODX Cloud users can also use free development users on their cloud domains, but will need a paid license once you add a custom domain.

On accepted development domains our Package Provider will show "Free to try on development" in the package name for the eligible Premium Extras. Any invalid licenses that are identified on a development domain will be automatically replaced by a new development license.

How do Development Licenses work?

With our free development licenses, you can try our Premium Extras on approved domain names, without needing a purchase. There is no limit on the number of development domains you can install it on, nor is there a time limit or restriction on features. These free development licenses allow you to try out all our extras, or start working on your client projects, and then purchasing the live licenses when it's ready to go live.

Do development licenses include support?

Officially support is limited to purchased licenses only, but we will of course try to answer any questions you may have, even if you've only been using a free development license.

We do reserve the right to ask you to purchase a license before offering our full support, so it can be useful to buy the license at the start of the project, just to avoid an awkward situation regarding supported status.

What happens if I migrate my dev site to a live domain?

We'll notify you that a new license is needed for the site. This happens via the email address on your account, and if no action is taken after two days we will also start showing messages within the manager that there is a license problem. This gives you some time to resolve the issue before your client gets spooked with scary license warnings.

These messages contain a link to our website where you will be able of selecting or purchasing appropriate licenses to update your site. Selecting a new license on the website will automatically update your site with the updated license key.

If a license issue isn't resolved after a week, you will find the package may be (partially) disabled in the back-end until a new license is in place.

For Unlimited License holders we'll automatically correct the license when you've migrated the site, so you wont receive an email.

Where is the license key stored?

The license key, also known as the public key, is stored in core/components/name-of-the-package/ and is a file called .pubkey. There's also a related .pubkey_c file in the same directory that contains the timestamp the license was last checked.

If you're using a workflow based on a version control system like git, you should exclude these files. If you don't, you might run into license issues during/after deployments, despite the proper licenses being available.

You normally don't have to update any of these files manually. Our license checks manage their contents for you, and automatically update it when a new license has been attached to a domain. It is also safe to remove them (e.g. if a package installation refuses to work because of a license issue) as they will be automatically restored.

Can I use development licenses on MODX Cloud?

Yes! We've also whitelisted MODX Cloud for development licenses. Please be aware that if you attach your Cloud to a live domain you will need a live license.

Can you add {some domain here} to the whitelist?

The development licenses depends on a whitelist of approved development domains and top level domains. We have the technical ability to add extra domains on request, however we will not be able of accommodating project-specific domains, such as a mystagingsite.com. Why? Simply because all our clients combined work on a lot of projects, and we want to focus our support time on helping our clients do cool things, rather than maintaining a large list of domains.

If your workflow follows a predictable pattern for development domains (for example all your development happens on a virtual .mycompany top level domain) we would be happy to add that to the whitelist on request. Just send us an email at [email protected]

Which packages are eligible for development licenses?

Free development licenses are available for all of our Premium Extras that support the 2017 version of our license system. With that in place we're able of offering development licenses.

Connect

Disclaimer: Viewing non-Euro pricing

You are currently viewing prices in a non-Euro currency. Please be advised that these prices are estimates, based on data by Open Exchange Rates.

While we offer this currency converter hoping our users find it convenient, all purchases are made in Euro, and the final amount charged can vary depending on payment provider, day, time of day and a number of other factors outside of modmore's control. There are no guarantees on accuracy and modmore nor Open Exchange Rates can not be held liable for errors.