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.

[RESOLVED] Blank screen with specific entry

April 25, 2011 6:06pm

Subscribe [3]
  • #1 / Apr 25, 2011 6:06pm

    Versa Studio

    572 posts

    I have a weird situation where I’m getting a blank screen for a particular entry.

    From this page:
    http://percthinkwork.org/education/training-list/

    Click “History of Employment” and you see the entry, but if you click “Vocational Rehabilitation (VR) Introduction”, a blank screen appears. I’ve gone over the code carefully, but cannot see what is happening.

    I’ve tried making the code more explicit, i.e, calling segment_3, but no luck.

    {exp:channel:entries channel="courses" dynamic="off" limit="1" url_title="{segment_3}" 
    disable="member_data|pagination" show_future_entries="yes"}

    Ideas?

    EE2.1.3
    Build:  20101220

    Thanks,

    Ben

  • #2 / Apr 25, 2011 7:03pm

    narration

    773 posts

    Ben, I see the same you do on that site, as well as an apparent slight delay for the problem entry, and then the (Chrome) browser says the error is an empty response—connection closed without data sent from the server.

    This naturally makes one think about PHP memory limits. You might check what you have set, vs. what EE tells you is used for a working page in the debug you can turn on from the CP, and then observe while using the site on the same browser, still logged in as adminstrator.

    You equally might want to set $debug=1 temporarily in index.php, so as to see any PHP errors. Be sure to read what it says in the comments there about security etc..

    Hope this leads you to a trail.

    Regards,
    Clive

  • #3 / Apr 25, 2011 7:27pm

    Versa Studio

    572 posts

    Hi,

    PHP mem limit is at 64, and I turned on debug in CP as well as in index.php, but am still getting a blank page even when logged in.

    Thx,

    Ben

  • #4 / Apr 25, 2011 7:52pm

    narration

    773 posts

    Ben, 64M should be more than enough unless you are doing something unusual on that page.

    —What is the memory usage shown for a working page, when you have CP template debugging turned on? 

    There should be a figure at the very bottom of the result, and mine is showing 8.1 MB for a medium-complex page with a few add-ons. It can reasonably go quite a bit higher, though, for certain add-ons.

    —are you able to get any memory use reading this way for the failing page?

    —If these are just different entries on the same template, as they appear, you can try replicating the bad entry’s content on a new entry, preferably one element at a time, to see if there’s an issue about the data.

    —as you may understand, blank page with apparent PHP shutdown and no clues is a bit of a blank slate also as far as possibilities. A thing that occurs to me to try next, especially if that bad entry can be successfully run as as replicated but not itself, would be to repair the database. No reason it should be bad, but this does sometimes occur due to upsets like power fails at the server.

    You can do this repair from Tools>Data>SQL Manager, then choosing Manage Database Tables. Go to the bottom, click Select All and see that it does, then choose Repair Selected Tables, and Submit. Afterwards (doesn’t take long) do the same, but choose Optimize Selected Tables, and Submit. Then see if your problem entry works.

    —if none of the above work, and especially if the replicated entry also fails with a blank page, you might suspect a problem add-on, perhaps one that is out-of-date with an upgraded EE at your site.

    You can try Disable Extensions on the Extensions page as a quick check in this direction; this will not remove any Extension data so is safe. If your page is ok then, you have a clue and can start tracking down by process of elimination to see which extension has problems.

    You may find the process is tricky if your page won’t run at all without a given Extension. Plug-ins you can similarly test just by moving them to a save folder.

    Deinstalling Extensions or Modules usually removes all their data, which you definitely don’t want.  So past this point of troubleshooting, you will want to isolate any issues by version number of the add-on, and then do an upgrade without deinstalling.

    Make sense?

    Good fortune, then, Ben, and keep letting the forum know what you find.

    Regards,
    Clive

  • #5 / Apr 26, 2011 12:49am

    Versa Studio

    572 posts

    Thanks Clive. I went through the steps and it turns out a plugin was bombing and not giving any errors.

  • #6 / Apr 26, 2011 4:00am

    narration

    773 posts

    Glad to hear you got it, Ben. Enjoyed a tour through your website, also.

    Regards,
    Clive

  • #7 / Apr 26, 2011 4:42am

    John Henry Donovan

    12339 posts

    Thanks Clive.

    Glad you are up and running Ben. Feel free to start a new thread if you have any more questions

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

ExpressionEngine News!

#eecms, #events, #releases