How are templates executed? - Revision history

Mvangeest: Added category

2011-11-27T15:58:30Z

Added category

Mvangeest: Removed category

2011-01-16T00:02:08Z

Removed category

Chris Davenport: Reverted edits by GeraldineKelley (Talk) to last version by Batch1211

2011-01-13T23:32:53Z

Reverted edits by GeraldineKelley (Talk) to last version by Batch1211

GeraldineKelley at 18:55, 13 January 2011

2011-01-13T18:55:17Z

Batch1211 at 20:55, 29 September 2010

2010-09-29T20:55:07Z

Chris Davenport: Module execution was not in the right place.

2008-08-29T21:16:13Z

Module execution was not in the right place.

Chris Davenport: 1 revision(s)

2008-01-14T23:27:30Z

1 revision(s)

Chris Davenport at 22:51, 14 January 2008

2008-01-14T22:51:38Z

New page

=== How are templates executed? ===

Templates are executed in a 2-phase process that makes full use of the PHP parser to provide considerable flexibility and performance to the template designer. Templates are executed in the context of the document object so that the $this object is always the instantiation of the JDocument class.

Before template execution begins, the component and modules will have been executed and their output buffered for later use.

Template execution then proceeds as follows:-
* template parameters (if any) are loaded
* template language (if any) is loaded
* if legacy mode is on then the configuration variables are copied as globals
* the template file (index.php) is loaded and executed (by PHP). The output is buffered. This is phase 1 of the 2-phase process. Everything between <?php and ?> tags is executed as PHP code. Everything outside of these tags is output but otherwise ignored. As the output is being buffered, nothing is sent to the client web browser at this stage.
* a favicon.ico file is looked for, first in the Joomla! root directory, then in the template root directory. The latter will override the former if found.
* the output that was buffered in phase 1 is now parsed for <jdoc:include> elements. For each jdoc element found, the appropriate renderer class is loaded and its render method is called. The output from the render method replaces the <jdoc:include> element itself in the output buffer.
* Certain template-specific HTTP headers are added to the list of headers to be output.
* Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.
[[Category:Templates]]

@@ Line 15: / Line 15: @@
 [[Category:Templates]]
 [[Category:Template Development]]
-[[Category:Tutorials]]
+[[Category:Explanations]]

← Older revision		Revision as of 23:32, 13 January 2011
Line 13:		Line 13:
	* Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.		* Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.
	<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>[[Category:Template Development]][[Category:Tutorials]]		<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>[[Category:Template Development]][[Category:Tutorials]]
−	*[http://www.superiorpapers.com/ essay writing]

← Older revision		Revision as of 18:55, 13 January 2011
Line 13:		Line 13:
	* Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.		* Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.
	<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>[[Category:Template Development]][[Category:Tutorials]]		<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>[[Category:Template Development]][[Category:Tutorials]]
		+	*[http://www.superiorpapers.com/ essay writing]

@@ Line 12: / Line 12: @@
 * Certain template-specific HTTP headers are added to the list of headers to be output.
 * Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.
-<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>
+<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>[[Category:Template Development]][[Category:Tutorials]]

@@ Line 1: / Line 1: @@
 Templates are executed in a 2-phase process that makes full use of the PHP parser to provide considerable flexibility and performance to the template designer.  Templates are executed in the context of the document object so that the $this object is always the instantiation of the JDocument class.
-Before template execution begins, the component and modules will have been executed and their output buffered for later use.
+Before template execution begins, the component will have been executed and its output buffered for later use.
 Template execution then proceeds as follows:-
-* template parameters (if any) are loaded
+* template parameters (if any) are loaded.
-* template language (if any) is loaded
+* template language (if any) is loaded.
-* if legacy mode is on then the configuration variables are copied as globals
+* if legacy mode is on then the configuration variables are copied as globals.
 * the template file (index.php) is loaded and executed (by PHP).  The output is buffered.  This is phase 1 of the 2-phase process.  Everything between <?php and ?> tags is executed as PHP code.  Everything outside of these tags is output but otherwise ignored.  As the output is being buffered, nothing is sent to the client web browser at this stage.
 * a favicon.ico file is looked for, first in the Joomla! root directory, then in the template root directory.  The latter will override the former if found.
-* the output that was buffered in phase 1 is now parsed for <jdoc:include> elements.  For each jdoc element found, the appropriate renderer class is loaded and its render method is called.  The output from the render method replaces the <jdoc:include> element itself in the output buffer.
+* the output that was buffered in phase 1 is now parsed for <jdoc:include> elements.  This is phase 2 of the process.  For each jdoc element found, the appropriate renderer class is loaded and its render method is called.  The output from the render method replaces the <jdoc:include> element itself in the output buffer.  In the case of module renderer classes this triggers the execution of the modules and the buffering of their output.
 * Certain template-specific HTTP headers are added to the list of headers to be output.
 * Control is then passed back to the JApplication object which will handle the rest of the process of getting the now rendered web page back to the client web browser.
-[[Category:Templates]]
+<noinclude>[[Category:Templates]][[Category:Development]]</noinclude>