<blockquote>
  <p>Does allowUpdates and allowAdminChanges affect whether or not content will be updated on the site?</p>
</blockquote>

<p>Nope.</p>

<blockquote>
  <p>Thought it might be a cache issue but why would it work on dev and not prod?</p>
</blockquote>

<p>Caching is my first thought. Is production behind a CDN, Varnish or some other caching solution that dev is not?</p>

<p>Maybe the <a href="https://docs.craftcms.com/v3/config/config-settings.html#enabletemplatecaching" rel="nofollow noreferrer">enableTemplateCaching</a> config setting is set to <code>false</code> for non-production environments?</p>

CC BY-SA 4.0
2019-02-14T11:58:33.327Z
Looks like the enableTemplateCaching is set to true on staging and prod. I am going to set it to false and see if that changes anything.
Jason
CC BY-SA 4.0
2019-02-14T12:15:36.870Z
Changed the settings and nothing changed. Going to look into it a little more today and tomorrow. Will update once I figure something out. Thank you for the response.
Jason
CC BY-SA 4.0
2019-02-14T00:00:31.250Z
2019-02-14T00:00:31.250Z
Brad Bell
<p>Hey there and thanks in advance. We just moved our site to production as a beta site. The only thing that is different between this site and our local/staging site is the config file. The allowUpdates and allowAdminChanges is set to false. Databases are separate and all sites are running.</p>

<p>We I update entries on prod, they save but my site does not update. When I do the same change on local/dev the changes render on my dev site. </p>

<p>Am I missing something? Does allowUpdates and allowAdminChanges affect whether or not content will be updated on the site? Thought it might be a cache issue but why would it work on dev and not prod?</p>

<p>Any thoughts on this would be greatly appreciated. </p>

<p>Thank you,</p>

<craft3>
Entries save but site doesn't update
# Entries save but site doesn't update

(Asked by: username_0 on 2019-02-13)

Hey there and thanks in advance. We just moved our site to production as a beta site. The only thing that is different between this site and our local/staging site is the config file. The allowUpdates and allowAdminChanges is set to false. Databases are separate and all sites are running.

We I update entries on prod, they save but my site does not update. When I do the same change on local/dev the changes render on my dev site.

Am I missing something? Does allowUpdates and allowAdminChanges affect whether or not content will be updated on the site? Thought it might be a cache issue but why would it work on dev and not prod?

Any thoughts on this would be greatly appreciated.

Thank you,

**Tags:** craft3

---

## 1 answers

### Answer by username_1 on 2019-02-14. Score: 1

> Does allowUpdates and allowAdminChanges affect whether or not content will be updated on the site?

Nope.

> Thought it might be a cache issue but why would it work on dev and not prod?

Caching is my first thought. Is production behind a CDN, Varnish or some other caching solution that dev is not?

Maybe the [enableTemplateCaching](https://docs.craftcms.com/v3/config/config-settings.html#enabletemplatecaching) config setting is set to `false` for non-production environments?

> **Comments:**
> **username_0**: Looks like the enableTemplateCaching is set to true on staging and prod. I am going to set it to false and see if that changes anything.  
> **username_0**: Changed the settings and nothing changed. Going to look into it a little more today and tomorrow. Will update once I figure something out. Thank you for the response.  

---

