Thread

I’d been editing a site’s index template with Mountee all morning, when suddenly I refreshed the home page and it disappeared. I closed Mountee and re-submitted the index template (which looked fine) for good measure. No dice.

I can navigate the admin panel normally, and can view any other page on the public site including 404’s. Surprisingly enough, there are no PHP errors. Safari gives me a blank page with a 200 response, while Chrome somehow gets a 500 error. It’s also worth noting that I hide index.php with htaccess, but visiting the URL with index.php directly produces the same result.

Neither template debugging and output profiling add anything to the blank response.

Any ideas?

After further investigation, I decided to set $debug to ‘1’ in index.php. I finally got a timezone error:

A PHP Error was encountered

Severity: Warning

Message: date_default_timezone_get(): It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected ‘America/Los_Angeles’ for ‘PST/-8.0/no DST’ instead

Filename: libraries/Core.php

Line Number: 254

I chased things around further and ended up setting a default timezone in php.ini and restarting Apache. This got rid of the PHP warning, but the blank home page persists. I followed the advice given in this bug report (https://support.ellislab.com/bugs/detail/13112/) just to be safe, and that had no effect.

After successfully replacing the template markup with the word ‘test’, I re-added chunks and finally isolated the line that causes a blank template:

{exp:ce_img:single src="{image:url}" width="650" height="390" crop="yes|center,center|0,0|yes" allow_scale_larger="yes"}

Despite working fine this whole time, it appears that the addon of my dreams is suddenly the culprit. Not sure what to make of this, or how it could possibly prevent the rendering of an entire page, but at least it’s something…

To conclude this conversation I’m having with myself: updating CE Image fixed the problem which remains unsolved. The wild goose chase has ended, though we have no goose.

Hi Matt,

I hope you don’t mind if I intrude on your conversation 😉

Have you contacted Causing Effect with your issue? Excellent troubleshooting, by the way.

Let me know what you turn up!

Cheers,

Hey Dan,

I was getting ready to drop a note at your suggestion, but stumbled upon this Devot:ee thread:
http://devot-ee.com/add-ons/support/ce-image/viewthread/3836

It looks as though a low memory limit can ultimately be the culprit. Even though my issue is on a 128M-limited MediaTemple DV server, a client may have uploaded a huge file that choked things up.

Hi Matt Stein,

Did you get a chance to go down the “low memory limit” path? Did that turn anything up?

I agree with Dan, excellent job troubleshooting.

We are here to help, just let us know if there is anything else we can help with.

Regards,

Hello Shane,

I’m (still) working on a deadline so I was simply happy to have the issue resolved with a fresh update of CE Image. After looking at the change log (http://www.causingeffect.com/software/expressionengine/ce-image/change-log), I think the problem was fixed in v2.3. My PHP memory limit is at 128MB, but CE Image may have accidentally forced it to be *lower* in prior versions. The One Image that threw everything off likely blew through memory in earlier versions, but processed normally as soon as CE Image got updated.

I’ve set my detective hat aside while I get back to wrapping up this site!

Hi Matt,

I understand. Lots to do, so little time to do it.

Thanks for sharing your process and updating the thread.

Glad things are working gain.

Cheers,