ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Blank page in Edit/Publish areas on *MOST* weblogs after upgrade from 1.6.3 to 1.6.7

July 01, 2009 11:20pm

Subscribe [4]
  • #1 / Jul 01, 2009 11:20pm

    benjyrose

    16 posts

    Well, the title about says it all.  I finally upgraded from 1.6.3 to 1.6.7, went back in, and I can’t Edit or Publish entries in 7 of my 10 weblogs. The other three work just fine. I disabled extensions, to no effect.  I searched this forum, and it seems that people had similar issues, but they all seemed to be related to either language translations (I’m using English only) or extensions (they’re disabled).  What other info can I provide to maybe figure this out? 

    Build 20090320, BTW.

    thanks,
    benjy

  • #2 / Jul 02, 2009 1:38am

    John Henry Donovan

    12339 posts

    benjy,

    What behaviour are you experiencing when you do try to edit or publish?
    Are you receiving any sort of error message?

    Will you walk us through the steps you are taking to publish or edit a weblog?

  • #3 / Jul 02, 2009 7:17am

    benjyrose

    16 posts

    Sorry…I guess I wasn’t clear—I get blank pages in my browser when I try to edit or publish pages in 7 or the 10 weblogs.  No error message (display_errors is off in my php_info).

    Basically, in 3 of the 10 weblogs, it works as normal.  In the other 7, I get completely blank white pages.

    -benjy

  • #4 / Jul 02, 2009 10:41am

    Sue Crocker

    26054 posts

    How much memory is allocated for PHP?

    EEWiki:// How to Determine Memory Limits

  • #5 / Jul 02, 2009 11:15am

    benjyrose

    16 posts

    20Mb.

  • #6 / Jul 02, 2009 11:24am

    Sue Crocker

    26054 posts

    Try raising it to 64M and see if that makes a difference.

    EEWiki:// HowTo Override Memory Limitations

    Turn on error reporting would probably be helpful as well.

  • #7 / Jul 02, 2009 11:31am

    benjyrose

    16 posts

    Changed to 64M via .htaccess -> no change
    Turned on error reporting with the code changes (it’s off via the host) -> and I still only see blank pages.  Should i contact my host?

  • #8 / Jul 02, 2009 11:37am

    Sue Crocker

    26054 posts

    How do the weblogs differ?

    What about extensions?

  • #9 / Jul 02, 2009 11:56am

    benjyrose

    16 posts

    I use them for different sections of the site ( gmvoices.com ). Some have custom field groups, some don’t. However, one of the weblogs that works has the same field group as one of the ones that doesn’t…so I’m not sure it’s that.

    Extensions are disabled.

  • #10 / Jul 02, 2009 12:05pm

    Sue Crocker

    26054 posts

    And you’re certain the switch to 64M stuck? Some hosts don’t allow you to chamge memory_limit via .htaccess.

  • #11 / Jul 02, 2009 12:09pm

    benjyrose

    16 posts

    Local Value is 64M, but Master Value is still 20M.  So….um…I’m not sure 😊  Should I contact the host?

  • #12 / Jul 02, 2009 12:14pm

    Sue Crocker

    26054 posts

    Also, if you aren’t on the most recent build, upgrading might clear up any issues of bad file uploading if they exist.

    Also see:

    http://expressionengine.com/knowledge_base/article/visiting_my_site_results_in_a_blank_page/

  • #13 / Jul 02, 2009 12:40pm

    benjyrose

    16 posts

    increased php memory through the host to 64M (now it shows up on both Local and Master values).  Still no change.

  • #14 / Jul 02, 2009 4:34pm

    Ingmar

    29245 posts

    Let’s make sure your errors actually. You followed the steps outlined in the wiki article Sue linked to above, correct? Take a simple template, make sure PHP is enabled, then introduce a deliberate PHP error. It doesn’t matter, something like

    <?php echo $foo ?>

    will do. Getting any errors?

  • #15 / Jul 02, 2009 4:56pm

    benjyrose

    16 posts

    OK…well, um, problem apparently solved.  It works now.
    I decided to try re-uploading the 1.6.7 files (after deleting the corresponding folders in my system folder), and now it works.  Hmmmmm.  I’m guessing there was a file upload error the first time.

    I appreciate the responses and the response time, Sue, and I apologize for taking up your time.

    -benjy

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases