| Trouble-shooting a script that doesn't retuen HTML [message #182775] |
Mon, 09 September 2013 11:22  |
Derek Turner
Messages: 48
Registered: October 2010
Karma: 0
|
Member |
|
|
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 :)
|
|
|
|
| Re: Trouble-shooting a script that doesn't retuen HTML [message #182777 is a reply to message #182775] |
Mon, 09 September 2013 11:43  |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
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(at)attglobal(dot)net
==================
|
|
|
|
| Re: Trouble-shooting a script that doesn't retuen HTML [message #182778 is a reply to message #182775] |
Mon, 09 September 2013 11:54 |
Tim Streater
Messages: 328
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
In article <b95pc4Ffk4U1(at)mid(dot)individual(dot)net>,
Derek Turner <frderek(at)cesmail(dot)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
|
|
|
|
| Re: Trouble-shooting a script that doesn't retuen HTML [message #182779 is a reply to message #182775] |
Mon, 09 September 2013 12:19 |
Thomas 'PointedEars'
Messages: 701
Registered: October 2010
Karma: 0
|
Senior Member |
|
|
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).
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]