<p>If you have gzip compression enabled (either at the PHP or Apache level), try disabling that and see if helps.  Obviously that's not a proper long-term solution, but if you leave it on and set the <a href="https://craftcms.com/docs/config-settings#runTasksAutomatically" rel="nofollow">runTasksAutomatically</a> config setting to <code>false</code> and setup a cron job as described in the docs, you can see if that helps as well.</p>

CC BY-SA 3.0
2016-03-24T16:39:09.653Z
2016-03-24T16:39:09.653Z
Brad Bell
<p>When saving an entry, Craft will sit endlessly waiting for the page to load. I've seen this behaviour intermittently in the past - but not for months. It's doing it again now though.</p>

<p>Seems to me to be related to PHP or Apache in some way. I can restart Apache and Craft will then work fine on the first save, but edit and save again and it'll sit spinning forever. The 'hung' save does actually work, you can see changes reflected by checking the front-end in a different browser. However, while the save 'redirect' is hung, you can't browse any of the website, back-end or front, from the browser you were using to edit the entry.</p>

<p>This is only happening on our staging server, not our local machines, though both run the same website and same database.</p>

<p>Staging is Debian Jessie, on PHP 5.6.17-0+deb8u1 and Apache/2.4.10 (Debian). Our local machines are Macs running PHP 5.5.31 and Apache/2.4.16 (Unix).</p>

<p>I haven't found a cause or solution, and there doesn't seem to be anything of use in the craft.log either (though I'm not sure what to look for).</p>

<p>(This post is a follow-on from <a href="https://craftcms.stackexchange.com/questions/11245/craft-hangs-when-updating-entry">Craft hangs when updating entry</a>, which never seemed to be answered definitively).</p>

CC BY-SA 3.0
2016-03-24T11:44:16.527Z
UPDATE: Disabling Dev Mode on the staging server seems to stop this issue from occurring. Which is half an answer, I guess!
Matt Wilcox
CC BY-SA 3.0
2016-03-24T16:00:00.477Z
If you clear the caches between saves does it work?
RitterKnight
<bug>
Craft hanging when updating an Entry
# Craft hanging when updating an Entry

(Asked by: username_0 on 2016-03-24)

When saving an entry, Craft will sit endlessly waiting for the page to load. I've seen this behaviour intermittently in the past - but not for months. It's doing it again now though.

Seems to me to be related to PHP or Apache in some way. I can restart Apache and Craft will then work fine on the first save, but edit and save again and it'll sit spinning forever. The 'hung' save does actually work, you can see changes reflected by checking the front-end in a different browser. However, while the save 'redirect' is hung, you can't browse any of the website, back-end or front, from the browser you were using to edit the entry.

This is only happening on our staging server, not our local machines, though both run the same website and same database.

Staging is Debian Jessie, on PHP 5.6.17-0+deb8u1 and Apache/2.4.10 (Debian). Our local machines are Macs running PHP 5.5.31 and Apache/2.4.16 (Unix).

I haven't found a cause or solution, and there doesn't seem to be anything of use in the craft.log either (though I'm not sure what to look for).

(This post is a follow-on from [Craft hangs when updating entry](https://craftcms.stackexchange.com/questions/11245/craft-hangs-when-updating-entry), which never seemed to be answered definitively).

**Tags:** bug
> **Comments:**
> **username_0**: UPDATE: Disabling Dev Mode on the staging server seems to stop this issue from occurring. Which is half an answer, I guess!  
> **username_1**: If you clear the caches between saves does it work?  

---

## 1 answers

### Answer by username_2 on 2016-03-24. Score: 1

If you have gzip compression enabled (either at the PHP or Apache level), try disabling that and see if helps. Obviously that's not a proper long-term solution, but if you leave it on and set the [runTasksAutomatically](https://craftcms.com/docs/config-settings#runTasksAutomatically) config setting to `false` and setup a cron job as described in the docs, you can see if that helps as well.


---

