Joomla! Documentation - Changes related to "Component Development/Reading list" [en]

Managing Component Updates with Joomla!2.5 - Part 1

2013-05-24T11:58:52Z

Hutchy68 moved page Managing Component Updates with Joomla!2.5 - Part 1 to J2.5:Managing Component Updates namespacing for version

Managing Component Updates with Joomla!2.5 - Part 1

2013-05-24T11:57:59Z

Hutchy68 moved page Managing Component Updates with Joomla!2.5 - Part 1 to Managing Component Updates namespacing for version

Creating Mootools accordion or simple slider/toggler

2013-05-24T00:39:54Z

Hutchy68 moved page Creating Mootools accordion or simple slider/toggler to J2.5:Creating Mootools accordion or simple slider/toggler namespacing for version

Using the JToolBar class in the frontend

2013-05-18T18:00:00Z

updating for disambiguation

Using the JToolBar class in the frontend

2013-05-18T17:47:58Z

Hutchy68 moved page Using the JToolBar class in the frontend to J1.5:Using the JToolBar class in the frontend namespacing

Using the JToolBar class in the frontend

2013-05-18T17:45:22Z

splitting article to archive 1.5 material

J3.1:Using Tags in an Extension

2013-05-18T16:55:36Z

‎Add or modify a delete() method:

← Older revision		Revision as of 18:00, 18 May 2013
Line 1:		Line 1:
−	~~#REDIRECT [[J1~~.5:Using the JToolBar class in the frontend]]	+	{{disambig\|
		+	{{version\|2.5,3.1}}
		+	}}
		+	{{other versions/navbox\|The '''Using the JToolBar class in the frontend''' article is available in these versions:-\|version}}
		+	<noinclude>[[Category:Tutorials]][[Category:Component Development]]</noinclude>
		+	<noinclude>[[Category:Development]]</noinclude>

← Older revision		Revision as of 17:45, 18 May 2013
Line 1:		Line 1:
−	~~== Using JToolBar in 1.6 and newer with Search Engine Friendly enabled (SEF)==~~
−	~~When using the toolbar on the frontend,the standard buttons will sometimes bug out. This is usually because Search Engine Friendly urls is defined.~~
−
−	~~What happens is that instead of going to index.php?option=com_yourcom&view=&...#, it will go to index.php/friendlyurl# . This bugs out many users.~~
−
−	Using these two together can be done,however. There's two tricks to it. First, make a class called JButtonFrontend and extend JButton. For this, jimport('joomla.html.toolbar') has to be done,because this includes the standard button classes.
−
−	~~Just copy over the content of joomla.html.toolbar.button standard.php; then, change the fetchbutton function~~
−	~~<source lang="php">~~
−	~~//Goes inside JButtonFrontend class definition.~~
−	~~public function fetchButton($type = 'Standard', $name = '', $text = '', $task = '', $list = true)~~
−	{
−	~~$i18n_text = JText::_($text);~~
−	~~$class = $this->fetchIconClass($name);~~
−	~~$doTask = $this->_getCommand($text, $task, $list);~~
−
−	~~$html = "<a href=\"javascript: void( $doTask);\" onclick=\"$doTask\" class=\"toolbar\">\n";~~
−	~~$html .= "<span class=\"$class\">\n";~~
−	~~$html .= "</span>\n";~~
−	~~$html .= "$i18n_text\n";~~
−	~~$html .= "</a>\n";~~
−
−	~~return $html;~~
−	}
−	~~</source>~~
−
−	~~Then, in your mainfile (site/yourcom.php), use this:~~
−	~~<source lang="php">~~
−	~~JLoader::register('JButtonFrontend', dirname(__FILE__) . DS . 'buttons' . DS . 'frontend.php');~~
−	~~</source>~~
−
−	~~As you can see, I made a directory called 'buttons' in my /site directory. If you do so, don't forget to add it to your package xml file! (yourcom.xml).~~
−
−	~~You can now use the 'Frontend' button:~~
−	~~<source lang="php">~~
−	~~$this->bar->appendButton( 'Frontend', 'name', 'label', 'subcontroller.method', false );~~
−	~~</source>~~
−
−	~~== Using JToolBar in 2.5 and newer==~~
−	~~{{JVer/multi\|2.5,3.x}}~~
−	~~It's even simpler to use JToolBar in the front end, as it only requires two steps.~~
−	~~First (Using the MVC architecture of 1.6), add a function definition to view.html.php file in the view you wish to add the toolbar to.~~
−	~~<source lang="php>~~
−	~~function getToolbar() {~~
−	~~// add required stylesheets from admin template~~
−	~~$document = & JFactory::getDocument();~~
−	~~$document->addStyleSheet('administrator/templates/system/css/system.css');~~
−	~~//now we add the necessary stylesheets from the administrator template~~
−	~~//in this case i make reference to the bluestork default administrator template in joomla 1.6~~
−	~~$document->addCustomTag(~~
−	~~'<link href="administrator/templates/bluestork/css/template.css" rel="stylesheet" type="text/css" />'."\n\n".~~
−	~~'<!--[if IE 7]>'."\n".~~
−	~~'<link href="administrator/templates/bluestork/css/ie7.css" rel="stylesheet" type="text/css" />'."\n".~~
−	~~'<![endif]-->'."\n".~~
−	~~'<!--[if gte IE 8]>'."\n\n".~~
−	~~'<link href="administrator/templates/bluestork/css/ie8.css" rel="stylesheet" type="text/css" />'."\n".~~
−	~~'<![endif]-->'."\n".~~
−	~~'<link rel="stylesheet" href="administrator/templates/bluestork/css/rounded.css" type="text/css" />'."\n"~~
−	);
−	~~//load the JToolBar library and create a toolbar~~
−	~~jimport('joomla.html.toolbar');~~
−	~~$bar =& new JToolBar( 'toolbar' );~~
−	~~//and make whatever calls you require~~
−	~~$bar->appendButton( 'Standard', 'save', 'Save', 'savetask', false );~~
−	~~$bar->appendButton( 'Separator' );~~
−	~~$bar->appendButton( 'Standard', 'cancel', 'Cancel', 'canceltask', false );~~
−	~~//generate the html and return~~
−	~~return $bar->render();~~
−	}
−	~~</source>~~
−	Now in the corresponding tmpl file, you simply need to add code like the following (added here to a default.php file in the tmpl folder of the view to which the code above was added to the view.html.php file.
−	~~Note I say "like" the following, changes may be required. I'm including the <form> declaration html (the toolbar MUST be in a form with the id of "adminForm" in order for it to work.~~
−	~~<source lang="php">~~
−	~~<form action="index.php" method="post" id="adminForm" name="adminForm">~~
−	~~<?php echo $this->getToolbar(); ?>~~
−	~~<input type = "hidden" name = "task" value = "" />~~
−	~~<input type = "hidden" name = "option" value = "com_yourcom" />~~
−	~~</form>~~
−	~~<div class="clr"></div>~~
−	~~</source>~~
−	You'll note the [div class="clr"] which you may or may not need depending on your own design requirements. If you don't add the div tag, slapping this code into an existing component front end will place the buttons to the right and level with the content on the left.
−	~~Also, and as explained above, you'll need to add functions within the controller that is called when one of the toolbar buttons is pressed, to process the request gracefully.~~
−
	== Using JToolBar in 1.5 ==		== Using JToolBar in 1.5 ==
	{{JVer\|1.5}}		{{JVer\|1.5}}

@@ Line 127: / Line 127: @@
 	public function delete($pk = null)
+	{
-		$return = parent::delete($pk, $children);
+		$result = parent::delete($pk);
-		if ($return)
+		return $result && $this->tagsHelper->deleteTagData($this, $pk);
-−
+	}
-			$helper = new JHelperTags;
-			$helper->tagDeleteInstances($pk);
-−
-		return $return;	}
 </source>
 This manages the deletion of all related data if a content item is deleted.
 == Add tags to the getItem() method of the model ==