Re: Is There a Stack Trace for Errors?

From: Date: Wed, 31 Mar 2004 15:16:07 +0000
Subject: Re: Is There a Stack Trace for Errors?
References: 1  Groups: php.general 
Request: Send a blank email to php-general+get-181948@lists.php.net to get a copy of this message
Maybe you would like to check out debug_bracktrace(); Hawkes, Richard wrote:
Hi Gang, I'm now writing the dreaded support document for the code, and I need to enhance my PHP to show error numbers so we can diagnose where it failed. All fine so far, but I've found a couple of functions that can be called from various other functions, so it's difficult to track where it came from. So... Is there a 'printStackTrace()' type function in PHP like there is in Java? Hope that's clear! Thanks Richard -----Original Message----- From: Aaron Wolski [mailto:aaronjw@martekbiz.com] Sent: 31 March 2004 15:16 To: 'Michael Egan'; 'John W. Holmes'; 'Will'; php-general@lists.php.net Subject: RE: [PHP] Hinding URL{ot}[Scanned]
On seeing that the only way of doing this was to use frames I decided
that
the costs of doing this probably outweighed what is in effect a purely cosmetic issue.
Never ever underestimate the "cosmetic" factor when you are talking about Usability and search engines. For example, if you are developing an ecommerce site - you have to think about your users/customers. In my testing and research, I have found that a large percentage of users will not bookmark URLS that look like: http://www.domain.com?id=1232&subcat=32&prodId=165412 They will, however, be more apt to bookmark URLS that look like: http://www.domain.com/shirts/white/flanel_button_down/ Why are users more apt to bookmark the latter? They make sense to the user. If you want people to come back to your site, bookmark your pages, and forward pages along to their friends... you gotta think like they do. You have to use URLs that make sense to THEM - not you. Search engine marketing is another factor to usable URLs. Just my thoughts. Aaron


« previous php.general (#181948) next »