Actions

Difference between revisions of "How to debug your code"

From Joomla! Documentation

(Converted bold title to section headings. Added a section for the JFirePHP extension. Corrected grammar.)
m (JDEBUG: fixing images)
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==The Easy Way==
+
{{page|needs improvement|Updated Joomla! System-debug plugin features not listed here.}}
 +
 
 +
==The Easy Way 1 (echo)==
 
The simplest way to see what is going on inside your code is to temporarily add echo statements for variables to show their values on the screen. For example, say you want to know what the value of some variables are when $i is "5". You could use code like this:
 
The simplest way to see what is going on inside your code is to temporarily add echo statements for variables to show their values on the screen. For example, say you want to know what the value of some variables are when $i is "5". You could use code like this:
  
Line 10: Line 12:
  
 
This works for simple situations. However, if you are planning on doing a lot of Joomla! development, it is worth the effort to install and learn an integrated development environment (IDE) that includes a real PHP debugger.
 
This works for simple situations. However, if you are planning on doing a lot of Joomla! development, it is worth the effort to install and learn an integrated development environment (IDE) that includes a real PHP debugger.
 +
 +
==The Easy Way 2 (joomla message)==
 +
Your code won't always display simple echo statements. In that case you can try this alternative, still easy way:
 +
<source lang="PHP">JFactory::getApplication()->enqueueMessage('Some debug string(s)');</source>
 +
You can choose different [[Display_error_messages_and_notices|message types]] which corresponds to grouping with different styles (colors mainly).
 +
 
==Using an IDE==
 
==Using an IDE==
Many Joomla! developers use the Eclipse IDE. This is free and includes a debugger. Instructions for installing it are available at [[Setting_up_your_workstation_for_Joomla!_development]].
+
Check this 3 minutes video that shows [http://www.youtube.com/watch?v=sP4dHAuq2kc&feature=youtu.be how you can debug your code with a Browser and an IDE]
 +
 
 +
{{#ev:youtube|sP4dHAuq2kc}}
 +
 
 +
Many Joomla! developers use the Eclipse IDE. This is free and includes a debugger. Instructions for installing it are available at [[Setting up your workstation for Joomla! development]].
 +
 
 
==Using the PHP Expert editor==
 
==Using the PHP Expert editor==
 
Another option is the PHP Expert editor with an installed extension for debugging. Add the following lines to the php.ini file:
 
Another option is the PHP Expert editor with an installed extension for debugging. Add the following lines to the php.ini file:
Line 28: Line 41:
 
To check whether the Website is in the debug mode, test the JDEBUG variable:  
 
To check whether the Website is in the debug mode, test the JDEBUG variable:  
 
<source lang="PHP">
 
<source lang="PHP">
if(JDEBUG){
+
if(JDEBUG)
//whatever debugging code you want to run
+
{
 +
    //whatever debugging code you want to run
 
}
 
}
 
</source>
 
</source>
 +
 +
The debug mode can be enabled from the Joomla! Global Configuration under the System tab.  Once enabled the output of the debug plugin will be displayed at the bottom of each page.
 +
 +
[[File:Jdebug-module.jpg|The JDebug Plugin output]]
 +
 +
This plugin provides important information that can assist in debugging and improving the performance of your component.
 +
 +
===Profile Information===
 +
 +
The Profile Information tab from the debug plugin provides information about the time and memory taken to render the page based on each of the application events.  This can help to identify areas outside of network speed that are contributing to long page load times high server memory usage.
 +
 +
[[File:Jdebug-profile.jpg|JDEBUG Profile]]
 +
 +
===Database Queries===
 +
 +
One of the most useful tabs is the Database Queries tab.  This will provide a log of all queries that have been executed while loading the page and identify both the time taken to execute the query and whether duplicate queries have occurred.  This is particularly useful when debugging performance problems on larger components as duplicate queries are often a contributing factor.
 +
 +
[[File:Jdebug-query.jpg]]
 +
 
==JFirePHP==
 
==JFirePHP==
 
Use the Joomla [http://extensions.joomla.org/extensions/miscellaneous/development/11343 JFirePHP extension].
 
Use the Joomla [http://extensions.joomla.org/extensions/miscellaneous/development/11343 JFirePHP extension].
  
 
[[Category:Development]]
 
[[Category:Development]]
 +
[[Category:Video]]

Latest revision as of 05:04, 6 July 2014

Copyedit.png
This Article Needs Your Help

This article is tagged because it NEEDS IMPROVEMENT. You can help the Joomla! Documentation Wiki by contributing to it.
More pages that need help similar to this one are here. NOTE-If you feel the need is satistified, please remove this notice.

Reason: Updated Joomla! System-debug plugin features not listed here.


Contents

The Easy Way 1 (echo)

The simplest way to see what is going on inside your code is to temporarily add echo statements for variables to show their values on the screen. For example, say you want to know what the value of some variables are when $i is "5". You could use code like this:

for ( $i = 0; $i < 10; $i++ ) {
        if ( $i == 5 ) {
                echo '$i=' . $i; 
                // other echo statements 
        }
}

This works for simple situations. However, if you are planning on doing a lot of Joomla! development, it is worth the effort to install and learn an integrated development environment (IDE) that includes a real PHP debugger.

The Easy Way 2 (joomla message)

Your code won't always display simple echo statements. In that case you can try this alternative, still easy way:

JFactory::getApplication()->enqueueMessage('Some debug string(s)');

You can choose different message types which corresponds to grouping with different styles (colors mainly).

Using an IDE

Check this 3 minutes video that shows how you can debug your code with a Browser and an IDE

Many Joomla! developers use the Eclipse IDE. This is free and includes a debugger. Instructions for installing it are available at Setting up your workstation for Joomla! development.

Using the PHP Expert editor

Another option is the PHP Expert editor with an installed extension for debugging. Add the following lines to the php.ini file:

extension=php_dbg.dll
[Debugger]
debugger.enabled=on
debugger.profiler_enabled=off

It is best to set profiler_enable to "off". Then you need to set options in the Run/Options menu to use HTTP-server and the directory in which your script is located.

If all options are correct, you may run your script in debug mode by clicking on the Debug button (F8)

J!Dump

An often handy extension that can be found in the JED is the J!Dump extension that will allow you to dump variable, stack traces, and system information into a popup window at run time. This extension works like the PHP command `var_dump` but formats the output in a much more readable fashion.

JDEBUG

To check whether the Website is in the debug mode, test the JDEBUG variable:

if(JDEBUG)
{
    //whatever debugging code you want to run
}

The debug mode can be enabled from the Joomla! Global Configuration under the System tab. Once enabled the output of the debug plugin will be displayed at the bottom of each page.

The JDebug Plugin output

This plugin provides important information that can assist in debugging and improving the performance of your component.

Profile Information

The Profile Information tab from the debug plugin provides information about the time and memory taken to render the page based on each of the application events. This can help to identify areas outside of network speed that are contributing to long page load times high server memory usage.

JDEBUG Profile

Database Queries

One of the most useful tabs is the Database Queries tab. This will provide a log of all queries that have been executed while loading the page and identify both the time taken to execute the query and whether duplicate queries have occurred. This is particularly useful when debugging performance problems on larger components as duplicate queries are often a contributing factor.

Jdebug-query.jpg

JFirePHP

Use the Joomla JFirePHP extension.