[Chugalug] LAMP problem

Ed King chevyiinova at bellsouth.net
Thu Mar 14 20:59:44 UTC 2013

hehe, I sent piratically identical advice to Garrett off-list.    I guess I should have sent on-list, but I'm always afraid my suggestions are bourgeois and I will be laughed at for my simplicity ;)

--- On Thu, 3/14/13, Mike Robinson <miker at sundialservices.com> wrote:

From: Mike Robinson <miker at sundialservices.com>
Subject: Re: [Chugalug] LAMP problem
To: chugalug at chugalug.org
Date: Thursday, March 14, 2013, 4:20 PM

When trying to diagnose a problem like this one, look at two places:  server logs (or wherever debugging-messages are put out to), and a browser's HTML debugger .. such as the Firebug plugin for Firefox, the Developer screens in Safari (you have to flip an option in preferences to turn that on), and so on.
Firebug will =show= you what HTTP packet is being sent to the host, and what HTTP packet is returned.  No more guessing about what was actually sent or received.
When debugging, make the code initially "chatty."  Echo stuff out as you go along the success-route, not just in case of failure.  Comment those out later.

---------Mike RobinsonTechnical DirectorSundial Services International, LLChttp://www.sundialservices.commiker@sundialservices.com(615) 268-3829http://www.linkedin.com/pub/mike-robinson/51/532/5a

-----Inline Attachment Follows-----

Chugalug mailing list
Chugalug at chugalug.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://chugalug.org/pipermail/chugalug/attachments/20130314/6cab8a0c/attachment-0001.html>

More information about the Chugalug mailing list