<p>Nothing around trial usage has changed between Craft 2 and Craft 3, so as long as you follow this, it should work:</p>

<p><a href="https://craftcms.com/support/try-craft-client-pro" rel="nofollow noreferrer">https://craftcms.com/support/try-craft-client-pro</a></p>

<p>Just keep in mind (because it sounds like you're swapping license keys around) that license.key info is cached for 24 hours at a time, so be sure and clear <code>craft/storage/runtime/cache</code> in whenever you do something like that to get accurate results and hit the updates page if you need to force a call home to Craft's web services.</p>

CC BY-SA 3.0
2017-12-19T03:43:05.967Z
Thank you, Brad - I had named the local site with an extension .blog - which caused the issue.
Nutmeg
CC BY-SA 3.0
2017-12-19T00:14:12.407Z
2017-12-19T00:14:12.407Z
Brad Bell
<p>Craft Personal 3.0.0-RC2 doesn't show the Pro Trial offer anymore? Is that correct?
I did install a Pro License however this triggers the system to change the domain (from local dev to live) which is unwanted.</p>

<install>
Pro trial not showing
# Pro trial not showing

(Asked by: username_0 on 2017-12-18)

Craft Personal 3.0.0-RC2 doesn't show the Pro Trial offer anymore? Is that correct?
I did install a Pro License however this triggers the system to change the domain (from local dev to live) which is unwanted.

**Tags:** install

---

## 1 answers

### Answer by username_1 on 2017-12-19. Score: 1 | Accepted answer

Nothing around trial usage has changed between Craft 2 and Craft 3, so as long as you follow this, it should work:

<https://craftcms.com/support/try-craft-client-pro>

Just keep in mind (because it sounds like you're swapping license keys around) that license.key info is cached for 24 hours at a time, so be sure and clear `craft/storage/runtime/cache` in whenever you do something like that to get accurate results and hit the updates page if you need to force a call home to Craft's web services.

> **Comments:**
> **username_0**: Thank you, Brad - I had named the local site with an extension .blog - which caused the issue.  

---

