<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Usage</title><link>https://sourceforge.net/p/phptrace/wiki/Usage/</link><description>Recent changes to Usage</description><atom:link href="https://sourceforge.net/p/phptrace/wiki/Usage/feed" rel="self"/><language>en</language><lastBuildDate>Mon, 23 Jul 2012 14:55:20 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/phptrace/wiki/Usage/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Usage modified by Tamil Amuthan</title><link>https://sourceforge.net/p/phptrace/wiki/Usage/</link><description>&lt;pre&gt;--- v2
+++ v3
@@ -1,46 +1,3 @@
-Introduction
-
-It displays the trace list of the error. It is based on debug_backtrace. It is very helpful in PHP projects. Jquey is used to display the error list in expandable and collapsable block.
-Details
-
-This is a simple error tracker for PHP, which displays a trace list from the start page to the page where the error occured. It can show the fatal error details also.
-
-It displays the following:
-
-1) File name, path and line number of each page
-
-2) The list of variables(data will be showed in a popup by clicking it) when the error occured.
-
-
-
-
-
-It can be used as two ways
-
-a) display error at run time
-
-b) display message manually (alternative to print_r)
-
-It can also be used alternative to print_r.
-
-
-
-It will work in 4 modes
-
-1) show message and die
-
-2) show message and continue
-
-3) show only when $REQUEST has a key "trace" - useful for debugging live server
-
-4) show only in developer IP address - useful for debugging live server
-
-Installation
-
-upload the debug.php into the project folder
-
-Usage
-
 1) include the file in the main page(usually index.php)
 
 Ex: include_once("debug.php") - if the main page is in project root directory
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tamil Amuthan</dc:creator><pubDate>Mon, 23 Jul 2012 14:55:20 -0000</pubDate><guid>https://sourceforge.netc44ea258a8ac2472f6cc98468583fadd3a1ee3e1</guid></item><item><title>WikiPage Usage modified by Tamil Amuthan</title><link>https://sourceforge.net/p/phptrace/wiki/Usage/</link><description>&lt;pre&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tamil Amuthan</dc:creator><pubDate>Mon, 23 Jul 2012 14:54:32 -0000</pubDate><guid>https://sourceforge.netc523fbe63944b493a5dcbd7e43cd63c79827dcd4</guid></item><item><title>WikiPage add modified by Tamil Amuthan</title><link>https://sourceforge.net/p/phptrace/wiki/add/</link><description>Introduction

It displays the trace list of the error. It is based on debug_backtrace. It is very helpful in PHP projects. Jquey is used to display the error list in expandable and collapsable block.
Details

This is a simple error tracker for PHP, which displays a trace list from the start page to the page where the error occured. It can show the fatal error details also.

It displays the following:

1) File name, path and line number of each page

2) The list of variables(data will be showed in a popup by clicking it) when the error occured.





It can be used as two ways

a) display error at run time

b) display message manually (alternative to print_r)

It can also be used alternative to print_r.



It will work in 4 modes

1) show message and die

2) show message and continue

3) show only when $REQUEST has a key "trace" - useful for debugging live server

4) show only in developer IP address - useful for debugging live server

Installation

upload the debug.php into the project folder

Usage

1) include the file in the main page(usually index.php)

Ex: include_once("debug.php") - if the main page is in project root directory

That's all for Run time error display

2) call function trace with following parameters

Parmeter 1) message

Parameter 2) number of time the display has to be ignored - it will be useful when using it in loop. if you want to display error at 6th loop, then use trace($message,6). It will show the message when the loop enters 6th cycle.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tamil Amuthan</dc:creator><pubDate>Mon, 23 Jul 2012 14:51:02 -0000</pubDate><guid>https://sourceforge.net9e5001ce07370f7cd419b95458a1b57074f5c32d</guid></item></channel></rss>