Cache-Monster
Cache-Monster copied to clipboard
supercool
Server Error 500 on entry update
After installing Cache-Monster I could not update any entries. On Save I got a server error 500. Uninstalling the plugin removed the problem, so I am pretty sure it is related. Craft version is up-to-date as of today. Let me know how I can provide additional information if it is helpful.
Hi, I'm sorry it took me a while to respond - I can’t replicate this. Perhaps you are on a lower PHP version? http://plugins.supercooldesign.co.uk/plugin/cache-monster/docs#requirements
@joshangell I just updated to 1.0 and I'm experiencing something similar. I didn't get a chance to test saving entries, but mine occurred with saving users. Immediately when saving, something crashes. I couldn't quite nail down whether it was apache, mysql, or what it was, but reverting the update put me back to normal.
I'm on PHP 7, latest version of Craft (2.5.2760). The logs didn't scream anything. Tomorrow I'm going to debug a little further and see what I can find.
@ChaseGiunta really weird, could you try with devMode turned on and see if it spits out a stack trace?
@JoshAinsworth Tried at this again... Tough to troubleshoot because it's only crashing on my production site. From my naive understanding, it seems that it locks up the either mysql or php process. Restarting either seems to resolve the issue, but I did notice mysql is still running once I restart it (meaning it didn't crash). There's nothing jumping out in any logs that say what's going on (craft logs w/ devMode enabled, or server logs).
I can confirm that it happens upon saving users AND entries, so I assume it's any element saving. The bug does NOT occur if I toggle OFF the "Enable cache warming?" setting in the Cache-Monster settings.
Hey @ChaseGiunta - I have begun to see some similar errors to this in my own testing now, which is good as I can begin to work on it! Essentially I think it is to do with the template caches criteria table getting quite large and the fact that it has to crawl this whole table before the element finishes saving.
I have some ideas about how to fix this - but I really need to be able to hook into the template caches service, which I can’t at present. I'll re-open and update when I have any further news!
Just to update you that this will be coming in v2 - which is in development in the v2 branch. Check out the roadmap there for how the new setup will work.
I also get this issue - But it's only when the site has a large amount of entries. In this case it was around 8,000+ entries. CacheMonster killed the CMS.
