If you set your error reporting to E_ALL | E_STRICT in your php.ini,
and display_errors to on, all your syntax errors etc should show up in
shindig's output.
In the case of the social requests, to be able to see them, firebug is
your friend as Ropu suggested, imo you just can't develop a web
application without it :) Also those errors should show up in your
apache log's.. but i find for me it just works quicker to check out
the results in firebug.
For debugging a simple syslog(5, '... my message ...'); works wonders
(messages then turn up /var/log/messages on a *nix machine), or echo's
and print_r's combined with firebug works well too (but with the
downside it'll break the json/etc syntax so for the situations where
you just want some info syslog is better suited).
For 'real debugging', get a copy of Zend Studio for eclipse, install
the zend debug server to your php installation, and you can do full,
real debugging in eclipse... i wouldn't call it required, but
sometimes visual tracing and inspecting can be quite enlightening :)
-- Chris
On Jul 14, 2008, at 3:11 PM, ajay singh wrote:
Thanks Ropu
I was also using the Apache log.
Fire bug is a good option . i'll try that.
Is Shindig also maintain its log anywhere?
Thanks
Ajay
Ropu <[EMAIL PROTECTED]> wrote: Hi, my best suggestion is to write
to the Apache (or web server) logs.
just #tail -f "WS_error_logs"
also i would suggest to work with Firebug to debug the HTTP traffic...
ropu
On Mon, Jul 14, 2008 at 7:59 AM, ajay singh
wrote:
Hi
I am connecting shindig to my SNS backend data.
Now If any error occurs in my service files
(People,Activities,AppData),
then how to know this error?
Suppose i have done any syntax error in writing query in my
dbfetcher(
something like PartuzaDbFetcher) then how can i debug the error.
Thanks
Ajay
--
.-. --- .--. ..-
R o p u
