[FX.php List] PHP Server Error
Gjermund Gusland Thorsen
ggt667 at gmail.com
Sat Dec 1 14:54:10 MST 2007
Always make a web log table, it helps you keep track of stuff and who did what.
ggt
On Dec 1, 2007 10:20 PM, Jonathan Schwartz <jschwartz at exit445.com> wrote:
>
>
> Dale,
>
>
> Thanks.
>
>
> Perhaps I'm different...and this might tie in with one of my recent post
> about "whipping up a solution" for relatively short term projects...I find
> myself constantly adding features and code to live solutions. I need the
> error reporting to tell me if things work.
>
>
> Now, I also work with a bit of caution. I monitor a FMP log that tells if
> anyone is in process on the site. If the coast is clear, I will save the
> existing page as back up, make the edit and then test it. If it doesn't
> worked as planned, and if I feel that I don't have time to resolve it
> immediately, I will revert to the saved BAK file and have time to rethink
> the change.
>
>
> Sort of like playing on the train tracks as a kid. I don't smoke. I don't
> drink. Have to get my thrills somehow. ;-)
>
>
> Jonathan
>
>
>
>
>
>
>
>
>
>
> At 3:02 PM -0600 12/1/07, Dale Bengston wrote:
> Correct. The first error is from FX. The two WARNING errors are from PHP,
> because the PHP code is expecting a data array to walk, and it didn't get
> one due to the failed connection.
>
>
> Personally, I make sure all errors are gone before I roll out a solution. I
> don't think it's right to just shut off error reporting and look the other
> way. Maybe I'm just obsessed or something!
>
>
> Dale
>
>
> On Dec 1, 2007, at 1:19 PM, Jonathan Schwartz wrote:
>
>
>
> So one could/should trap for (1) PHP errors and (2) FMP errors, but not
> fx.php errors? What about the errors below?
>
>
> For "fun", I just mad my server disappear by changing the IP address in
> server_data. I got the familiar error:
>
>
> FX: cURL could not retrieve Post data in RetrieveFM7Data(). A bad URL is the
> most likely reason.FX: cURL could not retrieve Post data in
> RetrieveFM7Data(). A bad URL is the most likely reason.
>
> Warning: Cannot use a scalar value as an array in
> /Library/WebServer/Documents/exit445/mvll/totals.php on line 70
>
> Warning: Invalid argument supplied for foreach() in
> /Library/WebServer/Documents/exit445/mvll/totals.php on line 70
>
>
>
>
> So...this is FX complaining first and then PHP native?
>
>
> I know that I should inhibit error reporting for production systems, but my
> project never really seem to reach that "perfect state". ;-)
>
>
> If I wanted to do so, I have to set both fx and PHP to not print errors to
> the screen?
>
>
> Jonathan
>
>
>
>
> Gusland Thorsen wrote:
>
> Aha, those errors are not usually seen by a regular user of FX.php as
> long as we made FX.php work correctly.
>
> ggt
>
> On Dec 1, 2007 7:08 PM, Jonathan Schwartz <jschwartz at exit445.com> wrote:
> > Thank ggt.
> >
> > I guess I can interpret that one as "no connection to server".
> >
> > I guess what I wanted to know is how to get the existing error
> > reporting mechanism to report OTHER errors. All i get is the one
> > mentioned below. Or...am I thinking about pure PHP errors which
> > occur outside of fx?
> >
> > How can generate an error inside of fx that would be reported, as a test?
> >
> > Thx.
> >
> > Jonahan
> >
> >
> > At 7:02 PM +0100 12/1/07, Gjermund Gusland Thorsen wrote:
> > >Odd errors are usually due to any least square of not being able to
> > >connect to the server
> > >
> > >Username/Password
> > >Wrong IP address/port for server
> > >curl on/off depending on release/system
> > >
> > >ggt
> > >
> > >On Dec 1, 2007 6:00 PM, Jonathan Schwartz <jschwartz at exit445.com> wrote:
> > >>
> > >>
> > >> Hi Folks,
> > >>
> > >>
> > >> I finally turned on the option in fx.php to receive emails if/when
> errors
> > >> occur in fx.
> > >>
> > >>
> > >> It seems that I only get a single message that isn't very
> informative:
> > >>
> > >>
> > >> The following error just occured:
> > >>
> > >>
> > >> Message: FX: ExecuteQuery XML error: no element found at line 1
> > >>
> > >>
> > >> How can I expand this? I know this one occured during development.
> > >>
> > >>
> > >> Thanks
> > >>
> > >>
> > >> Jonathan --
> > >>
> > >>
> > >> Jonathan Schwartz
> > >> Exit 445 Group
> > >> jonathan at exit445.com
> > >> http://www.exit445.com
> > >> 415-381-1852
> > >> _______________________________________________
> > >> FX.php_List mailing list
> > >> FX.php_List at mail.iviking.org
> > >> http://www.iviking.org/mailman/listinfo/fx.php_list
> > >>
> > >>
> > >_______________________________________________
> > >FX.php_List mailing list
> > >FX.php_List at mail.iviking.org
> > >http://www.iviking.org/mailman/listinfo/fx.php_list
> >
> >
> > --
> >
> > Jonathan Schwartz
> > Exit 445 Group
> > jonathan at exit445.com
> > http://www.exit445.com
> > 415-381-1852
> > _______________________________________________
> > FX.php_List mailing list
> > FX.php_List at mail.iviking.org
> > http://www.iviking.org/mailman/listinfo/fx.php_list
> >
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
>
>
>
> --
> Jonathan Schwartz
> Exit 445 Group
> jonathan at exit445.com
> http://www.exit445.com
> 415-381-1852
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
>
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
>
> --
>
>
> Jonathan Schwartz
> Exit 445 Group
> jonathan at exit445.com
> http://www.exit445.com
> 415-381-1852
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
More information about the FX.php_List
mailing list