Difference between revisions of "Theme debugging tools"

From JReviews Documentation
Jump to: navigation, search
 
Line 1: Line 1:
<div class="jrInfo">It is always recommended to create a new custom JReviews theme for your customizations so that they are not lost during updates. Once you identify the files you need to change [[JReviews_Code_Overrides#How_to_create_a_custom_theme|create a new custom theme]]
+
<div class="jrInfo">It is always recommended to create a new custom JReviews theme for your customizations so that they are not lost during updates. Once you identify the files you need to change, [[JReviews_Code_Overrides#How_to_create_a_custom_theme|create a new custom theme]] to override those files with your customized versions.</div>
  
 
In JReviews Configuration you will find debugging tools:
 
In JReviews Configuration you will find debugging tools:

Latest revision as of 12:52, 25 January 2014

It is always recommended to create a new custom JReviews theme for your customizations so that they are not lost during updates. Once you identify the files you need to change, create a new custom theme to override those files with your customized versions.

In JReviews Configuration you will find debugging tools:

Theme-debug-tools.png

Debug PHP & Queries

This option is very useful during development when something doesn't work because of php or database errors. Enabling it will display all php errors and database queries below all content on pages.

Debug Themes

This option is very useful if you don't know which file or function outputs specific elements of JReviews pages.

If you enable this option, it will show the theme output of each theme labeled with the theme filepath as well as the controller filename and function is used to process the output. Example:

Theme-debug-output.png

Debug IP

Enter your IP address to the Debug IP input when you enable Debug options so that other visitors of your site won't see debug info.