2 December 2009

Fatal Error: Allowed Memory Size Fix for ExpressionEngine 2.0 PB

I’ve been running a couple of tests with a new installation of Expression Engine 2.0 Public Beta. Everything has been running pretty smoothly, but I did run into an error when I tried to edit existing pages added during the installation (if you selected to have Agile Records added).

When trying to edit an entry would get:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 311296 bytes) in...

A quick workaround for this is to add the following line of code at the top of your admin index.php page.

1
ini_set('memory_limit', '32M');

I’m only running a local version on my MacBook Pro MAMP PRO setup for my own testing purposes so this is going to be pretty isolated, but I thought I’d post this in case somebody else runs into the same snag.

Continue Reading

28 July 2009

"No input file specified." ExpressionEngine Issue Resolved

This morning I woke up to a downed site. I could log into the administration section of the site, but none of the public-facing pages worked. Looks like this might be specific to ExpressionEngine on Dreamhost, but I’m not completely sure about this.

Since we hadn’t made any changes to the site in a long while I was a little confused about what could be causing the issue. Turns out it ended up being a small change that was needed in the .htaccess file.

Here is a copy of line 3 in the .htaccess code before the change:

RewriteRule ^(.*)$ /index.php/$1 [L]

Turns out that I just needed to add a ‘?’ right after the ‘php’ like this:

RewriteRule ^(.*)$ /index.php?/$1 [L]

Once I made this little change everything was back up and running.

Again, this change looks like it was specific to Dreamhost. I checked out a few other sites that use ExpressionEngine on other hosts where I know the .htaccess file hasn’t been changed, and they are still up and running.

If somebody else knows what might have caused the change in functionality please feel free to weigh in.

Continue Reading