Joomla! Documentation - Recent changes [en]

User:Caza2a

Caza2a — Wed, 23 May 2012 22:33:21 GMT

New user account

User:Wallacevbuiwwukfgzmwiliqosneclynajxzitkrdtmassoni

Wallacevbuiwwukfgzmwiliqosneclynajxzitkrdtmassoni — Wed, 23 May 2012 22:33:04 GMT

New user account

User:Faustodjwurdsqniivwncknhluqjvmzmzmjpigonlenglar

Faustodjwurdsqniivwncknhluqjvmzmzmjpigonlenglar — Wed, 23 May 2012 22:16:40 GMT

New user account

User:ShacklefordCarbone851

ShacklefordCarbone851 — Wed, 23 May 2012 22:07:41 GMT

New user account

User:Cicekgonder

Cicekgonder — Wed, 23 May 2012 21:37:09 GMT

New user account

User:MeaghanCardinale879

MeaghanCardinale879 — Wed, 23 May 2012 21:06:56 GMT

New user account

User:GreenwoodSelph15

GreenwoodSelph15 — Wed, 23 May 2012 20:59:54 GMT

New user account

User:Udg629oa

Udg629oa — Wed, 23 May 2012 20:39:49 GMT

New user account

User:Oimeljm

Oimeljm — Wed, 23 May 2012 20:27:21 GMT

New user account

User:GillumGuess830

GillumGuess830 — Wed, 23 May 2012 20:23:01 GMT

New user account

User:Melhand

Melhand — Wed, 23 May 2012 20:22:37 GMT

New user account

User talk:Janeyoung123

Chris Davenport — Wed, 23 May 2012 20:03:25 GMT

deleted "[[User talk:Janeyoung123]]" Spam

User:Aapti

Chris Davenport — Wed, 23 May 2012 19:59:44 GMT

blocked [[Aapti (Talk | contribs)]] with an expiry time of infinite (account creation disabled, e-mail blocked) Spamming links to external sites

User:Lpt6r8e799

Lpt6r8e799 — Wed, 23 May 2012 19:52:50 GMT

New user account

User:Car finance

Car finance — Wed, 23 May 2012 19:41:50 GMT

New user account

User:NolanaBloch475

NolanaBloch475 — Wed, 23 May 2012 19:39:11 GMT

New user account

User:NinoMoore613

NinoMoore613 — Wed, 23 May 2012 19:26:01 GMT

New user account

User:FulfordEichler254

FulfordEichler254 — Wed, 23 May 2012 19:25:31 GMT

New user account

User:Billb

Billb — Wed, 23 May 2012 19:13:02 GMT

New user account

User:LittleTownley991

LittleTownley991 — Wed, 23 May 2012 19:12:19 GMT

New user account

Component Development

Svanschu — Wed, 23 May 2012 18:56:21 GMT

Components:jform fields

Svanschu — Wed, 23 May 2012 18:53:03 GMT

← Older revision		Revision as of 18:53, 23 May 2012
Line 61:		Line 61:
	default="now"></field>		default="now"></field>
	</source>		</source>
		+
		+	[[Category:Development]]
		+	[[Category:Extensions]]
		+	[[Category:References]]
		+	[[Category:Component Development]]

User:Ud23v1r9oa

Ud23v1r9oa — Wed, 23 May 2012 18:49:20 GMT

New user account

User:Hassanqoxyselfteqfvvdwgxouoeuynovizazrenkpoteet

Hassanqoxyselfteqfvvdwgxouoeuynovizazrenkpoteet — Wed, 23 May 2012 18:48:31 GMT

New user account

User:DemaioOates505

DemaioOates505 — Wed, 23 May 2012 18:42:23 GMT

New user account

User:Soumyajit40cs

Soumyajit40cs — Wed, 23 May 2012 18:40:27 GMT

New user account

User:Amit.d.kadam1987

Amit.d.kadam1987 — Wed, 23 May 2012 18:33:59 GMT

New user account

User:DiandraG3umm188

DiandraG3umm188 — Wed, 23 May 2012 18:26:39 GMT

New user account

User:Vsb1o3v254

Vsb1o3v254 — Wed, 23 May 2012 18:02:01 GMT

New user account

User:EmileeHarbour601

EmileeHarbour601 — Wed, 23 May 2012 17:57:08 GMT

New user account

User:Xy1239oa

Xy1239oa — Wed, 23 May 2012 17:51:51 GMT

New user account

User:ElledgeMaddy743

ElledgeMaddy743 — Wed, 23 May 2012 17:20:56 GMT

New user account

User:LavinaToon152

LavinaToon152 — Wed, 23 May 2012 17:05:20 GMT

New user account

User:Wallysbmnhjlfrmjfrgbtjklivdmmggsnpuqldazbroce

Wallysbmnhjlfrmjfrgbtjklivdmmggsnpuqldazbroce — Wed, 23 May 2012 17:01:43 GMT

New user account

JController and its subclass usage overview

Mcormier — Wed, 23 May 2012 17:01:11 GMT

Master Controller:

← Older revision		Revision as of 17:01, 23 May 2012
(One intermediate revision not shown)
Line 56:		Line 56:
	* If a view is specified with a task (but not in the dot format), master controller loads the specified view and executes method specified by task. This case is used to display edit form, or to present one item of record to user. An example is index.php?option=com_content&view=article&layout=edit.		* If a view is specified with a task (but not in the dot format), master controller loads the specified view and executes method specified by task. This case is used to display edit form, or to present one item of record to user. An example is index.php?option=com_content&view=article&layout=edit.

-	When master controller creates view, it normally loads a model having the same name as the view and pushes model into the view. Then view's display method is called. Doing this, in view we can get data from model using function like $this->get("Items"). In this case, view will look for method getItems in model and execute it. Doing this, we can use one controller for display all information type in component. But many views still required. This reduces the controller class and, of course, reduces code produced by developer.	+	When the master controller a creates view, it normally loads a model having the same name as the view and pushes model into the view. Then the view's display method is called. Doing this, in view we can get data from model using function like $this->get("Items"). In this case, view will look for method getItems in model and execute it. Doing this, we can use one controller for display all information type in component. But many views still required. This reduces the controller class and, of course, reduces code produced by developer.

	=== Subcontrollers ===		=== Subcontrollers ===
Line 67:		Line 67:
	=== Contributors ===		=== Contributors ===
	*[[User:Mrs.siam\|Prasit Gebsaap]]		*[[User:Mrs.siam\|Prasit Gebsaap]]
		+	*[[User:mcormier\|Matthieu Cormier]]

	[[Category:Development]]		[[Category:Development]]

User:Camelia

Camelia — Wed, 23 May 2012 16:52:29 GMT

New user account

JController and its subclass usage overview

Mcormier — Wed, 23 May 2012 16:52:18 GMT

Master Controller:

← Older revision		Revision as of 16:52, 23 May 2012
(2 intermediate revisions not shown)
Line 50:		Line 50:


-	For example, to edit an article the task variable would be article.edit. This ~~request~~ will ~~load~~ the article subcontroller and ~~execute~~ the edit method. You may have a question, this mean we will display edit form to user. That is right! ~~for~~ general we do that but in Joomla! 1.6 core component, it just ~~set~~ article id to be edit in user session and ~~redirect~~ it to URL like &view=article&layout=edit. And this will be handled by master controller and edit form will be presented to user. So in this case, all display will be handled by master controller and ~~need~~ views.	+	For example, to edit an article the task variable would be article.edit. This will cause the article subcontroller to be loaded and the edit method to be executed. You may have a question, this mean we will display edit form to user. That is right! In general we do that, but in Joomla! 1.6 core component, it just sets the article id to be edit in the user session and redirects it to an URL like &view=article&layout=edit. And this will be handled by master controller and edit form will be presented to user. So in this case, all display will be handled by master controller and needed views.

	* If a view name is not defined in URL, default view is used and a default task (display) will be executed. We use this to display a list of records. For example, index.php?option=com_content.		* If a view name is not defined in URL, default view is used and a default task (display) will be executed. We use this to display a list of records. For example, index.php?option=com_content.

User:DiepAkins990

DiepAkins990 — Wed, 23 May 2012 16:44:41 GMT

New user account

User:MeldrumRodas265

MeldrumRodas265 — Wed, 23 May 2012 16:44:06 GMT

New user account

JController and its subclass usage overview

Mcormier — Wed, 23 May 2012 16:44:01 GMT

Master Controller:

← Older revision		Revision as of 16:44, 23 May 2012
(One intermediate revision not shown)
Line 26:		Line 26:

	The master controller found in the root folder is only responsible for the display task. This is the default task for JController. If you look at JController::getInstance in com_content/content.php, only the component name was passed as a parameter. In JController, it uses the task variable (from the request) to determine what Controller class to load. If the task variable contains a dot (.), it assumes that this variable is in the form of controller.task or controller.method. You should know that task variable specifies method of controller to run. Then in this case, it will load controller class in controllers folder and rewrite task variable to real task. If the task does not contain a dot (.), JController will load the master controller located in the root folder. To simplify, we will refer to controllers in 'controllers' folder as subcontroller. You may notice that in the master controller, a default view is also specified. If there is no view variable in the URL request, this one will be used. So in general, we can conclude:		The master controller found in the root folder is only responsible for the display task. This is the default task for JController. If you look at JController::getInstance in com_content/content.php, only the component name was passed as a parameter. In JController, it uses the task variable (from the request) to determine what Controller class to load. If the task variable contains a dot (.), it assumes that this variable is in the form of controller.task or controller.method. You should know that task variable specifies method of controller to run. Then in this case, it will load controller class in controllers folder and rewrite task variable to real task. If the task does not contain a dot (.), JController will load the master controller located in the root folder. To simplify, we will refer to controllers in 'controllers' folder as subcontroller. You may notice that in the master controller, a default view is also specified. If there is no view variable in the URL request, this one will be used. So in general, we can conclude:
-	* To use the master controller, specify a view variable as view name to use or default one will be used.	+	* To use the master controller, specify a view variable as view name to use or the default one will be used.
	* To use a subcontroller, specify the task variable in the form of controller.task, clearly specified CONTROLLER_NAME.CONTROLLER_METHOD.		* To use a subcontroller, specify the task variable in the form of controller.task, clearly specified CONTROLLER_NAME.CONTROLLER_METHOD.

Line 50:		Line 50:


-	For example, ~~article~~ edit~~, its~~ task variable is article.edit. This request will load the article subcontroller and execute the edit method. You may have a question, this mean we will display edit form to user. That is right! for general we do that but in Joomla! 1.6 core component, it just set article id to be edit in user session and redirect it to URL like &view=article&layout=edit. And this will be handled by master controller and edit form will be presented to user. So in this case, all display will be handled by master controller and need views.	+	For example, to edit an article the task variable would be article.edit. This request will load the article subcontroller and execute the edit method. You may have a question, this mean we will display edit form to user. That is right! for general we do that but in Joomla! 1.6 core component, it just set article id to be edit in user session and redirect it to URL like &view=article&layout=edit. And this will be handled by master controller and edit form will be presented to user. So in this case, all display will be handled by master controller and need views.

	* If a view name is not defined in URL, default view is used and a default task (display) will be executed. We use this to display a list of records. For example, index.php?option=com_content.		* If a view name is not defined in URL, default view is used and a default task (display) will be executed. We use this to display a list of records. For example, index.php?option=com_content.

← Older revision		Revision as of 18:56, 23 May 2012
(One intermediate revision not shown)
Line 49:		Line 49:
	* [[Managing Component Updates with Joomla!1.6 - Part 1]] {{JVer\|1.6}}		* [[Managing Component Updates with Joomla!1.6 - Part 1]] {{JVer\|1.6}}
	* [[Xml-rpc changes in Joomla! 1.6]] {{JVer\|1.6}}		* [[Xml-rpc changes in Joomla! 1.6]] {{JVer\|1.6}}
		+	* [[Components:jform fields]]. and their usage {{JVer\|2.5}}
	</onlyinclude>		</onlyinclude>