Making single installation packages for Joomla! 1.5 and 2.5 series - Revision history

Wilsonge: Add migration category

2013-05-09T13:45:08Z

Add migration category

Wilsonge: Remove 1.6 and 1.7 tags

2013-04-29T22:59:46Z

Remove 1.6 and 1.7 tags

Wilsonge at 22:42, 12 February 2013

2013-02-12T22:42:38Z

Wilsonge at 22:04, 1 February 2013

2013-02-01T22:04:37Z

Wilsonge: /* More tricks? */

2013-02-01T22:04:18Z

‎More tricks?

Wilsonge: /* Content plugins work slightly different */

2013-02-01T22:03:07Z

‎Content plugins work slightly different

Wilsonge: /* Content plugins work slightly different */

2013-02-01T22:01:53Z

‎Content plugins work slightly different

Wilsonge: /* Obsolete code */

2013-02-01T22:01:33Z

‎Obsolete code

Wilsonge: /* JElement vs JFormField */

2013-02-01T22:01:11Z

‎JElement vs JFormField

Wilsonge: /* Tips and tricks for language strings */

2013-02-01T21:59:07Z

‎Tips and tricks for language strings

← Older revision		Revision as of 13:45, 9 May 2013
Line 387:		Line 387:

	Nicholas K. Dionysopoulos, AkeebaBackup.com Lead Developer		Nicholas K. Dionysopoulos, AkeebaBackup.com Lead Developer
		+
		+	<noinclude>[[Category:Migration]]</noinclude>

← Older revision		Revision as of 22:59, 29 April 2013
Line 1:		Line 1:
−	{{version\|1.5~~,1.6,1.7~~,2.5}}	+	{{version\|1.5,2.5}}
	It is possible to create a single installation package which can install a component in Joomla! 1.5, 1.6, 1.7 and 2.5 with minor changes. Below you will find some of the most common tricks required to create an extension which is compatible with all current versions of the Joomla! CMS.		It is possible to create a single installation package which can install a component in Joomla! 1.5, 1.6, 1.7 and 2.5 with minor changes. Below you will find some of the most common tricks required to create an extension which is compatible with all current versions of the Joomla! CMS.

← Older revision		Revision as of 22:42, 12 February 2013
Line 1:		Line 1:
		+	{{version\|1.5,1.6,1.7,2.5}}
	It is possible to create a single installation package which can install a component in Joomla! 1.5, 1.6, 1.7 and 2.5 with minor changes. Below you will find some of the most common tricks required to create an extension which is compatible with all current versions of the Joomla! CMS.		It is possible to create a single installation package which can install a component in Joomla! 1.5, 1.6, 1.7 and 2.5 with minor changes. Below you will find some of the most common tricks required to create an extension which is compatible with all current versions of the Joomla! CMS.

← Older revision		Revision as of 22:04, 1 February 2013
Line 1:		Line 1:
−	~~{{review}}~~
−
	It is possible to create a single installation package which can install a component in Joomla! 1.5, 1.6, 1.7 and 2.5 with minor changes. Below you will find some of the most common tricks required to create an extension which is compatible with all current versions of the Joomla! CMS.		It is possible to create a single installation package which can install a component in Joomla! 1.5, 1.6, 1.7 and 2.5 with minor changes. Below you will find some of the most common tricks required to create an extension which is compatible with all current versions of the Joomla! CMS.

@@ Line 383: / Line 383: @@
 == More tricks? ==
-I am sure that by writing this page I have left out a number of tricks which I am already using in my software. If you get stuck somewhere, feel free to take a look at how I've implemented things in Admin Tools Core, Akeeba Backup Core and Akeeba Release System, my Joomla! 1.5/1.6/1.7 compatible extensions. If you find a better way to implement something, or found a trick not listed here, feel free to edit this wiki page. Sharing the knowledge is caring!
+I am sure that by writing this page I have left out a number of tricks which I am already using in my software. If you get stuck somewhere, feel free to take a look at how I've implemented things in Admin Tools Core, Akeeba Backup Core and Akeeba Release System, my Joomla! 1.5/1.6/1.7/2.5 compatible extensions. If you find a better way to implement something, or found a trick not listed here, feel free to edit this wiki page. Sharing the knowledge is caring!
 Peace, love and friendship,
 Nicholas K. Dionysopoulos, AkeebaBackup.com Lead Developer

@@ Line 245: / Line 245: @@
 	public function onContentPrepare($context, &$row, &$params, $page = 0)
+	{
-		// Danger, Will Robinson! $row in Joomla! 1.6/1.7 may be a string, not an article object!
+		// Danger, Will Robinson! $row in Joomla! 1.6/1.7/2.5 may be a string, not an article object!
 		if(is_object($row)) {
 			return $this->onPrepareContent($row, $params, $page);

@@ Line 229: / Line 229: @@
 == Content plugins work slightly different ==
-The content plugins in Joomla! 1.5 were using the onPrepareContent method, whereas the content plugins in Joomla! 1.6/1.7 use the onContentPrepare method. The arguments have also changed. You can, however, create a single content plugin which runs on both Joomla! versions without rewriting code. Here's how:
+The content plugins in Joomla! 1.5 were using the onPrepareContent method, whereas the content plugins in Joomla! 1.6/1.7/2.5 use the onContentPrepare method. The arguments have also changed. You can, however, create a single content plugin which runs on both Joomla! versions without rewriting code. Here's how:
 <source lang="php">

@@ Line 216: / Line 216: @@
 == Obsolete code ==
-Joomla 1.6 / 1.7 have been left any code obsolete, we should review code for do compatible with all versions.
+Joomla 1.6 / 1.7/2.5 have been left any code obsolete, we should review code for do compatible with all versions.
 === Global Mainframe ===
 Bad: <source>global $mainframe;</source>

@@ Line 155: / Line 155: @@
 </source>
-As you see, we instruct both Joomla! 1.5 and 1.6/1.7 to look into the same directory, for the same-named file (sql2.php). Here are the contents of the modules/mod_foobar/elements/sql2.php file:
+As you see, we instruct both Joomla! 1.5 and 1.6/1.7/2.5 to look into the same directory, for the same-named file (sql2.php). Here are the contents of the modules/mod_foobar/elements/sql2.php file:
 <source lang="php">
@@ Line 161: / Line 161: @@
 /*
-  * This trick allows us to extend the correct class, based on whether it's Joomla! 1.5 or 1.6
+  * This trick allows us to extend the correct class, based on whether it's Joomla! 1.5 or 2.5 series
   */
 if(!class_exists('JFakeElementBase')) {
          if(version_compare(JVERSION,'1.6.0','ge')) {
                  class JFakeElementBase extends JFormField {
-                         // This line is required to keep Joomla! 1.6/1.7 from complaining
+                         // This line is required to keep Joomla! 1.6/1.7/2.5 from complaining
                          public function getInput() {}
+                 }
@@ Line 191: / Line 191: @@
+	}
-	// Joomla! 1.6
+	// Joomla! 2.5 series
 	function getInput()
+	{
@@ Line 212: / Line 212: @@
 </source>
-Considering that most custom widgets have a lot more code than this, you can create two different initialisation sections for Joomla! 1.5 and 1.6/1.7 (fetchElement and getInput), populate class variables, then call a big, common method to render the bulk of the widget (just like we did with JHTML's genericlist in the example above). This will eliminate the need to rewrite the same code over again just to cater for a new Joomla! version.
+Considering that most custom widgets have a lot more code than this, you can create two different initialisation sections for Joomla! 1.5 and 1.6/1.7/2.5 (fetchElement and getInput), populate class variables, then call a big, common method to render the bulk of the widget (just like we did with JHTML's genericlist in the example above). This will eliminate the need to rewrite the same code over again just to cater for a new Joomla! version.
 == Obsolete code ==

@@ Line 103: / Line 103: @@
 to this:
 COM_FOOBAR_SOME_KEY="<a href='http://www.example.com'>Just a test</a>"
-It is valid HTML, it works on Joomla! 1.5/1.6/1.7 but it will invalidates XHTML. You can't always win, sorry.
+It is valid HTML, it works on Joomla! 1.5/1.6/1.7/2.5 but it will invalidates XHTML. You can't always win, sorry.
 === Making untranslated strings look more beautiful ===