You can always use this "super-cool feature" with sub-domains of "craft.dev" or "ontherocks.dev"! You can have as many as you want:
Relevant link: http://buildwithcraft.com/help/license-enforcement
But the TLDR is that purchases are tied to your craft/config/license.key file and the purchase will follow that file wherever it goes.
So as long as your replication script ignores that file, you'll get a fresh one tied to Craft Personal Edition the first time that Craft sees it's has an ...
All Craft CMS updates are free of charge - including major versions. In other words, Craft 3 will be a free upgrade.
As announced under DotAll 2017, following the release of Craft 3 in April 2018, P&T is changing the pricing model for Craft CMS. In order to stay updated, Craft 3 sites will have to renew their license yearly (for a reduced fee; $39/...
As Luke referenced in his answer, you're mixing up two separate (but related) concepts.
Your license key is stored in your craft/config/license.key file. This file is automatically generated the first time you run Craft, and should always remain a part of your website. If you're using version control, make sure that it's included in your repo....
Sebastian, you can always work locally "for free", using "craft.dev" as host name.
Check the FAQs here at the bottom of the pricing page https://buildwithcraft.com/pricing
MAMP PRO makes it really easy to setup custom host names, btw.
From what I understand you can use the one licence key on multiple
environments but you can only then login to the Admin area from one of
Sort of – you'll be able to login everywhere, but if the license isn't valid the CP will be blocked behind a "upgrade-wall", prompting you to purchase a valid license or downgrading to Personal (the free edition)...
When you move the license to production you'll see a warning in the CP - you then have the option to transfer the license to the new domain. See here for more info.
Obviously then you'll get the warning in your development environment but that's something you can live with I assume!
I got the official answer from Brandon, here is the summary for anyone that might be in a similar situation:
I can do what I need with only one pro license
the main portal (acme.com) will run the "en" locale
additional domains will use different locales (en-uk for UK, etc.)
this will work even better in Craft 3.0 - there will be a support for "portal" and ...
I think it would be enough to delete the license.key file under
and purchase a new license. The key file will be re-generated.
Some more info in this answer, and here is how Craft decides if it is running on a public domain
1) Is there anything to say about a release date for Craft 4? And about around what time Pixel and Tonic consider it a stable release to be used in production?
Nothing official on either.
2) What will happen to the support and updates for Craft 3 once Craft 4 is out? Is there any roadmap showing support/update-cycles for Pixel and Tonic products?
http://staging-subdomain.mysite.com would be considered a dev domain because we look for any of those keywords in the subdomain part of the URL.
http://www-next.mysite.com would be considered a public domain because it does not meet any of the criteria.
I found a solution! I had my local environment setup with homebrew following this article's instructions. After looking at the php error logs, I uncommented always_populate_raw_post_data = -1 in the php.ini file found in /usr/local/etc/php/5.6.
I then restarted the brew services with brew services restart php56 (install brew services by tapping gapple/...
“Reactivate” is the button you are looking for. Try checking for updates so Craft gets updated license info – the Trial badge sholud go away once Craft realizes that it’s licensed to run Pro. (If not, please contact firstname.lastname@example.org and send in your config/license.key file, and we’ll sort it out.)
No, it doesn't match anything on the list:
After filing this request, the documentation has been improved to more clearly state that this is, in fact, an exhaustive list.
I have update the screenshot above accordingly.
If you create your folder structure like this:
And set the $craftPath variable in each index.php like this:
$craftPath = '../../craft';
It should do what you're looking for.
You won't be able to test the creation of user accounts without upgrading to Craft Pro. However, in development, you can run Craft Pro as a trial.
Is there a way I can try Craft Client or Pro out before buying?
Yes. As long as you’re running Craft CMS from a non-public-looking
domain name (e.g. “mysite.dev” or “...
Short answer is yes, that is entirely allowed. Great information has already been provided in Tom's answer and Adam's answer.
If you are already certain that you'll be purchasing a Craft Client account, then you won't have to do anything special to get the site working locally. As long as the same license key remains in your site, any purchased upgrades ...
The only way to stop the message appearing is using a domain ending in craft.dev
As long as your client doesn't mind seeing the message it is not a big issue.
Also, licences can easily be moved to a different domain when you go live. Purchase the licence now and when you access the cp from the live domain in production, simple click the 'transfer licence ...
Right now, contacting email@example.com is the only way to retrieve a lost license.key file.
In the future, once we add user accounts to buildwithcraft.com, we'll also be adding order and license management, so you'll be able to retrieve it from there as well.
I've responded to your ticket with your proper license.key file.
I was only able to answer this because the OP sent a support ticket to and was able to look at their database. :)
When the site was setup in Craft Pro trial mode, the content was built out with multiple locales and those locales were enabled for the sections.
Craft Personal only allows for 1 locale, so when you try to save an entry in a section that was ...
The question is, is there a multiple license discount?
We currently don't have an official policy, but to-date we've handled bulk discount requests on a case-by-case basis.
As the FAQ suggests, contact firstname.lastname@example.org :).
According to Pixel & Tonic:
Can I use Craft Solo for client work?
Technically yes, however, we don’t recommend it. Craft Solo is meant to be a solution for developers to get to know Craft and create one-off sites for themselves and their friends. We do not recommend giving admin access to non-developers and therefore strongly recommend that any ...
Take a look at Jake Chapman's Craft CMS - Boilerplate on GitHub. You simply copy or clone your Craft boilerplate for each new project, and then add a newly downloaded craft/app/ folder (wich is already on the latest Craft version) with a new license.key file to it.