Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #10736 > unrolled thread

Trouble-shooting a script that doesn't retuen HTML

Back to article view | Back to comp.lang.php

Contents

  Trouble-shooting a script that doesn't retuen HTML Derek Turner <frderek@cesmail.net> - 2013-09-09 11:22 +0000
    Re: Trouble-shooting a script that doesn't retuen HTML Jerry Stuckle <jstucklex@attglobal.net> - 2013-09-09 07:43 -0400
    Re: Trouble-shooting a script that doesn't retuen HTML Tim Streater <timstreater@greenbee.net> - 2013-09-09 12:54 +0100
    Re: Trouble-shooting a script that doesn't retuen HTML Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-09-09 14:19 +0200

#10736 — Trouble-shooting a script that doesn't retuen HTML

Hi folks,

I have a script that has just 'stopped working', nothing has been changed 
in the script at all.

The script queries a database and outputs (or should do) an excel 
spreadsheet. I was working fine a fortnight ago before I went on holiday. 
Now I just get a blank browser page and no spreadsheet when I call it.

Before I tackle the hosting company, is there an obvious way of getting 
all and every error and warnings output?

Sorry if this is a bit of a n00b question but I've always had error 
messages when something was wrong: never this silence :)

[toc] | [next] | [standalone]

#10738

On 9/9/2013 7:22 AM, Derek Turner wrote:
> Hi folks,
>
> I have a script that has just 'stopped working', nothing has been changed
> in the script at all.
>
> The script queries a database and outputs (or should do) an excel
> spreadsheet. I was working fine a fortnight ago before I went on holiday.
> Now I just get a blank browser page and no spreadsheet when I call it.
>
> Before I tackle the hosting company, is there an obvious way of getting
> all and every error and warnings output?
>
> Sorry if this is a bit of a n00b question but I've always had error
> messages when something was wrong: never this silence :)
>

First of all, does it work on your development system?  Or do you get 
failures there, also?

Your development system's php.ini should have:

display_errors = on
error_reporting = E_ALL

If it does not fail on your development system, what is different 
between it and your production system?

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#10739

In article <b95pc4Ffk4U1@mid.individual.net>,
 Derek Turner <frderek@cesmail.net> wrote:

> I have a script that has just 'stopped working', nothing has been changed 
> in the script at all.
> 
> The script queries a database and outputs (or should do) an excel 
> spreadsheet. I was working fine a fortnight ago before I went on holiday. 
> Now I just get a blank browser page and no spreadsheet when I call it.
> 
> Before I tackle the hosting company, is there an obvious way of getting 
> all and every error and warnings output?

You could ask your browser to show you the source of the "blank page" to 
see if anything at all has been generated. You could also put some 
debugging echo statements in your script and see which of those get 
executed (if any).

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

[toc] | [prev] | [next] | [standalone]

#10740

Derek Turner wrote:

> I have a script that has just 'stopped working', nothing has been changed
> in the script at all.
> 
> The script queries a database and outputs (or should do) an excel
> spreadsheet. I was working fine a fortnight ago before I went on holiday.
> Now I just get a blank browser page and no spreadsheet when I call it.
> 
> Before I tackle the hosting company, is there an obvious way of getting
> all and every error and warnings output?

Yes.

<http://lmgtfy.com/?q=PHP+errors>
<http://catb.org/~esr/faqs/smart-questions.html>
 
> Sorry if this is a bit of a n00b question but I've always had error
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
See above.

> messages when something was wrong: never this silence :)

It may be that your hoster has made the wise decision in the meantime not to 
display PHP error messages and warnings by default as that is considered a 
security risk.  If the culprit is not the client-side, those messages should 
have been written to the server log instead.  With good hosters you get 
access to the server logs for your site, either through special agreement or 
(more common) Web interface (Plesk et al.)


PointedEars
-- 
When all you know is jQuery, every problem looks $(olvable).

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.php

csiph-web