DEPRECATION WARNING

This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

EXT: Fire Debug

Author:Kasper Skårhøj
Created:2002-11-01T00:32:00
Changed:2008-08-03T20:18:29
Author:Marketing Factory
Email:typo3@marketing-factory.de
Info 3:
Info 4:

img-1 img-2 EXT: Fire Debug

EXT: Fire Debug

Extension Key: fire_debug

Copyright 2008, Marketing Factory, <typo3@marketing-factory.de>

This document is published under the Open Content License

available from http://www.opencontent.org/opl.shtml

The content of this document is related to TYPO3

- a GNU/GPL CMS/Framework available from www.typo3.org

Table of Contents

EXT: My Extension 1

`Introduction 3 <#1.1.Introduction|outline>`_

What does it do? 3

Screenshots 3

`Users manual 4 <#1.2.Users%20manual|outline>`_

FAQ 4

`Administration 5 <#1.3.Administration|outline>`_

FAQ 5

`Configuration 6 <#1.4.Configuration|outline>`_

FAQ 6

Reference 6

`Tutorial 7 <#1.5.Tutorial|outline>`_

`Known problems 8 <#1.6.Known%20problems|outline>`_

`To-Do list 9 <#1.7.To-Do%20list|outline>`_

`ChangeLog 10 <#1.8.ChangeLog|outline>`_

Important guidelines 11

`Issues with Open Office documentation for TYPO3 12 <#2.1.Issues%20w ith%20Open%20Office%20documentation%20for%20TYPO3|outline>`_

Inserting images 12

Paragraph styles 12

Linking 13

Meta data and updates 13

Help by documentation.openoffice.org 13

Introduction

What does it do?

This extension prints debug commands into the Firebug Extension for Mozilla.

Users manual

Quickinstall:
  • Install the extension with the Extension Manager
  • Install Firebug for Firefox
  • Install FirePHP for Firefox (http://www.firephp.org/)
Installation

This section describes how to install the extension and set it up.

Go to the Extension Manager an import the extension fire_debug from TER. After importing it just click to install it.

Congratulations! The extension has been installed. Don't forget to set the config options for the extension to your specific needs.

Enable logging when BE User is logged in only? - this option when enabled will print the debug only when you are logged into the backend

Enable logging for an IP Range – this option allows you to specify a specific IP Range (I.e. 192.168.217.*) that will see the debug commands. This is useful when you cannot log into the backend but still want to keep your debug messages private.

The following part describes how to install the Firefox extensions. First, install Firebug ( http://getfirebug.com/ ). However, we suggest that you look for the most recent version on https://addons.mozilla.org , the homepage does not always have the latest version. Then you install the FirePHP Extension ( http://www.firephp.org/ ). Now you are ready to debug into the Firebug console.

Documentation

How to use: after you installed the Firefox Extensions correctly, you can use the debug() command.

Example:

debug($array,'array',__LINE__,__FILE__);

debug($string,'string',__LINE__,__FILE__);

debug($string,'string',__LINE__);

debug($string,'string');

debug($string);

This will print out a detailed view for the variable you choose to debug. There are no type restrictions for which variables you can debug. Arrays and objects work just as well as strings and integers.

When you debug an array or an object, you can click on the value- Property of the output in Firebug to browse its contents.

When you debug an object, it is printed out as a array with two subarrays. The first contains all available properties of the object, the second contains all available methods. Properties are also displayed as an array with four fields. The first three are length of the property, its type and its name. The last is the value, which you can again click if it is an object or another array.

Please see more at http://forge.typo3.org/projects/show/extension- fire_debug

3