<p>There is a known issue where if you use a variable name 'entry' in any template involved in a Live Preview request (including layout templates), then it can cause the behavior you're seeing.</p>

<p>Some examples are:</p>

<pre><code>{% set entry = craft.entries. ... .find() %}
</code></pre>

<p>or</p>

<pre><code>{% for entry in craft.entries. ... .find() %}
</code></pre>

<p>The workaround is to rename that variable to something else.  <code>myEntry</code>, for example.</p>

CC BY-SA 3.0
2017-02-27T17:05:11.640Z
Is this still a problem in the current version (2.6.2963) of Craft? I’m having problems with live preview as well and wonder if this could be the cause.
periodical
CC BY-SA 3.0
2014-08-06T01:42:22.800Z
2014-08-06T01:42:22.800Z
Brad Bell
<p><strong>Be sure to look for JavaScript errors as well!</strong> I was having the same trouble with a CloudFlare-enabled site, and it turned out that the Rocket Loader feature was choking and keeping previews from working properly. Otherwise no <code>entry</code> variables in play.</p>

CC BY-SA 3.0
2015-02-20T21:08:24.717Z
2015-02-20T21:08:24.717Z
Matt Stein
<p>Brad &amp; Matt provided good suggestions, but we just found another case where this can happen – when <strong>using matrix blocks with special filters or conditions</strong>.</p>

<p>In Craft 2.6 I found that this line does <em>not</em> update during Live Preview, but instead uses the last saved revision:</p>

<pre><code>{{ entry.banner.type('bannerContent').first().bannerTitle }}
</code></pre>

<p>Whereas this line works fine:</p>

<pre><code>{{ entry.banner.first().bannerTitle }}
</code></pre>

CC BY-SA 3.0
2017-03-17T00:36:16.997Z
2017-03-17T02:26:13.333Z
2017-03-17T02:26:13.333Z
Simon East
<p>any help would be much appreciated.</p>

<p>I have Live Preview working on my entries ie. I can see and use the button, but the live preview won't update as I manipulate the content? It was working before so it is baffling me as to how it could stop working.</p>

<p>The only change I think I have made in that time is removing the open_basedir settings in my php.ini, but I wouldn;t imagine that would affect it?</p>

<p>Thanks,</p>

<p>Dc</p>

<p>UPDATE::</p>

<p>This is the htaccess code:</p>

<pre><code>&lt;IfModule mod_rewrite.c&gt;
    RewriteEngine On

    # Send would-be 404 requests to Craft
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !^/(favicon\.ico|apple-touch-icon.*\.png)$ [NC]
    RewriteRule (.+) index.php?p=$1 [QSA,L]
&lt;/IfModule&gt;
</code></pre>

CC BY-SA 3.0
2014-08-06T00:19:19.597Z
I had a smilar issue a while back: Can you post your .htaccess code, and also check whether your Inspector-Network-log shows something.
Victor
CC BY-SA 3.0
2014-08-06T00:28:03.680Z
What happens when in your network-logger when you change something during live-preview?
Victor
CC BY-SA 3.0
2014-08-06T00:29:42.347Z
There is this message not sure if its related: "Element was added to more than one selector" garnish-0.1.min.js:11
user630
CC BY-SA 3.0
2014-08-06T00:32:12.570Z
This is also coming up:: GET http://use.typekit.net/c/e41e7d/futura-pt:i3:i4:i5:i7:i8:n3:n4:n5:n7:n8.SH7:P:2,SH9:P:2,SH4:P:2,SH6:P:2,SHD:P:2,SHB:P:2,Y5K:P:2,SH3:P:2,SH5:P:2,SHC:P:2/d [HTTP/1.1 403 Forbidden 50ms]
user630
<live-preview>
Live preview not automatically updating
# Live preview not automatically updating

(Asked by: username_0 on 2014-08-06)

any help would be much appreciated.
I have Live Preview working on my entries ie. I can see and use the button, but the live preview won't update as I manipulate the content? It was working before so it is baffling me as to how it could stop working.
The only change I think I have made in that time is removing the open_basedir settings in my php.ini, but I wouldn;t imagine that would affect it?
Thanks,
Dc
UPDATE::
This is the htaccess code:

    RewriteEngine On

    # Send would-be 404 requests to Craft
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !^/(favicon\.ico|apple-touch-icon.*\.png)$ [NC]
    RewriteRule (.+) index.php?p=$1 [QSA,L]

**Tags:** live-preview

> **Comments:**
> **username_1**: I had a smilar issue a while back: Can you post your .htaccess code, and also check whether your Inspector-Network-log shows something.  
> **username_1**: What happens when in your network-logger when you change something during live-preview?  
> **username_0**: There is this message not sure if its related: "Element was added to more than one selector" garnish-0.1.min.js:11  
> **username_0**: This is also coming up:: GET http://use.typekit.net/c/e41e7d/futura-pt:i3:i4:i5:i7:i8:n3:n4:n5:n7:n8.SH7:P:2,SH9:P:2,SH4:P:2,SH6:P:2,SHD:P:2,SHB:P:2,Y5K:P:2,SH3:P:2,SH5:P:2,SHC:P:2/d [HTTP/1.1 403 Forbidden 50ms]  

---

## 3 answers

### Answer by username_2 on 2014-08-06. Score: 8

There is a known issue where if you use a variable name 'entry' in any template involved in a Live Preview request (including layout templates), then it can cause the behavior you're seeing.
Some examples are:
{% set entry = craft.entries. ... .find() %}

or
{% for entry in craft.entries. ... .find() %}

The workaround is to rename that variable to something else.  myEntry, for example.

> **Comments:**
> **username_3**: Is this still a problem in the current version (2.6.2963) of Craft? I’m having problems with live preview as well and wonder if this could be the cause.  

---

### Answer by username_4 on 2015-02-20. Score: 2

**Be sure to look for JavaScript errors as well!** I was having the same trouble with a CloudFlare-enabled site, and it turned out that the Rocket Loader feature was choking and keeping previews from working properly. Otherwise no `entry` variables in play.


---

### Answer by username_5 on 2017-03-17. Score: 1

Brad & Matt provided good suggestions, but we just found another case where this can happen – when using matrix blocks with special filters or conditions.
In Craft 2.6 I found that this line does not update during Live Preview, but instead uses the last saved revision:
{{ entry.banner.type('bannerContent').first().bannerTitle }}

Whereas this line works fine:
{{ entry.banner.first().bannerTitle }}


---

