How can I prevent my client from auto-updating Craft in production? I don't want them to run Craft updates on the production site, but the "updates" badge seems irresistible to them. I would prefer to run Craft updates in my dev environment, version control with Git, test, and then deploy at my leisure.
1
- 6My guess is that Craft's update badge was specifically engineered for irresistableness. I'm not even on the client side, and I still have to remind myself to play it cool.Matt Stein– Matt Stein2014-06-12 04:19:20 +00:00Commented Jun 12, 2014 at 4:19
Add a comment |
2 Answers
You can use the config/general.php file to specify whether auto-updating is allowed:
Craft 2
'allowAutoUpdates' => false https://docs.craftcms.com/v2/config-settings.html#allowAutoUpdates
Craft 3
'allowUpdates' => false https://docs.craftcms.com/api/v3/craft-config-generalconfig.html#property-allowupdates
Combined with a multi-environment configuration, this can be very helpful.
Admittedly, this doesn't prevent the "Updates are available" notification from appearing... There have been some discussions about future versions of Craft possibly adding a separate config setting which will allow you to disable that notification as well.
- 6Stop making your answer better than mine!2014-06-12 02:15:06 +00:00Commented Jun 12, 2014 at 2:15
- 4Lol... You may be overqualified to handle a question like this... Save your rep for those really complicated ones. ;)Lindsey D– Lindsey D2014-06-12 02:17:13 +00:00Commented Jun 12, 2014 at 2:17
- 5Perfect. If I want to hide the updates badge completely I'll just use your excellent CP CSS Plugin, Lindsey ;)Alex Kendrick– Alex Kendrick2014-06-12 02:34:06 +00:00Commented Jun 12, 2014 at 2:34
- Hadn't even thought of that! Great idea Alex!Lindsey D– Lindsey D2014-06-12 04:42:51 +00:00Commented Jun 12, 2014 at 4:42
There is an "allowAutoUpdates" config setting that you can set to false, which will disable auto-updating for a Craft install. Manual updating will still work, though.
- 3It would be nice to see this option available to check off in the user/user group control panel. You could disallow it for everyone, including Site Admins, then go back to each individual user and allow them to run updates. This way you can allow clients the peace of mind of having a super admin account (which they could still go and undo what you just did above) while making it difficult for them to run updates and possible mess something up.Stuart McCoy– Stuart McCoy2014-06-12 17:09:54 +00:00Commented Jun 12, 2014 at 17:09