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

Groups > comp.lang.php > #12571

Re: json testing suggestions

Show all headers | View raw

BobMCT wrote:

> Pls help jolt my old memory with this?  Trying to work on some old php
> progs that output using the json_encode function on a NEW install of
> Ubuntu 13.10.  I'm NOT getting any output.  If I dump the array I'm
> using as the source for the json_encode it looks just fine.  However,
> firebug is showing non response.

*Where* does it show “non response” (sic!)?  *How?*

If in the Network tab, there are two possibilities:

A) You are not making an HTTP request with the correct URI.
B) You are not sending a non-empty HTTP response.

If A), you have to check the client-side script and Firebug's error console.  
If B), you have to check the server-side script.  Make sure that there are 
no syntax errors or other PHP errors.  The first lines of your PHP program 
should be:

<?php
  error_reporting(E_ALL | E_STRICT);
  ini_set('display_errors', true);

ini_set() is necessary (except on a development system where the value 
should be the default) unless you want/have to check the PHP log files 
instead.

> I checked with phpinfo and it shows that I do have json installed and
> active and when I try to run the target program I also receive just
> errors.

*Which* errors?
 
> So my question is:  can someone recommend some ways to properly debug
> the ajax/json process?

In addition to the above, there is the FirePHP add-on.

> I seem to remember firebug once having some features available to examine
> the response from a js call but I don't see it now.

They still are in the Network tab and the Console.  <http://getfirebug.com/>

> BTW - having just recently upgraded from 10.04 to 13.10

Of what?

> I've run into other issues with compatibiity.

Useless information again.

<http://www.catb.org/~esr/faqs/smart-questions.html#beprecise>

And please get a real name.


PointedEars
-- 
Danny Goodman's books are out of date and teach practices that are
positively harmful for cross-browser scripting.
  -- Richard Cornford, cljs, <cife6q$253$1$8300dec7@news.demon.co.uk> (2004)

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

json testing suggestions BobMCT <r.mariotti@fdcx.net> - 2014-01-07 20:33 -0500
  Re: json testing suggestions Richard Damon <Richard@Damon-Family.org> - 2014-01-07 21:48 -0500
    Re: json testing suggestions BobMCT <r.mariotti@fdcx.net> - 2014-01-09 22:43 -0500
  Re: json testing suggestions John Smith <johnsmithjsm@live.com> - 2014-01-07 23:23 -0500
  Re: json testing suggestions John Smith <johnsmithjsm@live.com> - 2014-01-07 23:24 -0500
  Re: json testing suggestions jnorth.au@example.com - 2014-01-08 17:39 +1100
    Re: json testing suggestions "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> - 2014-01-08 12:32 +0000
      Re: json testing suggestions BobMCT <r.mariotti@fdcx.net> - 2014-01-08 08:18 -0500
    Re: json testing suggestions bill <william@TechServSys.com> - 2014-01-09 07:41 -0500
      Re: json testing suggestions John Smith <johnsmithjsm@live.com> - 2014-01-09 16:13 +0000
  Re: json testing suggestions Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-01-08 15:40 +0100
  Re: json testing suggestions Gregor Kofler <usenet@gregorkofler.com> - 2014-01-09 09:38 +0100
    Re: json testing suggestions Christoph Michael Becker <cmbecker69@arcor.de> - 2014-01-09 13:38 +0100

csiph-web