Joomla! Documentation - Changes related to "Developers" [en]

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:

Module Development/Reading list

2013-05-17T07:47:12Z

Add 1.5 version

Creating a simple module

2013-05-17T07:46:26Z

Add 1.5 version link

Access Control List

2013-05-17T07:44:53Z

Remove 2.5 link

J3.1:Using Tags in an Extension

2013-05-17T07:41:17Z

Update Category

Layout Overrides in Joomla 2.5

2013-05-15T09:11:47Z

‎Plugin Alternative Layouts (Tested with Joomla 3.1):

Security and Performance FAQs

2013-05-14T20:41:13Z

← 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 ==

@@ Line 1: / Line 1: @@
-* [[Creating a simple module|Creating a simple module for Joomla 2.5 and 3.x]] {{JVer|2.5}} {{JVer|3.x}}
+* [[Creating a simple module|Creating a simple module for Joomla]] {{JVer|1.5}} {{JVer|2.5}} {{JVer|3.x}}
 * [[J2.5:Adapting_a_Joomla_1.5_extension_to_Joomla_2.5|Adapting a Joomla 1.5 extension to Joomla 2.5]] {{JVer|2.5}}
 * [[Extensions name]]<noinclude>[[Category:Landing subpages|{{PAGENAME}}]]</noinclude>

← Older revision		Revision as of 07:46, 17 May 2013
Line 1:		Line 1:
−	{{version/tutor\|2.5,3.1}}{{other versions/navbox\|The '''Creating a simple module''' Tutorial is available in these versions:-\|version}}	+	{{version/tutor\|1.5,2.5,3.1}}
		+	The following pages give further information on Joomla ACL:-
		+	* {{JVer\|1.5}} [[J1.5:Creating_a_simple_module\|Creating a simple module for Joomla 1.5]]
		+	{{other versions/navbox\|The '''Creating a simple module''' Tutorial is available in these versions:-\|version}}
	<noinclude>[[Category:Tutorials]][[Category:Module Development]]</noinclude>		<noinclude>[[Category:Tutorials]][[Category:Module Development]]</noinclude>

@@ Line 6: / Line 6: @@
 The following pages give further information on Joomla ACL:-
 * {{JVer|1.5}} [[J1.5:Access_Control_List/Tutorial|ACL Tutorial for Joomla 1.5]]
 <noinclude><br/>
 {{other versions/navbox||versions|pages=Access Control List Tutorial}}</noinclude>
 <noinclude>[[Category:Landing Pages]][[Category:Access Control]] [[Category:Glossary]][[Category:Access Management]][[Category:References]]</noinclude>

← Older revision		Revision as of 07:41, 17 May 2013
Line 295:		Line 295:


−	[[Category:Development]][[Category:Tags]]	+	[[Category:Development]][[Category:Content Tags]]

← Older revision		Revision as of 09:11, 15 May 2013
(2 intermediate revisions by one user not shown)
Line 25:		Line 25:

	It is important to understand that if specified in the Module Manager screen, an alternative layout file for a module will be used for that module regardless of what template is used to display the page where the module is shown. It is therefore the administrator's responsibility to make sure that the layout file will work as desired in any templates where this module may be shown.		It is important to understand that if specified in the Module Manager screen, an alternative layout file for a module will be used for that module regardless of what template is used to display the page where the module is shown. It is therefore the administrator's responsibility to make sure that the layout file will work as desired in any templates where this module may be shown.
		+
		+	=== Plugin Alternative Layouts (Tested with Joomla 3.1) ===
		+	Yes,it's possible to override plugin outputs.It's very useful, especially for content plugins.
		+
		+	For example to override the output of pagenavigation content plugin in "beez5" template, (It's responsible to show previous/next article links in article view of content component), create a folder named "templates/beez5/html/plg_content_pagenavigation/" and copy the original layout file (plugins/content/pagenavigation/tmpl/default.php) to this new folder.
		+
		+	So you can change this layour file to override plugin output.
		+
		+	Note:I think, this feature is very new, not all plugins support this yet

	=== Component Alternative Layouts ===		=== Component Alternative Layouts ===

@@ Line 1,362: / Line 1,362: @@
 # '''Note suspicious recently-modified files:''' Check the modified files list for any files that were recently changed. Pay particular attention to the modification, and correlate them to the dates of attacks shown in your log files.
 # '''Check for bogus CRON Jobs:''' Hacked cron jobs can be setup to reinfect your site over and over again.
-# '''Coordinate with your host:''' If you have identified how you were cracked, report the method to your host. If you are on a shared server, you may habe been attacked through another vulnerable site on your server. Report this to your host. A reputable host will appreciate your efforts in this area.
+# '''Coordinate with your host:''' If you have identified how you were cracked, report the method to your host. If you are on a shared server, you may have been attacked through another vulnerable site on your server. Report this to your host. A reputable host will appreciate your efforts in this area.
 # '''Delete the entire public_html directory:''' This is the best way to guarantee that every potential vulnerability in that site is removed.
 # '''Delete related database records:''' This step may only be possible if you have good backups. Simple script kiddies, who are only trying to mark your index page, may not attack your database, but professionals are usually very interested in confidential data, such as passwords. They may pose as script kiddies to avoid suspicion while repeatedly harvesting confidential information from your database.
-# '''Reinstall everything:''' Use pre-crack backups. If you don't have good backups, go on to step 10.
+# '''Reinstall everything:''' Use pre-crack backups. If you don't have good backups, reinstall everything anyways.
-# '''Reset critical passwords again:''' You must reset your passwards again now that your server is finally cleaned of any possible, hidden trojan horses.
+# '''Reset critical passwords again:''' You must reset your passwords again now that your server is finally cleaned of any possible hidden trojan horses.
 # '''Rebuild site:''' If you are unable to rebuild from clean backups, rebuild your entire site using original, pre-crack installs. Use only the latest stable versions of all software, and check the List of Vulnerable Extensions
 # '''Review security processes:''' Follow standard security precautions for important settings in php.ini, globals.php, configuration.php, .htaccess, etc.