Answers.Body: <p>Got to the bottom of it. It was a CORS thing - permission with the domain htaccess and elementAPI. A shift from non-www, to www redirection seemed to be the cause so now solved</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-07T10:44:32.050Z
Answers.LastActivityDate: 2019-02-07T10:44:32.050Z
Answers.UserDisplayName: joomkit
Body: <p>I have a site A using the Element API plugin to feed content to site B via JSON and handlebars templates. The process is both sites are up to date with content 'x' and it works fine.</p>
  
  <p>When I run the CP updates on site A and it finishes the data on site B never shows until the site A cache is cleared.</p>
  
  <p>Is this expected behavior?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-02-06T23:34:35.183Z
Comments.Text: Not sure I'm following 100%, but the data doesn't show up on the front-end of site B until you clear Craft's caches?  Are you using the template `{% cache %}` tag or some other caching solution?
Comments.UserDisplayName: Brad Bell
Tags: <cache><plugin-elementapi><updating>
Title: Craft update process affecting Element API cache
ThreadText: # Craft update process affecting Element API cache
  
  (Asked by: username_0 on 2019-02-04)
  
  I have a site A using the Element API plugin to feed content to site B via JSON and handlebars templates. The process is both sites are up to date with content 'x' and it works fine.
  
  When I run the CP updates on site A and it finishes the data on site B never shows until the site A cache is cleared.
  
  Is this expected behavior?
  
  **Tags:** cache, plugin-elementapi, updating
  
  > **Comments:**
  > **username_1**: Not sure I'm following 100%, but the data doesn't show up on the front-end of site B until you clear Craft's caches?  Are you using the template `{% cache %}` tag or some other caching solution?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-02-07. Score: 1
  
  Got to the bottom of it. It was a CORS thing - permission with the domain htaccess and elementAPI. A shift from non-www, to www redirection seemed to be the cause so now solved
  
  
  ---
  
  