<p>@Dalton I would say that's indeed the issue (using the project.yaml file), at least at first glance. </p>

<p>Every time you're pushing the project.yaml file to your server, it'll overwrite your server's project.yaml file. Because the plugin isn't licensed locally, you're basically removing the license each deploy. </p>

<p>Can you register the license locally, then push your project.yaml file? You'll notice locally, as soon as you enter a license key, the file will change to store this license key. Things should stay in sync from then on.</p>

CC BY-SA 4.0
2019-09-10T14:11:51.387Z
2019-09-10T14:11:51.387Z
crawf
<p>I have licensed the Verbb Navigation plugin, but every time I update Craft I get a notice that the license needs attention. The key field on the Plugins page is empty after the update. Is this a bug, or is there another way to store the key so it will be saved after an update?</p>

CC BY-SA 4.0
2019-07-19T18:57:49.240Z
Odd... how are you updating/deploying Craft?
Brad Bell
CC BY-SA 4.0
2019-07-19T22:25:06.217Z
Update on a local dev machine via control panel, then deploy composer.json and run composer update on production machine.
Dalton Rooney
CC BY-SA 4.0
2019-07-19T22:27:00.697Z
We’re also deploying a project.yaml file from our local environment, where the plugin is not licensed. Could that be causing the problem?
Dalton Rooney
<plugins><license>
Plugin license key is lost every time I update Craft CMS
# Plugin license key is lost every time I update Craft CMS

(Asked by: username_0 on 2019-07-19)

I have licensed the Verbb Navigation plugin, but every time I update Craft I get a notice that the license needs attention. The key field on the Plugins page is empty after the update. Is this a bug, or is there another way to store the key so it will be saved after an update?

**Tags:** plugins, license

> **Comments:**
> **username_1**: Odd... how are you updating/deploying Craft?  
> **username_0**: Update on a local dev machine via control panel, then deploy composer.json and run composer update on production machine.  
> **username_0**: We’re also deploying a project.yaml file from our local environment, where the plugin is not licensed. Could that be causing the problem?  

---

## 1 answers

### Answer by username_2 on 2019-09-10. Score: 1

@Dalton I would say that's indeed the issue (using the project.yaml file), at least at first glance.

Every time you're pushing the project.yaml file to your server, it'll overwrite your server's project.yaml file. Because the plugin isn't licensed locally, you're basically removing the license each deploy.

Can you register the license locally, then push your project.yaml file? You'll notice locally, as soon as you enter a license key, the file will change to store this license key. Things should stay in sync from then on.


---

