Joomla! Documentation - User contributions [en]

J3.x:The reCaptcha function has been temporarily disabled for Joomla 3.2

2013-11-09T00:24:15Z

AmyStephen: /* How to fix */

Error Message: The mail function has been temporarily disabled on this site

== What is the cause ==
Google [changed the reCAPTCHA URL](https://groups.google.com/forum/#!topic/recaptcha/V7qswqBnA1o)

== How to fix ==

For v 3.2, go to plugins/captcha/recaptcha/recaptcha.php and change:
:- line 22 to the new RECAPTCHA_API_SERVER URL of 'http://www.google.com/recaptcha/api'
:- line 24 to the new RECAPTCHA_VERIFY_SERVER URL of 'www.google.com'
:- line 129 to the new RECAPTCHA_VERIFY_SERVER value of '/recaptcha/api/verify'

See the change in the next patch: https://github.com/SniperSister/joomla-cms/commit/01e3c84d653c4331f7e11c85aa605426c00bbf6a

This fix will be included in the next release.

<noinclude>
[[Category:Version 3.2.0 FAQ]]
</noinclude>

Please first make a selection from the list

2012-01-28T18:37:49Z

AmyStephen: /* Extension Developers */

This error message manifests on Administrator Forms for many non-core extensions even when an item has been selected.

This backwards compatibility error will be fixed in core for 2.5.1.

==Temporary Workaround==

Install the plugin from this forum item [http://forum.joomla.org/viewtopic.php?f=625&t=691865]

==Extension Developers==
To address this problem now so that your users do not have to wait for a core fix, update your Administrator forms and change name="adminForm" to id="adminForm". If backwards compatibility is required, simply use both values in the form definition. In future releases, Joomla will only support id="adminForm"

==Patch==
A [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27880 patch has been created] to fix the backwards compatibility in 2.5.1

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.0 FAQ]]

Please first make a selection from the list

2012-01-28T18:37:36Z

AmyStephen: /* Temporary Workaround */

This error message manifests on Administrator Forms for many non-core extensions even when an item has been selected.

This backwards compatibility error will be fixed in core for 2.5.1.

==Temporary Workaround==

Install the plugin from this forum item [http://forum.joomla.org/viewtopic.php?f=625&t=691865]

==Extension Developers==
* To address this problem now so that your users do not have to wait for a core fix, update your Administrator forms and change name="adminForm" to id="adminForm". If backwards compatibility is required, simply use both values in the form definition. In future releases, Joomla will only support id="adminForm"

==Patch==
A [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27880 patch has been created] to fix the backwards compatibility in 2.5.1

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.0 FAQ]]

Please first make a selection from the list

2012-01-28T18:37:03Z

AmyStephen: /* Temporary Workaround */

This error message manifests on Administrator Forms for many non-core extensions even when an item has been selected.

This backwards compatibility error will be fixed in core for 2.5.1.

==Temporary Workaround==

* Install the plugin from this forum item [http://forum.joomla.org/viewtopic.php?f=625&t=691865]

==Extension Developers==
* To address this problem now so that your users do not have to wait for a core fix, update your Administrator forms and change name="adminForm" to id="adminForm". If backwards compatibility is required, simply use both values in the form definition. In future releases, Joomla will only support id="adminForm"

==Patch==
A [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27880 patch has been created] to fix the backwards compatibility in 2.5.1

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.0 FAQ]]

Please first make a selection from the list

2012-01-28T18:36:50Z

AmyStephen:

This error message manifests on Administrator Forms for many non-core extensions even when an item has been selected.

This backwards compatibility error will be fixed in core for 2.5.1.

==Temporary Workaround==

* Install the plugin from this forum item [http://forum.joomla.org/viewtopic.php?f=625&t=691865], or 

==Extension Developers==
* To address this problem now so that your users do not have to wait for a core fix, update your Administrator forms and change name="adminForm" to id="adminForm". If backwards compatibility is required, simply use both values in the form definition. In future releases, Joomla will only support id="adminForm"

==Patch==
A [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27880 patch has been created] to fix the backwards compatibility in 2.5.1

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.0 FAQ]]

Archived:Creating a Custom 404 Error

2012-01-15T03:52:09Z

AmyStephen:

This tutorial will show you how to create a custom 404 Error Page for use in your Joomla 1.5 Web Site.

== Four Steps to Creating a Custom 404 Error Page ==

# '''Create an Uncategorized '404' Article'''
#: Create an 'uncategorized' article in Joomla! to serve as your 404 Page. Include some text such as ''Sorry, we could not find the page you were looking for...'' and if necessary, also any useful navigational links. For example, you may wish to add a link back to your site's home page.
# '''Create and copy a link to that new 404 Article.'''
#: Create a menu item which links to the new 404 Article and 'apply' your changes. Then copy the URL information (index.php?optio...), set the menu item as 'unpublished' and close out of the menu editing page. You may want to paste the copied URL into Notepad or somewhere accessible for the time-being.
# '''Copy error.php to your Template's Directory'''
#: In your Joomla! installation copy the file error.php from the templates/system directory, to your Template directory. For example, if I was using a template named 'Cleancloud' I would copy the error.php file to the templates/cleancloud directory.
# '''Modify error.php to Redirect 404 Errors to your 404 Article '''
#: Edit the error.php file as follows, adding the code below immediately under the 'restricted access' line:
<source lang="php">
if (($this->error->code) == '404') {
header('Location: /index.php?option=com_content&view=article&id=75');
exit;
}
</source>
If you are using Joomla 1.6/1.7, use this detection code instead:
<source lang="php">
if (($this->error->getCode()) == '404') {
</source>
::: Replace the location information (index.php?option..) with the URL from the menu item you created.

== Additional Steps toward a Better Custom 404 Error Page ==

* Add the following line to the robots.txt file located in the root directory of your Joomla! installation.
*: <code>Disallow: /index.php?option=com_content&view=article&id=75</code>
* Replacing the (index.php?option..) location with your 404 Article URL.
* Follow the Best-Practices described here: http://www.alistapart.com/articles/perfect404/
* Be creative, add a [http://www.geekhaiku.com/tag/404/ 404 Haiku] or maybe an [http://www.smashingmagazine.com/2007/08/17/404-error-pages-reloaded Interesting Photo]

== More Custom Error Page Information ==

* [[Custom_error_pages|Custom Error Pages]]
* [[System_error_pages|System Error Pages]]
* [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html HTTP/1.1 Status Code Definitions]
* [http://www.google.com/support/webmasters/bin/answer.py?answer=83040&topic=8474 Google Webmaster - Analyzing Crawl Errors]

[[Category:Management]]
[[Category:Tutorials]]

Upgrading 1.6.5 to 1.7

2011-07-20T23:32:42Z

AmyStephen: Reverted edits by Mvangeest (talk) to last revision by AmyStephen

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[#Quick_Update | Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin:

* Check that all installed extensions are compatible with Joomla 1.7 by checking the JED Listing or developer site.

* [[Backup | Backup]] the website files and database.

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:1-Extensions-ExtensionManager.png]]

2. Click the '''Update''' Sub menu.

[[Image:2-Extension-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:3-Extension-Manager-Update.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar.

'''Be patient while the system downloads and replaces the necessary files.''' This can take several minutes or could update very quickly, depending on your system.

[[Image:4-Update-Joomla.png]]

5. When the update has finished, you will be presented with this page.

[[Image:6-Final.png]]

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

1.7.0 List of API Changes

2011-07-20T13:06:09Z

AmyStephen:

1.7.0 is a point release that includes a number of API changes.

In some cases, developers must modify their Extensions to work with this release. A [http://docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_1.7_and_Joomla_Platform_11.1 list of those changes is available] to help developers with the migration.

[[Category:Version 1.7.0 FAQ]]

1.7.0 List of API Changes

2011-07-20T13:01:13Z

AmyStephen:

1.7.0 is a point release that includes a number of API changes.

In some cases, developers must modify their Extensions to work with this release. A [http://docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_1.7_and_Joomla_Platform_11.1 |list of those changes is available] to help developers with the migration.

[[Category:Version 1.7.0 FAQ]]

1.7.0 List of API Changes

2011-07-20T13:00:18Z

AmyStephen: Created page with "1.7.0 is a point release that includes a number of API changes. In some cases, developers must modify their Extensions to work with this release. A [[http://docs.joomla.org/Pot..."

1.7.0 is a point release that includes a number of API changes.

In some cases, developers must modify their Extensions to work with this release. A [[http://docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_1.7_and_Joomla_Platform_11.1 |list of those changes is available] to help developers with the migration.

[[Category:Version 1.7.0 FAQ]]

Upgrading 1.6.5 to 1.7

2011-07-20T11:55:07Z

AmyStephen: /* Quick Update */

Upgrading 1.6.5 to 1.7

2011-07-19T21:50:55Z

AmyStephen:

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[#Quick_Update | Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, [[Backup | backup]] your website files and database. '''This is important'''.

[[Image:1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:2-Extension-Update.png]]

2. Click the '''Update''' Sub menu.

[[Image:3-Extension-Manager-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:4-Update-Joomla.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar.

'''Be patient while the system downloads and replaces the necessary files.''' This can take several minutes or could update very quickly, depending on your system.

[[Image:6-Final.png]]

5. When the update has finished, you will be presented with this page.

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Upgrading 1.6.5 to 1.7

2011-07-19T21:49:53Z

AmyStephen: /* Quick Update */

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, [[Backup | backup]] your website files and database. '''This is important'''.

[[Image:1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:2-Extension-Update.png]]

2. Click the '''Update''' Sub menu.

[[Image:3-Extension-Manager-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:4-Update-Joomla.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar.

'''Be patient while the system downloads and replaces the necessary files.''' This can take several minutes or could update very quickly, depending on your system.

[[Image:6-Final.png]]

5. When the update has finished, you will be presented with this page.

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Upgrading 1.6.5 to 1.7

2011-07-19T21:48:56Z

AmyStephen: /* Quick Update */

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, [[Backup | backup]] your website files and database. '''This is important'''.

[[Image:1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:2-Extension-Update.png]]

2. Click the '''Update''' Sub menu.

[[Image:3-Extension-Manager-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:4-Update-Joomla.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

[[Image:6-Final.png]]

5. When the update has finished, you will be presented with this page.

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Upgrading 1.6.5 to 1.7

2011-07-19T21:48:27Z

AmyStephen: /* Quick Update */

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, [[Backup]] your website files and database. '''This is important'''.

[[Image:1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:2-Extension-Update.png]]

2. Click the '''Update''' Sub menu.

[[Image:3-Extension-Manager-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:4-Update-Joomla.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

[[Image:6-Final.png]]

5. When the update has finished, you will be presented with this page.

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Upgrading 1.6.5 to 1.7

2011-07-19T21:47:05Z

AmyStephen: /* Quick Update */

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, backup your website files and database. This is important.

[[Image:1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:2-Extension-Update.png]]

2. Click the '''Update''' Sub menu.

[[Image:3-Extension-Manager-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:4-Update-Joomla.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

[[Image:6-Final.png]]

5. When the update has finished, you will be presented with this page.

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Upgrading 1.6.5 to 1.7

2011-07-19T21:46:07Z

AmyStephen:

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, backup your website files and database. This is important.

[[Image:1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

[[Image:2-Extension-Update.png]]

2. Click the '''Update''' Sub menu.

[[Image:3-Extension-Manager-Update.png]]

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

[[Image:4-Update-Joomla.png]]

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

[[Image:6-Final.png]]

5. When the update has finished, you will be presented with this page.

'''That's it!''' Follow these simple instructions next time you upgrade. Now, it's to keep your Joomla website up-to-date and safe!

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

File:6-Final.png

2011-07-19T21:42:42Z

AmyStephen:

File:4-Update-Joomla.png

2011-07-19T21:42:10Z

AmyStephen:

File:3-Extension-Manager-Update.png

2011-07-19T21:41:38Z

AmyStephen:

File:2-Extension-Update.png

2011-07-19T21:41:11Z

AmyStephen:

File:1-Extensions-ExtensionManager.png

2011-07-19T21:30:32Z

AmyStephen: uploaded a new version of "File:1-Extensions-ExtensionManager.png"

Upgrading 1.6.5 to 1.7

2011-07-19T21:26:16Z

AmyStephen:

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, backup your website files and database. This is important.

[[File:http://docs.joomla.org/images/f/f9/1-Extensions-ExtensionManager.png]]

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

2. Click the '''Update''' Sub menu.

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

5. When the update has finished, you will be presented with this page.

That's it! For the next Upgrade, follow these simple instructions again. It's now easy to update a Joomla Website.

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

File:1-Extensions-ExtensionManager.png

2011-07-19T21:24:46Z

AmyStephen:

Upgrading 1.6.5 to 1.7

2011-07-19T21:00:58Z

AmyStephen: removed extra |

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update | Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager | Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation | Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, backup your Website files and database. This is important. Do not skip this step.

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

2. Click the '''Update''' Sub menu.

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

5. When the update has finished, you will be presented with this page.

That's it! For the next Upgrade, follow these simple instructions again. It's now easy to update a Joomla Website.

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Upgrading 1.6.5 to 1.7

2011-07-19T20:59:40Z

AmyStephen: Simplifying the instructions for the Quick Upgrade (pictures will be added next)

{{JVer|1.6}}{{JVer|1.7}}

Joomla! 1.7 introduces a [[#Quick_Update || Quick Update]] for sites already up-to-date with Joomla 1.6.5.

If your site is not already at 1.6.5, or you prefer not to use the [[Quick Update]], there are several other options:

* [[#Installation_Manager || Traditional Update using the Installation Manager]]
* [[Upgrading 1.6 from an existing 1.6x version|Sites on 1.6, but not on 1.6.5]]
* [[#Manual_Upload.2FInstallation || Manual Update for 1.6.5]]
* [[Migrating from Joomla 1.5 to Joomla_1.6+]]

== Quick Update ==

For sites already up-to-date running Joomla 1.6.5, upgrading to Joomla 1.7 is now very easy.

Before you begin, backup your Website files and database. This is important. Do not skip this step.

1. In the Administrator, select the '''Extensions-Extensions Manager''' Menu item.

2. Click the '''Update''' Sub menu.

3. Click the '''Purge Cache''', then '''Find Updates''' Buttons in the Button Bar located in the upper right of the page.

4. Click the checkbox to the left of the Joomla line containing the latest Version Number and, next, press the Update Button in the Button Bar. Be patient while the system downloads and replaces the necessary files. This can take several minutes or could update very quickly, depending on your system.

5. When the update has finished, you will be presented with this page.

That's it! For the next Upgrade, follow these simple instructions again. It's now easy to update a Joomla Website.

==Installation Manager ==

If you aren’t yet comfortable with using the Update Manager to update your site, you’re still ok! There are more easy options to update your site. The second method to update your Joomla! 1.6.5 site to 1.7.0 is to use the extension installer, just as if you were installing a component, module, plugin, or template in your site. This method is specially handy for users updating localized distributions made available by Language Communities.

To update your site using this method, first, download the update package from JoomlaCode. The 1.6.5 > 1.7.0 package can be found [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here].

{{ambox|image=notice|style=notice|text=If you are not currently on Joomla! 1.6.5, use [[Upgrading 1.6 from an existing 1.6x version|this tutorial]] to update your site to 1.6.5, then resume the process of updating to 1.7}}

After you download the update package, access your Joomla! installer by logging in to your adminstrator control panel, and navigating to the '''Extensions''' > '''Extension Manager''' option in your administrator menu. From here you can select the file you just downloaded, and install it. The Joomla! installer will upload the package, and install it, making any changes to files or the database as needed.

== Manual Upload/Installation ==

The last method available to update your site, involves a little more technical expertise, and should probably only be used if the previous methods won’t work due to a highly complex site or hosting issues (shared hosting for example). ''' As usual back-up your site and your database.''' For most Joomla! sites, the first two methods will successfully update your site. However, updating is still fairly easily, and should not be a problem.

Before you begin, go to global configuration and on the server tab and in the Database Settings area find the database table prefix used by your site.

To update your site manually, you will need to download the 1.6.5 > 1.7.0 update package from JoomlaCode. You can download it [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=5986 here]. Unpack the package and you will find two zip files in it. You will only need the large zip file called <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> for your update. Using an ftp client, upload the zip file to your server into the root directory of your website, and unpack the files. This will over-write any modified files with new, updated files for 1.7.0. Alternatively, you can unpack the <tt>Joomla_1.7.0-Stable-Update_Package.zip</tt> on your local computer, then copy the un-packed files into your websites root, overwriting the modified files.

After unpacking the files to your website you need to manually delete the files and folders listed in administrator/components/com_admin/script.php.

This is the list of files:

*<tt>/templates/atomic/css/blueprint/src/blueprintcss-0-9-1-cheatsheet-3-5-3-gjms.pdf</tt>
*<tt>/administrator/manifests/packages/joomla.xml</tt>
*<tt>/administrator/templates/bluestork/css/rounded.css</tt>
*<tt>/administrator/templates/bluestork/css/norounded.css</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_bl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right_rtl.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_right.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_black.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_bl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_dark.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_br_med.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tl_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_crn_tr_light.png</tt>
*<tt>/administrator/templates/bluestork/images/j_corner_br.png</tt>
*<tt>/administrator/templates/bluestork/images/j_header_left_rtl.png</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/modal.php</tt>
*<tt>/administrator/templates/hathor/html/com_modules/module/edit_assignment.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/item/edit_modules.php</tt>
*<tt>/administrator/templates/hathor/html/com_menus/items/default_batch.php</tt>
*<tt>/administrator/templates/hathor/html/com_languages/language/edit.php</tt>
*<tt>/administrator/templates/hathor/html/com_content/article/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/category/edit_metadata.php</tt>
*<tt>/administrator/templates/hathor/html/com_categories/categories/default_batch.php</tt>
*<tt>/administrator/components/com_menus/models/forms/item_options.xml</tt>
*<tt>/administrator/language/overrides/xx-XX.override.ini</tt>
*<tt>/administrator/help/helpsites-16.xml</tt>
*<tt>/administrator/help/en-GB/Components_Content_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Weblinks_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Newsfeeds_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Banners_Categories_Edit.html</tt>
*<tt>/administrator/help/en-GB/Components_Contact_Categories_Edit.html</tt>
*<tt>/media/editors/codemirror/css/docs.css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.js</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/media/css/content.css</tt>
*<tt>/media/mod_languages/images/ta.gif</tt>
*<tt>/libraries/joomla/config.php</tt>
*<tt>/libraries/joomla/import.php</tt>
*<tt>/libraries/joomla/version.php</tt>

And these folders:

*<tt>/plugins/authentication/example</tt>
*<tt>/plugins/user/example</tt>
*<tt>/plugins/content/example</tt>
*<tt>/plugins/extension/example</tt>
*<tt>/administrator/templates/hathor/html/com_modules/select</tt>
*<tt>/administrator/templates/hathor/html/com_media</tt>
*<tt>/administrator/templates/hathor/html/mod_popular</tt>
*<tt>/administrator/templates/hathor/html/mod_status</tt>
*<tt>/administrator/templates/hathor/html/mod_latest</tt>
*<tt>/administrator/components/com_weblinks/helpers/html</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/css</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/pagebreak/img</tt>
*<tt>/media/editors/tinymce/jscripts/tiny_mce/plugins/example</tt>

After you have done this you need to manually update your site's database. To do so locate the file <tt>installation/sql/mysql/joomla_update_17ga.sql</tt>, or the files <tt>/administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06.sql and administrator/components/com_admin/sql/updates/mysql/1.7.0-2011-06-06-2.sql</tt>.

As of July 16th 2011 the file(s) contains:

<source lang="sql">ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;
ALTER TABLE `#__languages` ADD INDEX `idx_ordering` (`ordering`);
</source>
<source lang="sql">CREATE TABLE IF NOT EXISTS `#__associations` (
`id` VARCHAR(50) NOT NULL COMMENT 'A reference to the associated item.',
`context` VARCHAR(50) NOT NULL COMMENT 'The context of the associated item.',
`key` CHAR(32) NOT NULL COMMENT 'The key for the association computed from an md5 on associated ids.',
PRIMARY KEY `idx_context_id` (`context`, `id`),
INDEX `idx_key` (`key`)
) DEFAULT CHARSET=utf8;

</source>

Inside you will find parts like <code>#__languages</code> and <code>#__associations</code>. Replace the pound sign and the first underscore (<code>#_</code>) with your [[Database Table Prefix|database tables prefix]]. By default this is <code>jos</code>. If you didn't get the prefix before starting, open your site's <tt>configuration.php</tt> and search for <code>$dbprefix</code>. The string inside the single quotes behind it is what you're looking for. So you need to change <code>#__languages</code> to <code>jos_languages</code> and so on.

Once you've done this go to your site's phpmyadmin (or any way you usually manage your database) and open the database your site uses. There will be a tab called SQL, open this. Paste the content of your modified <tt>joomla_update_17ga.sql</tt> inside the text area and press go.

Your site is now updated to Joomla 1.7.

[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

User:Rvsjoen/tutorial/Developing an MVC Component/Part 01

2011-07-10T01:56:11Z

AmyStephen:

= Developing a Basic Component =
Let's create a ''Hello World!'' component. All file name and path references in this tutorial are relative to the directory you are developing your extension in.

=== Basic frontend ===
With your favorite editor, create a file <tt>site/helloworld.php</tt> containing the following text, yes, it is very simple but its purpose is simply to demonstrate where the entry point of the component is. After all, this is part 01.

When Joomla! looks for a component it will look at the '''option''' variable given in the url, in our case this will be '''option=com_helloworld'''. This means that Joomla! will look in the <tt>components</tt> directory for a folder named <tt>com_helloworld</tt> and load the file <tt>helloworld.php</tt> contained within that directory.


'''<tt>site/helloworld.php</tt>'''
<source lang="php">
Hello World
</source>


=== Basic backend ===

You might at this point think to yourself, why are we creating a backend file when this part of the tutorial is only supposed to cover the frontend ? The answer to that question is simple, all configuration is done in the Administrator -- even though it is displayed for visitors in the frontend.

With your favorite editor, create a file <tt>admin/helloworld.php</tt> containing the following text


'''<tt>admin/helloworld.php</tt>'''
<source lang="php">
Hello Admins
</source>


=== Installation manifest ===

In order for our extension to be recognized by Joomla! we also need to provide an installation xml file, also called the manifest. Open up ''helloworld.xml'' in your favorite editor and add the following piece of code.


'''<tt>helloworld.xml</tt>'''
<source lang="xml" line>
<?xml version="1.0" encoding="utf-8"?>
<extension type="component" version="1.7.0" method="upgrade">

<name>Hello World!</name>

<creationDate>June 2011</creationDate>
<author>John Doe</author>
<authorEmail>john.doe@example.org</authorEmail>
<authorUrl>http://www.example.org</authorUrl>
<copyright>Copyright Info</copyright>
<license>License Info</license>

<version>0.0.1</version>

<description>Description of the Hello World component ...</description>



<files folder="site">
<filename>index.html</filename>
<filename>helloworld.php</filename>
</files>

<administration>

<menu>Hello World!</menu>


<files folder="admin">

<filename>index.html</filename>
<filename>helloworld.php</filename>
</files>
</administration>

</extension>
</source>


As we can see, there is a lot of markup here. This is pretty much a minimal extension manifest and we will try to explain the most important bits and pieces. First off, we notice that we have an administration section, using our reasoning skills this pretty much means that whats outside the administration section is for the site application. This is not the full truth but pretty close to it.

The <code><files></code> tag has an attribute '''folder''' which specifies which folder to look for the files in inside our extension package. Our top level extension structure has two folders <tt>site</tt> and <tt>admin</tt>. So what this tag does is tell the Joomla! installer which files to copy and to where.

Inside our administration section we also have a <code><menu></code> tag which simply decides which name we want to put in the Components menu in the backend when the component is installed. If we do not provide this ourselves, Joomla! will simply make a name for us based on the component name.

=== Additional files ===

In order to stay in sync with the Joomla! conventions, and to not allow misconfigured web servers to allow directory listings in our component, we also need to add the following <tt>index.html</tt> file to every folder we create within our extension structure. The purpose of this file is to simply show a blank page if someone attempts to see the directory contents by using the absolute url.


'''<tt>index.html</tt>'''
<source lang="html4strict">
<!DOCTYPE html><title></title>
</source>


== Installing your extension ==

If you have used Joomla before reading this tutorial, you have noticed that extensions are installed using a compressed file containing all the things which are needed for installing and uninstalling them.

A new feature made available in Joomla! 1.6 is "discover." That means you can place the filesin the correct places inside your Joomla! installation, and the "Discover" option within the extension manager will install it, when selected.

After installlation will notice that the Hello World component is visible in the administrator site of your Joomla! installation under the Components menu.

You can test this basic component by putting index.php?option=com_helloworld or administrator/index.php?option=com_helloworld in your browser address bar.

=== Packaging an installation zip file ===

Create a compressed file of your extension directory using the structure shown in the file listing section of this page or download the provided installable package.

When you have this package, install it using the extension manager.

== File listing ==

* <tt>[[#helloworld.xml|helloworld.xml]]</tt>
* <tt>[[#site/helloworld.php|site/helloworld.php]]</tt>
* <tt>[[#index.html|site/index.html]]</tt>
* <tt>[[#index.html|admin/index.html]]</tt>
* <tt>[[#admin/helloworld.php|admin/helloworld.php]]</tt>

== Download this part ==

[http://www.leyar.com/joomlaorg/part01.zip com_helloworld-part01.zip]

== Articles in this series ==
{{:Chunks:Developing_an_MVC_Component_Contents}}

[[Category:Development]]
[[Category:Tutorials]]
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

User:Rvsjoen/tutorial/Developing an MVC Component

2011-07-10T01:46:46Z

AmyStephen: /* Model */

== Introduction ==
A software framework contains a set of application development tools for developers. Joomla has been designed for extensibility. The scope of this tutorial will be to develop a simple Hello World! component using the convention and coding standards employed by the Joomla! framework.

Joomla! is constructed using three different applications:

=== Site ===
The site application, also called frontend, is the area of your site that guests and users see. It is used for displaying content. The components of the site application live in the "components" folder in your Joomla! root.

=== Administrator ===
The administrator application, also called backend, is the administration area of your site. Where logged in managers and administrators can manage the site. The components of the administrator application live in the "administrator/components" folder in your Joomla! root.

=== Installation ===
The installation application is used once when installing Joomla! the details of this application will not be covered by this tutorial.
for installing Joomla!)

== Introduction to Model-View-Controller ==
[[image:MVC basics.png|frameless|right]]While the idea behind a component may seem extremely simple, code can quickly become very complex as additional features are added or the interface is customized.

Model-View-Controller (referred to as MVC) is a software design pattern that can be used to organize code in such a way that the business logic and data presentation are separate. The premise behind this approach is that if the business logic is grouped into one section, then the interface and user interaction that surrounds the data can be revised and customized without having to reprogram the business logic. MVC was originally developed to map the traditional input, processing, output roles into a logical GUI architecture.

These three main roles are the basis for the Joomla! MVC. They are described here in brief, but for a more thorough explanation, please refer to the links provided at the end of this tutorial. Also do not despair, this explanation is intended as a reference to the MVC pattern and the bits and pieces of it will become clearer as you progress through this tutorial, allowing you to take a step back and reconsider what is explained here, perhaps with greater clarity.

=== Model ===
The model is the part of the component that encapsulates the application's data. It will often provide routines to retrieve, manage and manipulate this data.

In our case, the model will contain methods to add, remove and update information about the greetings in the database. It will also contain methods to retrieve the list of greetings from the database.

In general, the underlying data access technique should be encapsulated in the model. In this way, if an application uses a different type of database system or if the data elements change, the model is the only element that needs to be changed, not the view or the controller.

=== View ===
The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the data. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays data retrieved from the model.

=== Controller ===
The controller is responsible for responding to user actions. In the case of a web application, a user action is (generally) a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.

=== MVC connection ===
[[image:MVC joomla.png|frameless|right]]The simplified picture on the right depicts the basic components being used within Joomla. Besides the Model, the View and the Controller, an Entry Point has been added that is depicted as a small circle. Attached to the viewer (view) a Template has been added. With these five components you should be able to understand this tutorial about making a basic Joomla! MVC component.

== Joomla! MVC Implementation ==
In Joomla!, the MVC pattern is implemented using three classes: JModel, JView and JController. For more detailed information about these classes, please refer to the API reference documentation.

== Developing the component ==

Ok, now that we have all the nitty gritty details and theory covered, let us get cracking.

This tutorial is meant to serve both as a start-to-finish tutorial, and as a simple reference and showcase on how you as a developer can use the framework to implement certain features in your component. In order to accomplish this the tutorial is divded into parts, where each part builds on the code from the previous part, allowing you to jump in at any level.

{{:Chunks:Developing_an_MVC_Component_Contents}}

[[Category:Development]]
[[Category:Tutorials]]
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

User:Rvsjoen/tutorial/Developing an MVC Component

2011-07-10T01:44:28Z

AmyStephen: /* Introduction */

== Introduction ==
A software framework contains a set of application development tools for developers. Joomla has been designed for extensibility. The scope of this tutorial will be to develop a simple Hello World! component using the convention and coding standards employed by the Joomla! framework.

Joomla! is constructed using three different applications:

=== Site ===
The site application, also called frontend, is the area of your site that guests and users see. It is used for displaying content. The components of the site application live in the "components" folder in your Joomla! root.

=== Administrator ===
The administrator application, also called backend, is the administration area of your site. Where logged in managers and administrators can manage the site. The components of the administrator application live in the "administrator/components" folder in your Joomla! root.

=== Installation ===
The installation application is used once when installing Joomla! the details of this application will not be covered by this tutorial.
for installing Joomla!)

== Introduction to Model-View-Controller ==
[[image:MVC basics.png|frameless|right]]While the idea behind a component may seem extremely simple, code can quickly become very complex as additional features are added or the interface is customized.

Model-View-Controller (referred to as MVC) is a software design pattern that can be used to organize code in such a way that the business logic and data presentation are separate. The premise behind this approach is that if the business logic is grouped into one section, then the interface and user interaction that surrounds the data can be revised and customized without having to reprogram the business logic. MVC was originally developed to map the traditional input, processing, output roles into a logical GUI architecture.

These three main roles are the basis for the Joomla! MVC. They are described here in brief, but for a more thorough explanation, please refer to the links provided at the end of this tutorial. Also do not despair, this explanation is intended as a reference to the MVC pattern and the bits and pieces of it will become clearer as you progress through this tutorial, allowing you to take a step back and reconsider what is explained here, perhaps with greater clarity.

=== Model ===
The model is the part of the component that encapsulates the application's data. It will often provide routines to manage and manipulate this data in a meaningful way in addition to routines that retrieve the data from the model. In our case, the model will contain methods to add, remove and update information about the greetings in the database. It will also contain methods to retrieve the list of greetings from the database. In general, the underlying data access technique should be encapsulated in the model. In this way, if an application is to be moved from a system that utilizes a flat file to store its information to a system that uses a database, the model is the only element that needs to be changed, not the view or the controller.

=== View ===
The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the data. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays data retrieved from the model.

=== Controller ===
The controller is responsible for responding to user actions. In the case of a web application, a user action is (generally) a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.

=== MVC connection ===
[[image:MVC joomla.png|frameless|right]]The simplified picture on the right depicts the basic components being used within Joomla. Besides the Model, the View and the Controller, an Entry Point has been added that is depicted as a small circle. Attached to the viewer (view) a Template has been added. With these five components you should be able to understand this tutorial about making a basic Joomla! MVC component.

== Joomla! MVC Implementation ==
In Joomla!, the MVC pattern is implemented using three classes: JModel, JView and JController. For more detailed information about these classes, please refer to the API reference documentation.

== Developing the component ==

Ok, now that we have all the nitty gritty details and theory covered, let us get cracking.

This tutorial is meant to serve both as a start-to-finish tutorial, and as a simple reference and showcase on how you as a developer can use the framework to implement certain features in your component. In order to accomplish this the tutorial is divded into parts, where each part builds on the code from the previous part, allowing you to jump in at any level.

{{:Chunks:Developing_an_MVC_Component_Contents}}

[[Category:Development]]
[[Category:Tutorials]]
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]

Why does the administrator logoff all of the sudden

2011-04-22T11:12:25Z

AmyStephen:

In Joomla! 1.6, the session table data column was changed from a TEXT datatype to a varchar(20480).

That is not enough storage capacity for the needs of many Components. In cases where the memory needs are exceeded, a silent error results that manifests as a logoff to users.

To fix, use a tool like phpMyAdmin to change the datatype of the data field from varchar(20480) to MEDIUMTEXT or TEXT (either is fine.)

This issue will likely not be fixed until version 1.7 due to challenges with changing the SQL Table definitions for upgrades. For now, manual changes are required.

[[Category:Version 1.6.3 FAQ]]

Why does the administrator logoff all of the sudden

2011-04-22T11:10:08Z

AmyStephen: New page: In Joomla! 1.6, the session table data column was changed from a text datatype to a varchar(20480). That is not enough storage capacity for the needs of many Components. In cases where th...

In Joomla! 1.6, the session table data column was changed from a text datatype to a varchar(20480).

That is not enough storage capacity for the needs of many Components. In cases where the memory needs are exceeded, a silent error results that manifests as a logoff to users.

To fix, use a tool like phpMyAdmin to change the datatype of the data field from varchar(20480) to MEDIUMTEXT or TEXT (either is fine.)

This issue will likely not be fixed until version 1.7 due to challenges with changing the SQL Table definitions for upgrades. For now, manual changes are required.

[[Category:Version 1.6.3 FAQ]]

J2.5:What's new in Joomla 2.5

2011-01-02T23:19:15Z

AmyStephen: /* New Events */

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page
*Ability to create alternative menu items with customised parameters
*Ability to create multiple alternative layouts for one template

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Templates Manager===
*Options - allows you to enable/disable the tp=1 feature

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeCompileHead
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepare
*onContentPrepareData
*onContentPrepareForm
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010
*Beta 15: 29 November 2010
*Release Candidate 1: 13 December 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2011-01-02T23:18:02Z

AmyStephen: Corrected Events

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page
*Ability to create alternative menu items with customised parameters
*Ability to create multiple alternative layouts for one template

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Templates Manager===
*Options - allows you to enable/disable the tp=1 feature

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeCompileHead
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentBeforeSave
*onContentAfterSave
*onContentChangeState
*onContentPrepare
*onContentPrepareData
*onContentPrepareForm
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall
*onUserBeforeSave
*onUserAfterSave
*onUserBeforeDelete
*onUserAfterDelete

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010
*Beta 15: 29 November 2010
*Release Candidate 1: 13 December 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2011-01-02T23:10:31Z

AmyStephen: Moved tp=1 feature into new Template Manager section

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page
*Ability to create alternative menu items with customised parameters
*Ability to create multiple alternative layouts for one template

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Templates Manager===
*Options - allows you to enable/disable the tp=1 feature

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeCompileHead
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010
*Beta 15: 29 November 2010
*Release Candidate 1: 13 December 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2011-01-02T22:50:28Z

AmyStephen: Moved tp enable/disable to Template Manager

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page
*Ability to create alternative menu items with customised parameters
*Ability to create multiple alternative layouts for one template

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeCompileHead
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010
*Beta 15: 29 November 2010
*Release Candidate 1: 13 December 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2011-01-02T22:40:35Z

AmyStephen: Corrected Event Name

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Debug Modules - allows you to enabled to disable the tp=1 feature
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page
*Ability to create alternative menu items with customised parameters
*Ability to create multiple alternative layouts for one template

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeCompileHead
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010
*Beta 15: 29 November 2010
*Release Candidate 1: 13 December 2010

[[Category:Joomla! 1.6]]

J1.5:Plugin/Events/System

2011-01-01T23:34:21Z

AmyStephen: add onBeforeCompileHead Event

[[Category:Development]]
[[Category:Plugins]]
===Overview===
In a standard installation of Joomla! 1.5 we have several predefined events which, when triggered, call functions in the associated plugins. For more information on plugins, check [[Tutorial:Plugins|Tutorial:Plugins]], [[Tutorial:Creating_a_Plugin_for_Joomla_1.5|Tutorial:Creating a Plugin for Joomla 1.5]], [[How_to_create_a_content_plugin|How to create a content plugin]] etc.

This topic is aimed at "global" system events, including those triggered on every page load (onAfterInitialise, onAfterRoute, onAfterDispatch, onAfterRender), those supporting search within multiple plugins (onSearch, onSearchArea) and those supporting the presentation of web services (onGetWebServices). Visit [[Tutorial:Plugins|the plugins tutorial]] for a complete list over available core events.

=== onAfterInitialise ===
'''Description'''

This event is triggered after the framework has loaded and the applicaiton initialise method has been called.

'''Parameters'''

None.

'''Return Value'''

None.

'''Called in files'''

*index.php
*administrator/index.php

===onAfterRoute===
'''Description'''

This event is triggered after the framework has loaded and initialised and the router has route the client request.

Routing is the process of examining the request environment to determine which component should receive the request. The component optional parameters are then set in the request object to be processed when the application is being dispatched.

When this event triggers the router has parsed the route and pushed the request parameters into JRequest for retrieval by the application.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* index.php
* administrator/index.php

===onAfterDispatch===
'''Description'''
This event is triggered after the framework has dispatched the application.

Dispatching is the process of pulling the option from the request object and mapping them to a component. If the component do not exist, it handles determining a default component to dispatch.

When this event is triggered the output of the component is available in the document buffer.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* index.php
* administrator/index.php

===onBeforeRender===
'''Description'''
This event is triggered immediately before the framework has rendered the application.

Rendering is the process of pushing the document buffers into the template placeholders, retrieving data from the document and pushing it into the into the JResponse buffer.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* include/application.php
* administrator/include/application.php

===onAfterRender===
'''Description'''
This event is triggered after the framework has rendered the application.

Rendering is the process of pushing the document buffers into the template placeholders, retrieving data from the document and pushing it into the into the JResponse buffer.

When this event is triggered the output of the application is available in the response buffer.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* include/application.php
* administrator/include/application.php

===onBeforeCompileHead===
'''Description'''
This event is triggered before the framework creates the Head section of the Document.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* libraries/joomla/document/html/renderer/head.php

===onSearch===
'''Description'''

This event is triggered by a variety of search related operations. It is a request for a
plugin to return the result of a search request. The rows must return the following fields, which are used in a common display routine:

* href
* title
* section
* created
* text
* browsernav

'''Parameters'''

* The target search string.
* A string matching option (exact|any|all).
* A string ordering option (newest|oldest|popular|alpha|category)
* An array if restricted to areas, null if search all.

'''Return Value'''

Array of stdClass objects with members as described above.

'''Used in files'''

* administrator/components/com_statistics/admin.statistics.php
* components/com_search/search.php
* plugins/search/categories.php
* plugins/search/contacts.php
* plugins/search/content.php
* plugins/search/newsfeeds.php
* plugins/search/sections.php
* plugins/search/weblinks.php
* plugins/xmlrpc/joomla.php

===onSearchAreas===
'''Description'''

This appears to be a request for plugins to identify which "areas" they provide
search facilities for.

'''Parameters'''

None.

'''Return Value'''

An associative array of area names, indexed by the area identifier. For example, array( 'categories' => 'Categories' ).

'''Used in files'''

* components/com_search/search.php
* plugins/search/categories.php
* plugins/search/contacts.php
* plugins/search/content.php
* plugins/search/newsfeeds.php
* plugins/search/sections.php
* plugins/search/weblinks.php

===onGetWebServices===

'''Description'''

This is an introspection request for plugins that provide web services.

'''Parameters'''

None.

'''Return Value'''

An array of associative arrays. The outer array is indexed by the service method name and
contains an array with the following elements:

* ['function'] The method to be invoked, typically a string like 'ClassName::staticMethod'
* ['docstring'] A human-readable definition of the method's purpose.
* ['signature'] An array identifying the types of the method's parameters. See the global variables $xmlrpc* for more information.

'''Used in files'''

* plugins/xmlrpc/blogger.php
* plugins/xmlrpc/joomla.php
* xmlrpc/index.php

===Example===

This is an example system plugin. Please note that because system plugins are loaded before any other event group, they may also contain any other event.

The following class would be located in the file <code>/plugins/system/example.php</code>.

<pre><?php
// no direct access
defined( '_JEXEC' ) or die( 'Restricted access' );

jimport( 'joomla.plugin.plugin' );

/**
* Example system plugin
*/
class plgSystemExample extends JPlugin
{
/**
* Constructor
*
* For php4 compatability we must not use the __constructor as a constructor for plugins
* because func_get_args ( void ) returns a copy of all passed arguments NOT references.
* This causes problems with cross-referencing necessary for the observer design pattern.
*
* @access protected
* @param object $subject The object to observe
* @param array $config An array that holds the plugin configuration
* @since 1.0
*/
function plgSystemCache( &$subject, $config )
{
parent::__construct( $subject, $config );

// Do some extra initialisation in this constructor if required
}

/**
* Do something onAfterInitialise
*/
function onAfterInitialise()
{
}

/**
* Do something onAfterRoute
*/
function onAfterRoute()
{
}

/**
* Do something onAfterDispatch
*/
function onAfterDispatch()
{
}

/**
* Do something onAfterRender
*/
function onAfterRender()
{
}
}</pre>

The following XML document would be located in the file <code>/plugins/system/example.xml</code>.

<pre><?xml version="1.0" encoding="utf-8"?>
<install version="1.5" type="plugin" group="system">
<name>System - Example</name>
<author>Author</author>
<creationDate>Month 2008</creationDate>
<copyright>Copyright (C) 2008 Holder. All rights reserved.</copyright>
<license>GNU General Public License</license>
<authorEmail>email</authorEmail>
<authorUrl>url</authorUrl>
<version>1.0.1</version>
<description>An example system plugin</description>
<files>
<filename plugin="example">example.php</filename>
</files>
<params>
<param name="example"
type="text"
default=""
label="Example"
description="An example text parameter" />
</params>
</install></pre>

J1.5:Plugin/Events/System

2011-01-01T19:42:43Z

AmyStephen: Added onBeforeRender Event

[[Category:Development]]
[[Category:Plugins]]
===Overview===
In a standard installation of Joomla! 1.5 we have several predefined events which, when triggered, call functions in the associated plugins. For more information on plugins, check [[Tutorial:Plugins|Tutorial:Plugins]], [[Tutorial:Creating_a_Plugin_for_Joomla_1.5|Tutorial:Creating a Plugin for Joomla 1.5]], [[How_to_create_a_content_plugin|How to create a content plugin]] etc.

This topic is aimed at "global" system events, including those triggered on every page load (onAfterInitialise, onAfterRoute, onAfterDispatch, onAfterRender), those supporting search within multiple plugins (onSearch, onSearchArea) and those supporting the presentation of web services (onGetWebServices). Visit [[Tutorial:Plugins|the plugins tutorial]] for a complete list over available core events.

=== onAfterInitialise ===
'''Description'''

This event is triggered after the framework has loaded and the applicaiton initialise method has been called.

'''Parameters'''

None.

'''Return Value'''

None.

'''Called in files'''

*index.php
*administrator/index.php

===onAfterRoute===
'''Description'''

This event is triggered after the framework has loaded and initialised and the router has route the client request.

Routing is the process of examining the request environment to determine which component should receive the request. The component optional parameters are then set in the request object to be processed when the application is being dispatched.

When this event triggers the router has parsed the route and pushed the request parameters into JRequest for retrieval by the application.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* index.php
* administrator/index.php

===onAfterDispatch===
'''Description'''
This event is triggered after the framework has dispatched the application.

Dispatching is the process of pulling the option from the request object and mapping them to a component. If the component do not exist, it handles determining a default component to dispatch.

When this event is triggered the output of the component is available in the document buffer.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* index.php
* administrator/index.php

===onBeforeRender===
'''Description'''
This event is triggered immediately before the framework has rendered the application.

Rendering is the process of pushing the document buffers into the template placeholders, retrieving data from the document and pushing it into the into the JResponse buffer.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* include/application.php
* administrator/include/application.php

===onAfterRender===
'''Description'''
This event is triggered after the framework has rendered the application.

Rendering is the process of pushing the document buffers into the template placeholders, retrieving data from the document and pushing it into the into the JResponse buffer.

When this event is triggered the output of the application is available in the response buffer.

'''Parameters'''

None.

'''Return Value'''

None.

'''Used in files'''

* include/application.php
* administrator/include/application.php

===onSearch===
'''Description'''

This event is triggered by a variety of search related operations. It is a request for a
plugin to return the result of a search request. The rows must return the following fields, which are used in a common display routine:

* href
* title
* section
* created
* text
* browsernav

'''Parameters'''

* The target search string.
* A string matching option (exact|any|all).
* A string ordering option (newest|oldest|popular|alpha|category)
* An array if restricted to areas, null if search all.

'''Return Value'''

Array of stdClass objects with members as described above.

'''Used in files'''

* administrator/components/com_statistics/admin.statistics.php
* components/com_search/search.php
* plugins/search/categories.php
* plugins/search/contacts.php
* plugins/search/content.php
* plugins/search/newsfeeds.php
* plugins/search/sections.php
* plugins/search/weblinks.php
* plugins/xmlrpc/joomla.php

===onSearchAreas===
'''Description'''

This appears to be a request for plugins to identify which "areas" they provide
search facilities for.

'''Parameters'''

None.

'''Return Value'''

An associative array of area names, indexed by the area identifier. For example, array( 'categories' => 'Categories' ).

'''Used in files'''

* components/com_search/search.php
* plugins/search/categories.php
* plugins/search/contacts.php
* plugins/search/content.php
* plugins/search/newsfeeds.php
* plugins/search/sections.php
* plugins/search/weblinks.php

===onGetWebServices===

'''Description'''

This is an introspection request for plugins that provide web services.

'''Parameters'''

None.

'''Return Value'''

An array of associative arrays. The outer array is indexed by the service method name and
contains an array with the following elements:

* ['function'] The method to be invoked, typically a string like 'ClassName::staticMethod'
* ['docstring'] A human-readable definition of the method's purpose.
* ['signature'] An array identifying the types of the method's parameters. See the global variables $xmlrpc* for more information.

'''Used in files'''

* plugins/xmlrpc/blogger.php
* plugins/xmlrpc/joomla.php
* xmlrpc/index.php

===Example===

This is an example system plugin. Please note that because system plugins are loaded before any other event group, they may also contain any other event.

The following class would be located in the file <code>/plugins/system/example.php</code>.

<pre><?php
// no direct access
defined( '_JEXEC' ) or die( 'Restricted access' );

jimport( 'joomla.plugin.plugin' );

/**
* Example system plugin
*/
class plgSystemExample extends JPlugin
{
/**
* Constructor
*
* For php4 compatability we must not use the __constructor as a constructor for plugins
* because func_get_args ( void ) returns a copy of all passed arguments NOT references.
* This causes problems with cross-referencing necessary for the observer design pattern.
*
* @access protected
* @param object $subject The object to observe
* @param array $config An array that holds the plugin configuration
* @since 1.0
*/
function plgSystemCache( &$subject, $config )
{
parent::__construct( $subject, $config );

// Do some extra initialisation in this constructor if required
}

/**
* Do something onAfterInitialise
*/
function onAfterInitialise()
{
}

/**
* Do something onAfterRoute
*/
function onAfterRoute()
{
}

/**
* Do something onAfterDispatch
*/
function onAfterDispatch()
{
}

/**
* Do something onAfterRender
*/
function onAfterRender()
{
}
}</pre>

The following XML document would be located in the file <code>/plugins/system/example.xml</code>.

<pre><?xml version="1.0" encoding="utf-8"?>
<install version="1.5" type="plugin" group="system">
<name>System - Example</name>
<author>Author</author>
<creationDate>Month 2008</creationDate>
<copyright>Copyright (C) 2008 Holder. All rights reserved.</copyright>
<license>GNU General Public License</license>
<authorEmail>email</authorEmail>
<authorUrl>url</authorUrl>
<version>1.0.1</version>
<description>An example system plugin</description>
<files>
<filename plugin="example">example.php</filename>
</files>
<params>
<param name="example"
type="text"
default=""
label="Example"
description="An example text parameter" />
</params>
</install></pre>

GHOP students 2007-2008

2010-10-30T01:55:45Z

AmyStephen: /* Kevin Hayne (Kevin8020) */

== [[GHOP students/Anner J. Bonilla|Anner J. Bonilla]] (annerajb) ==
{{:GHOP students/Anner J. Bonilla}}{{-}}

== [[GHOP students/Andreas Lance Freund|Andreas Lance Freund]] ==
{{:GHOP students/Andreas Lance Freund}}{{-}}

== [[GHOP students/Anthony Vérez|Anthony Vérez]] (netantho) ==
{{:GHOP students/Anthony Vérez}}{{-}}

== [[GHOP students/Benjamin Hättasch|Benjamin Hättasch]]==
{{:GHOP students/Benjamin Hättasch}}{{-}}

== [[GHOP students/Branko Pajic|Branko Pajic]] (balvanboy) ==
{{:GHOP students/Branko Pajic}}{{-}}

== [[GHOP students/Chad Windnagle|Chad Windnagle]] (drmmr763) ==
{{:GHOP students/Chad Windnagle}}{{-}}

== [[GHOP students/Chit Sabesh Asokan|Chit Sabesh Asokan]] (chitsabesh) ==
{{:GHOP students/Chit Sabesh Asokan}}{{-}}

== [[GHOP students/James William Ramsay|James William Ramsay]] (J. Ramsay) ==
{{:GHOP students/James William Ramsay}}{{-}}

== [[GHOP students/Justo de Rivera|Justo de Rivera]] (justo.deRivera) ==
{{:GHOP students/Justo de Rivera}}{{-}}

== [[GHOP students/Kevin Hayne|Kevin Hayne]] (Kevin8020) ==
{{:GHOP students/Kevin Hayne}}{{-}}

== [[GHOP students/Marieke van der Tuin|Marieke van der Tuin]] (Marieke92) ==
{{:GHOP students/Marieke van der Tuin}}{{-}}

== [[GHOP students/Martin Pecka|Martin Pecka]] (peci1) ==
{{:GHOP students/Martin Pecka}}{{-}}

== [[GHOP students/Max Shinn|Max Shinn]] (trombonechamp) ==
{{:GHOP students/Max Shinn}}{{-}}

== [[GHOP students/Maximiliano David Bustos|Maximiliano David Bustos]] (Maxi) ==
{{:GHOP students/Maximiliano David Bustos}}{{-}}

== [[GHOP students/Michael Casha|Michael Casha]] (MiCCAS) ==
{{:GHOP students/Michael Casha}}{{-}}

== [[GHOP students/Miloš Bovan|Miloš Bovan]] (fantastic) ==
{{:GHOP students/Miloš Bovan}}{{-}}

== [[GHOP students/Miłosz Lewandowski|Miłosz Lewandowski]] (milosz.lewandowski) ==
{{:GHOP students/Miłosz Lewandowski}}{{-}}

== [[GHOP students/Ming-Ting Wei|Ming-Ting Wei]] "魏藥" (medicalwei) ==
{{:GHOP students/Ming-Ting Wei}}{{-}}

== [[GHOP students/Shantanu Bala|Shantanu Bala]] (shantanubala) ==
{{:GHOP students/Shantanu Bala}}{{-}}

== [[GHOP students/Thomas Gummerer|Thomas Gummerer]] (littlegeniuz) ==
{{:GHOP students/Thomas Gummerer}}{{-}}

== [[GHOP students/Tomasz Dobrzyński|Tomasz Dobrzyński]] (depresz) ==
{{:GHOP students/Tomasz Dobrzyński}}{{-}}

== [[GHOP students/Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna|Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna]] (Hashani) ==
{{:GHOP students/Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna}}{{-}}

== [[GHOP students/Witchakorn Kamolpornwijit|Witchakorn Kamolpornwijit]] (Chalet16) ==
{{:GHOP students/Witchakorn Kamolpornwijit}}{{-}}

== [[GHOP students/Yavor Sashov Georgiev|Yavor Sashov Georgiev]] (fealebenpae) ==
{{:GHOP students/Yavor Sashov Georgiev}}{{-}}

== [[GHOP students/Zach Kanzler|Zach Kanzler]] (theY4Kman) ==
{{:GHOP students/Zach Kanzler}}{{-}}

[[Category:GHOP]]

GHOP students 2007-2008/Kevin Hayne

2010-10-30T01:55:13Z

AmyStephen:

[[Image:kevin8020.jpg|thumb|Kevin Hayne (Kevin8020)]]

I'm from the USA - Denver, Colorado... and I love it. I've had an interest in computers since the Myst series entered in our home. My love for technology has stemmed from that experience. I started working with website for fun when I was 11, and haven't looked back since. Discovering Mambo back four years ago was my introduction into PHP and I started learning the joys of working with it. After seeing Joomla! appear, I was taken with the core team's plans, and jumped over here. I spent a few years with zoom gallery before it's demise, and a few with Joomla!hacks working on their bridge for SMF. Now, I do the occasional Joomla! contract project for corePHP but not much.

Seeing GHOP was like a dream come true - finally a way JUST for high school students to contribute to this amazing project. Being able to work with Joomla! and contribute small things that will make a difference in the project has been a great experience, and one that I have really enjoyed. The volunteer staff was great - especially Amy who got me through all of my tasks and helped me when I got stuck plenty of times. I hope I get the chance to participate next year too. If I were to do anything differently, it would be to get more people staffing the event. While I felt well attended too, I had to occasionally bump my own topic to get attention. Other than that - I think it was great! The only concert I have is that if people get too ambitious next year, there won't be a chance for any of us to grab more than one task... haha!

Outside of web coding and Joomla! stuff, I love music - which has resulted in my being able to work with bands in the area (as a web guy of course). I also play guitar, enjoy working with sound systems, and love to hike in the Colorado Rockies. Speaking of the Colorado Rockies... how about that baseball team, eh?
{{-}}

[http://community.joomla.org/blogs/community/1323-onwards-the-story-of-kevin-hayne.html Onwards - The story of Kevin Hayne]

GHOP students 2007-2008

2010-10-30T01:54:24Z

AmyStephen: /* Kevin Hayne (Kevin8020) */

== [[GHOP students/Anner J. Bonilla|Anner J. Bonilla]] (annerajb) ==
{{:GHOP students/Anner J. Bonilla}}{{-}}

== [[GHOP students/Andreas Lance Freund|Andreas Lance Freund]] ==
{{:GHOP students/Andreas Lance Freund}}{{-}}

== [[GHOP students/Anthony Vérez|Anthony Vérez]] (netantho) ==
{{:GHOP students/Anthony Vérez}}{{-}}

== [[GHOP students/Benjamin Hättasch|Benjamin Hättasch]]==
{{:GHOP students/Benjamin Hättasch}}{{-}}

== [[GHOP students/Branko Pajic|Branko Pajic]] (balvanboy) ==
{{:GHOP students/Branko Pajic}}{{-}}

== [[GHOP students/Chad Windnagle|Chad Windnagle]] (drmmr763) ==
{{:GHOP students/Chad Windnagle}}{{-}}

== [[GHOP students/Chit Sabesh Asokan|Chit Sabesh Asokan]] (chitsabesh) ==
{{:GHOP students/Chit Sabesh Asokan}}{{-}}

== [[GHOP students/James William Ramsay|James William Ramsay]] (J. Ramsay) ==
{{:GHOP students/James William Ramsay}}{{-}}

== [[GHOP students/Justo de Rivera|Justo de Rivera]] (justo.deRivera) ==
{{:GHOP students/Justo de Rivera}}{{-}}

== [[GHOP students/Kevin Hayne|Kevin Hayne]] (Kevin8020) ==
{{:GHOP students/Kevin Hayne}}{{-}}
[http://community.joomla.org/blogs/community/1323-onwards-the-story-of-kevin-hayne.html Onwards - The story of Kevin Hayne]

== [[GHOP students/Marieke van der Tuin|Marieke van der Tuin]] (Marieke92) ==
{{:GHOP students/Marieke van der Tuin}}{{-}}

== [[GHOP students/Martin Pecka|Martin Pecka]] (peci1) ==
{{:GHOP students/Martin Pecka}}{{-}}

== [[GHOP students/Max Shinn|Max Shinn]] (trombonechamp) ==
{{:GHOP students/Max Shinn}}{{-}}

== [[GHOP students/Maximiliano David Bustos|Maximiliano David Bustos]] (Maxi) ==
{{:GHOP students/Maximiliano David Bustos}}{{-}}

== [[GHOP students/Michael Casha|Michael Casha]] (MiCCAS) ==
{{:GHOP students/Michael Casha}}{{-}}

== [[GHOP students/Miloš Bovan|Miloš Bovan]] (fantastic) ==
{{:GHOP students/Miloš Bovan}}{{-}}

== [[GHOP students/Miłosz Lewandowski|Miłosz Lewandowski]] (milosz.lewandowski) ==
{{:GHOP students/Miłosz Lewandowski}}{{-}}

== [[GHOP students/Ming-Ting Wei|Ming-Ting Wei]] "魏藥" (medicalwei) ==
{{:GHOP students/Ming-Ting Wei}}{{-}}

== [[GHOP students/Shantanu Bala|Shantanu Bala]] (shantanubala) ==
{{:GHOP students/Shantanu Bala}}{{-}}

== [[GHOP students/Thomas Gummerer|Thomas Gummerer]] (littlegeniuz) ==
{{:GHOP students/Thomas Gummerer}}{{-}}

== [[GHOP students/Tomasz Dobrzyński|Tomasz Dobrzyński]] (depresz) ==
{{:GHOP students/Tomasz Dobrzyński}}{{-}}

== [[GHOP students/Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna|Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna]] (Hashani) ==
{{:GHOP students/Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna}}{{-}}

== [[GHOP students/Witchakorn Kamolpornwijit|Witchakorn Kamolpornwijit]] (Chalet16) ==
{{:GHOP students/Witchakorn Kamolpornwijit}}{{-}}

== [[GHOP students/Yavor Sashov Georgiev|Yavor Sashov Georgiev]] (fealebenpae) ==
{{:GHOP students/Yavor Sashov Georgiev}}{{-}}

== [[GHOP students/Zach Kanzler|Zach Kanzler]] (theY4Kman) ==
{{:GHOP students/Zach Kanzler}}{{-}}

[[Category:GHOP]]

GHOP students 2007-2008

2010-10-30T01:54:02Z

AmyStephen: /* Kevin Hayne (Kevin8020) */

== [[GHOP students/Anner J. Bonilla|Anner J. Bonilla]] (annerajb) ==
{{:GHOP students/Anner J. Bonilla}}{{-}}

== [[GHOP students/Andreas Lance Freund|Andreas Lance Freund]] ==
{{:GHOP students/Andreas Lance Freund}}{{-}}

== [[GHOP students/Anthony Vérez|Anthony Vérez]] (netantho) ==
{{:GHOP students/Anthony Vérez}}{{-}}

== [[GHOP students/Benjamin Hättasch|Benjamin Hättasch]]==
{{:GHOP students/Benjamin Hättasch}}{{-}}

== [[GHOP students/Branko Pajic|Branko Pajic]] (balvanboy) ==
{{:GHOP students/Branko Pajic}}{{-}}

== [[GHOP students/Chad Windnagle|Chad Windnagle]] (drmmr763) ==
{{:GHOP students/Chad Windnagle}}{{-}}

== [[GHOP students/Chit Sabesh Asokan|Chit Sabesh Asokan]] (chitsabesh) ==
{{:GHOP students/Chit Sabesh Asokan}}{{-}}

== [[GHOP students/James William Ramsay|James William Ramsay]] (J. Ramsay) ==
{{:GHOP students/James William Ramsay}}{{-}}

== [[GHOP students/Justo de Rivera|Justo de Rivera]] (justo.deRivera) ==
{{:GHOP students/Justo de Rivera}}{{-}}

== [[GHOP students/Kevin Hayne|Kevin Hayne]] (Kevin8020) ==
{{:GHOP students/Kevin Hayne}}{{-}}
[Onwards - The story of Kevin Hayne http://community.joomla.org/blogs/community/1323-onwards-the-story-of-kevin-hayne.html]

== [[GHOP students/Marieke van der Tuin|Marieke van der Tuin]] (Marieke92) ==
{{:GHOP students/Marieke van der Tuin}}{{-}}

== [[GHOP students/Martin Pecka|Martin Pecka]] (peci1) ==
{{:GHOP students/Martin Pecka}}{{-}}

== [[GHOP students/Max Shinn|Max Shinn]] (trombonechamp) ==
{{:GHOP students/Max Shinn}}{{-}}

== [[GHOP students/Maximiliano David Bustos|Maximiliano David Bustos]] (Maxi) ==
{{:GHOP students/Maximiliano David Bustos}}{{-}}

== [[GHOP students/Michael Casha|Michael Casha]] (MiCCAS) ==
{{:GHOP students/Michael Casha}}{{-}}

== [[GHOP students/Miloš Bovan|Miloš Bovan]] (fantastic) ==
{{:GHOP students/Miloš Bovan}}{{-}}

== [[GHOP students/Miłosz Lewandowski|Miłosz Lewandowski]] (milosz.lewandowski) ==
{{:GHOP students/Miłosz Lewandowski}}{{-}}

== [[GHOP students/Ming-Ting Wei|Ming-Ting Wei]] "魏藥" (medicalwei) ==
{{:GHOP students/Ming-Ting Wei}}{{-}}

== [[GHOP students/Shantanu Bala|Shantanu Bala]] (shantanubala) ==
{{:GHOP students/Shantanu Bala}}{{-}}

== [[GHOP students/Thomas Gummerer|Thomas Gummerer]] (littlegeniuz) ==
{{:GHOP students/Thomas Gummerer}}{{-}}

== [[GHOP students/Tomasz Dobrzyński|Tomasz Dobrzyński]] (depresz) ==
{{:GHOP students/Tomasz Dobrzyński}}{{-}}

== [[GHOP students/Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna|Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna]] (Hashani) ==
{{:GHOP students/Wickrama Arachchi Vithanage Hashani Maduwanthi Weerarathna}}{{-}}

== [[GHOP students/Witchakorn Kamolpornwijit|Witchakorn Kamolpornwijit]] (Chalet16) ==
{{:GHOP students/Witchakorn Kamolpornwijit}}{{-}}

== [[GHOP students/Yavor Sashov Georgiev|Yavor Sashov Georgiev]] (fealebenpae) ==
{{:GHOP students/Yavor Sashov Georgiev}}{{-}}

== [[GHOP students/Zach Kanzler|Zach Kanzler]] (theY4Kman) ==
{{:GHOP students/Zach Kanzler}}{{-}}

[[Category:GHOP]]

Archived:GCI 2010-11

2010-10-29T23:39:19Z

AmyStephen: /* Introduction */

== Google Code-in 2010-2011 ==

=== Introduction ===

[http://code.google.com/gci Google Code-in] (GCI) is a contest for pre-university (13-18 year old) students, that aims at helping students get involved in Open Source projects.

[http://code.google.com/opensource/gci/2010-11/faqs.html Google Code-in Frequently Asked Questions]

This list is a work in progress. The final listing for each task that is offered to students must include:

# A specific work product, whether a piece of code, a written report, a piece of writing, a website or an image.
# Evaluation criteria which will be used for determining whether the task has been successfully completed.
# A list of any resources that would be useful for the student doing the project. These will usually be links to information but could something else.
# A difficulty rating (we are using challenging, intermediate, basic).

=== Proposed Tasks ===

==== Code ====

Tasks related to writing or refactoring code

====== Challenging ======
# Add the ability for the Mass Mail feature in Joomla 1.6 to be able to send HTML messages.
# Add a batch update facility to the Joomla 1.6 user manager to be able to batch add, remove or set the user groups for users in a list.
# Create a bulk import utility for the Joomla! user manager to create from a csv file and optionally notify users of their account details via email.
# Create a plugin to allow users to delete their accounts.
# Create a new component syndicate a combined feed from two separate components.
# Create a new document type: vcalendar.
# Create a new document type: ical.
# Create a new document type: rdf.
# Create a new document type: hcard.
# Create a new document type: csv.
# Create a new document type: vcard.
# Implement frontend editing for com_contact.
# Implement frontend editing for com_newsfeeds.
# Implement a method for Apply in the front end for com_content or com_weblinks.
# Create a component that would allow a backend user to change his or her password and other account settings in the backend without having access to the com_users user interface.
# Create a Debian package for Joomla! 1.6. Document the process.
# Create a Debian package for the Joomla! Framework. Document the process.
# Create a RPM package for Joomla! 1.6. Document the process.
Resources: http://en.wikipedia.org/wiki/RPM_Package_Manager
http://www.rpm.org/
# Create a RPM package for Joomla! 1.6. Document the process.
Resources: http://en.wikipedia.org/wiki/RPM_Package_Manager
http://www.rpm.org/

====== Intermediate ======

#Create a custom document type to download vcard information in RDF format.
#Create a Google Map user plugin for display based on address information in com_contact.
#Create a plugin that stores information from specific fields in a profile plugin in the jos_contact_details table
#Create a plugin that parses actions from Mosets Tree and stores them in Scout (directory monitoring)
#Create an administrator module for quick article create that could replace Quick Icons.

====== Basic ======
#Create a module to display a list of contacts in a category
#Create a module to display a list of newsfeeds in a category.
#Create user plugin to display a Twitter feed.
#Create a user plugin to display a Facebook feed.

==== Documentation ====

====== Challenging ======
#Document a complete class of the Joomla! Framework including appropriate code examples from the Joomla! core or elsewhere. (This task can be repeated for each framework class).
#Create a document describing the observer design pattern and how it is implemented in Joomla! plugins.
#Consult with the Joomla! development community and draft proposed code style standards for XML.

====== Intermediate ======
#Document the use of alternative component layouts and provide a detailed commented example for each of the core components.
#Document the use of alternative module layouts and provide detailed commented examples for at least 5 core modules.
#Document how to create a custom document type, using a core component as an example (document types might be rdf, csv, hcard, ical, hcal etc).

====== Basic ======

For each of these create a page in docs.joomla.org
# Describe the way view access levels can be expanded in Joomla 1.6 and how a site owner would use them to control the visible access to site content.
# Describe the meanings of the core permissions in Joomla 1.6 and the four levels over which they can be applied.
# Describe the Global Level of permissions in Joomla 1.6 and how a site owner might use them to broadly control site access.
# Describe the Component Level of permissions in Joomla 1.6 and how a site owner can restrict users in groups to certain components.
# Describe the Category Level permissions in Joomla 1.6 and how a site owner can restrict content providers to create, edit and delete content in those categories.
# Describe the Article Level permissions in Joomla 1.6 and how a site owner can restrict content providers to edit and delete their articles.
# Describe how site owners can use the Edit Own permission effectively in Joomla 1.6.
# Describe how a template designer can create a template parameter to for the site owner to include their Google Analytics code in the template automatically.
# Describe how to restore the default ACL settings.

==== Outreach ====

====== Challenging ======

# Do a presentation for a local club, school or group on how to create a Joomla! Website. Write a brief report about the experience. (Can be done by several people)
# Create a Joomla! website for a non profit organization. Write a report about the experience. (Can be done by several people)
# Create a survey of third party developers to learn how closely they follow Joomla! core development and what forms of communication about core development they would find most useful.
# Organize an Install Fest where a group of students in your school can install and start creating a Joomla! website.

====== Intermediate ======

# Translate the Evaluators Persona (http://docs.joomla.org/Evaluators) into a language other than English.
# Write an article for the Joomla! Community Magazine
# Write an article about Joomla! or the Joomla! Project for your school newspaper or a local newspaper.
# Meet with the team working on the redesign of joomla.org and write an article about the current status. (Can be repeated every 2 weeks)
# Staff or help staff a Joomla! table or booth at a local IT Expo or event (To do this you must submit information about the specific event before hand and write a short report about it afterwards.)

====== Basic ======

# Create a standard "Download Joomla!" module that Joomla! fans can use on their sites.
# Create list of online media outlets for distribution of Joomla! announcements
# Create a document on ways to leverage participation in the Joomla! Project to promote your Joomla! Business (ideas like putting a link in your forum signature, listing on the Resources Directory and so on).
# Create contributing author badge for the Joomla! Community Magazine
# Update Author Resources content for the Joomla! Community Magazine
# Create a powerpoint presentation (or similar) on the new user features in Joomla 1.6 that could be used at conference presentations (including good slide notes).
# Create an information PDF about how to run a Joomla Day, how to register the event with Joomla, and include links to key and useful resources.
# Create an information PDF about how to set up a Joomla User Group in your area, how to register the group with Joomla, and include links to key and useful resources.

==== Quality Assurance ====

Tasks related to testing and ensuring code is of high quality

====== Challenging ======
# Write a PHPUnit test for a package or sub-package in the Joomla Libraries.(multiple opportunities exist for this task).
# Write a Selenium System test to cover a unit of the CMS functionality.(multiple opportunities exist for this task).

====== Intermediate ======
# Take a package or sub-package from the Joomla Libraries and ensure that the code formatting complies with our standards, and make corrections as appropriate (multiple opportunities exist for this task).

====== Basic ======

#Review 24 hours of posts in the New to Joomla! forums and report on the most common problems reported.
#Review 24 hours of posts in the Administration forums and report on the most common problems reported.

==== Research ====

Tasks related to studying a problem and recommending solutions

====== Challenging ======

# Research how to read/write video metadata in MP4 and webm containers. Write a report summarizing what you learn for the development team.
# Research the best server side tools/methods to transcode video from various formats to those MP4 and webm containers including various compression schemes and settings for different screen formats (for Example transcoding to an iOS device like iPhone/Pod/Pad vs the full TV experience. Write a report summarizing what you learn for the development team.
# Research various online resources for video metadata along with the strengths and weaknesses of their API's, access rules and licensing restrictions. Write a report summarizing what you learn for the development team.
# Research what it would take to start using PHAR packages for distributing the framework
(See http://www.php.net/manual/en/intro.phar.php). Write a report for the development team.

# Review the W3C Authoring Tool Accessibility Guidelines (ATAG) 1.0 checkpoints and document where Joomla! does and does not meet them.
# Review the W3C Authoring Tool Accessibility Guidelines 2.0 (http://www.w3.org/TR/ATAG20/) and write a report on what would be needed for Joomla! 1.7 to meet them.

====== Intermediate ======

# With Joomla's Google Analytics data, analyse the data for the past six months and make comments about how people are using www.joomla.org (entry points, exist points, etc).

====== Basic ======

# Analyze usage statistics for Joomla! Community Magazine and recommend changes to increase traffic
# Write a report on how you would improve one of the www.joomla.org sites to make it easier for people who don't know anything about Joomla to find information.

==== Training ====

Tasks related to helping others learn more

====== Challenging ======

# Suppose a teacher in your school was going to spend a month teaching his or her students to use Joomla! to make a website. Interview a teacher in your school about what resources would be useful for that and create a resource portal of links and materials on docs.joomla.org.
# Suppose a teacher in your school was going to spend a month teaching his or her students to develop a simple Joomla! component. Interview a teacher in your school about what resources would be useful for that and create a resource portal of links and materials on docs.joomla.org.
# Suppose a teacher in your school was going to spend a month teaching his or her students to create a Joomla! template. Interview a teacher in your school (this might be an art teacher) about what resources would be useful for that and create a resource portal of links and materials on docs.joomla.org.

====== Intermediate ======

# Create a guide to Joomla! resources, documents and sites for someone who has "inherited" a Joomla! site from somebody else and has never used Joomla! before. Create a persona for this profile in docs.joomla.org and link all resources to the persona page.

====== Basic ======
# Create a "HTML Basics" document aimed at someone who has a Joomla! site but has only used a WYSIWYG editor.
# Create a "CSS Basics" document aimed at someone with no web background.

==== Translation ====

Tasks related to localization

(Multiple opportunities exist for each of these but may be limited by the availability of mentors in a specific language. Limit of one instance of each task per distinct language.)

====== Challenging ======
# For a language that does not have an accredited translation team, begin the process of organizing a team. Completion of this task will involve contacting the translation coordinators, using resources such as local JUGs and the Joomla! Forums and People site to find collaborators, learning to use com_localise, and beginning the translation process.
# For a language that does not have an accredited translation team, provide a translation of core strings.

====== Intermediate ======
# Translate the Absolute Beginner's Guide (http://docs.joomla.org/Beginners) into a language besides English.
# Translate the documentation on creating translations and becoming an accredited translation team into a language besides English.
# Translate the security documentation into a language other than English. (http://docs.joomla.org/Security)

====== Basic ======
# Provide an accredited translation team with translation of sample data.
# Provide an accredited translation team with the translation of the help screens for one complete component.
# Provide an accredited translation team with translation of 100 strings.

==== User Interface ====

Tasks related to user experience research or user interface design and interaction

====== Challenging ======

# Card sorting studies are a basic approach to usability testing (http://www.deyalexander.com.au/resources/uxd/card-sorting.html ). Research card sorting and design a set of cards that could be used for analyzing usability in the Joomla! Administrator. Have at least one user try the card sorting task. Document your work and the results of the test case so that others know how to use the cards to test usability.
# Card sorting studies are a basic approach to usability testing (http://www.deyalexander.com.au/resources/uxd/card-sorting.html). Research card sorting and design a set of cards that could be used for analyzing usability of the docs.joomla.org. Have at least one user try the card sorting task. Document your work and the results of the test case so that others know how to use the cards to test usability.

# Think out loud studies are another basic type of usability research (http://en.wikipedia.org/wiki/Think_aloud_protocol). For the following tasks create and document a think out loud procedure and carry out a test with at least 3 users: Creating an article in the administrator.
# Think out loud studies are another basic type of usability research (http://en.wikipedia.org/wiki/Think_aloud_protocol). For the following tasks create and document a think out loud procedure and carry out a test with at least 3 users: Installing an extension.
# Think out loud studies are another basic type of usability research (http://en.wikipedia.org/wiki/Think_aloud_protocol). For the following tasks create and document a think out loud procedure and carry out a test with at least 3 users: Updating Joomla!.
# Think out loud studies are another basic type of usability research (http://en.wikipedia.org/wiki/Think_aloud_protocol). For the following tasks create and document a think out loud procedure and carry out a test with at least 3 users: Creating a menu item.
# Think out loud studies are another basic type of usability research (http://en.wikipedia.org/wiki/Think_aloud_protocol). For the following tasks and document a think out loud procedure for it and carry out a test with at least 3 users: Configuring permissions to achieve a specific goal.
# Think out loud studies are another basic type of usability research (http://en.wikipedia.org/wiki/Think_aloud_protocol). For the following tasks and document a think out loud procedure for it and carry out a test with at least 3 users: Creating an new action permissions user group.

====== Intermediate ======

# Create a document about techniques for usability testing for developers.
# Check a standard installation of Joomla with the default template against a colour-blind checking site, then install a freely available template and do the same. Report any interesting results.

====== Basic ======

# Check a standard installation of Joomla 1.6 against a HTML and CSS validation site. Report back any errors that you find.
# Identify 10 common tasks in the Joomla! administrator and record step by step the number of clicks it takes to completion.

[[Category:GCI]]

J2.5:What's new in Joomla 2.5

2010-09-15T12:39:07Z

AmyStephen: /* Archived Articles */

Lots of things.

...and:
* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

...and:

==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Debug Modules - allows you to enabled to disable the tp=1 feature
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to a Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
*** Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareFormData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.2/1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Still Mootools 1.2. Will be upgrading to 1.3 during the beta process.
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 1: 18 May 2010
*Beta 2: 31 May 2010
*Beta 3: 14 June 2010
*Beta 4: 28 June 2010
*Beta 5: 12 July 2010
*Beta 6: 26 July 2010
*Beta 7: 09 August 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2010-09-15T12:36:52Z

AmyStephen: /* Archived Articles */

Lots of things.

...and:
* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

...and:

==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Debug Modules - allows you to enabled to disable the tp=1 feature
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to a Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before they could be updated.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
*** Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareFormData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.2/1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Still Mootools 1.2. Will be upgrading to 1.3 during the beta process.
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 1: 18 May 2010
*Beta 2: 31 May 2010
*Beta 3: 14 June 2010
*Beta 4: 28 June 2010
*Beta 5: 12 July 2010
*Beta 6: 26 July 2010
*Beta 7: 09 August 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2010-09-15T12:35:34Z

AmyStephen: /* Articles Manager */

Lots of things.

...and:
* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

...and:

==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Debug Modules - allows you to enabled to disable the tp=1 feature
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to a Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before they could be updated. In 1.6, an Article with an Archived Status can be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
*** Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareFormData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.2/1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Still Mootools 1.2. Will be upgrading to 1.3 during the beta process.
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 1: 18 May 2010
*Beta 2: 31 May 2010
*Beta 3: 14 June 2010
*Beta 4: 28 June 2010
*Beta 5: 12 July 2010
*Beta 6: 26 July 2010
*Beta 7: 09 August 2010

[[Category:Joomla! 1.6]]

Archived:Joomla! 1.6 Development Status

2010-07-23T14:27:52Z

AmyStephen:

Please see [http://www.joomla.org/component/content/article/5252.html Joomla! 1.6 General Status] for the latest information or review the [http://www.joomla.org/announcements/release-news.html Release News] for the latest release and a link to the downloads.

'''Note: This page is outdated.'''

{| class="wikitable" style="font-size: 95%; padding:4px; width: auto;"
!'''Task'''
!'''Blocker'''
!'''Status'''
!'''Contact person'''
!'''Description'''
|-
|Implement JForm library
|Alpha
|100%
|Rob Schley, Andrew Eddie
|This library allows to create forms from XML definition files. See the introduction at http://tinyurl.com/psj6c6
|-
|Implement new event triggers
|Alpha
|60%
|
|onBeforeRender, triggers in JForm, onContentDisplay etc.
|-
|Implement new controller dispatcher
|Alpha
|100%
|
|See the discussion at http://tinyurl.com/qlh5bg where Louis explained how this works in 1.6. See related article in wiki here: [[Xml-rpc changes in Joomla! 1.6]].
|-
|Upgrade to Mootools 1.2
|Alpha
|100%
|Louis Landry, Ercan Özkaya
|
|-
|Javascript translation
|Alpha
|100%
|
|This is implemented and finished. Take a look at JOpenID Javascript class and mod_login for details
|-
|New extension updater work
|Alpha
|100%
|Samuel Moffatt
|New extension updater is implemented, but not finished yet.
|-
|Conversion of INI to JSON
|Alpha
|100%
|
|We now use JSON format for storing parameters in the database. This is completed for core components.
|-
|Nested categories
|Alpha
|90%
|Hannes Papenberg
|
|-
|Access control list (ACL)
|Alpha
|80%
|Hannes Papenberg, Louis Landry
|
|-
|User management system
|Alpha
|75%
|
|The new com_members needs to be proof checked.
|-
|Documenting the triggers, finishing them
|
|10%
|Louis Landry, Rob Schley, Andrew Eddie
|The triggers for JForm need to be implemented in the respective extension, which has not happened yet. We need a plan for this one.
|-
|MVCing backend components
|
|90%
|
|Most of the back-end components have MVC file structure, but they are not fully MVC yet
|-
|Parameters for templates in the database
|
|100%
|Hannes Papenberg
|Especially the UI will take a lot of work, we might have to change the database for this one.
|-
|Add template parameter set to menu item creation
|
|10%
|Hannes Papenberg
|
|-
|Refactoring parameters
|
|80%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
|Comments system
|
|80%
|Louis Landry, Andrew Eddie, Rob Schley
|It will be donated by JXtended and will be added to trunk somewhere in the beta phase.
|-
|Hooks for external authentication systems
|
|0%
|
|Need to be implemented in JUser and in the code where Usergroups are managed. Maybe we need a JUsergroupclass
|-
|Database driven install log
|
|0%
|Samuel Moffatt
|
|-
|Convert all layouts to semantic and XHTML strict
|
|0%
|Ron Severdia
|There are some efforts going on for this. See the topic at http://tinyurl.com/qrb39k
|-
|Timezones, JDate and Datetime (gregorian, julian, shamsi, hijri, jewish, buddhist, ethiopian, chinese and french calendar)
|
|0%
|Hannes Papenberg
|
|-
|Refactoring all components to use JForm
|
|80%
|
|
|-

|Localising invalid token message
|
|100%
|
|die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
|-
|Ability to select multiple categories for some views
|
|0%
|
|
|-
|New sample content
|
|80%
|Elin Waring
|
|-
|Reformat translation files to adhere to proper INI specs
|
|75%
|Ole Ottosen, JM Simonet
|In 1.6 we will use PHP's own INI parser and will namespace strings. For example "Weblinks_Category_Fieldname" or "Config_Application_Name"
|-
|Migration script from 1.5 to 1.6
|
|0%
|oc666
|[[Migration script from 1.5 to 1.6]]
|-
|Add module assignment to menu items creation
|
|100%
|
|
|-
|Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|
|-
|[[Language switcher frontend]]
|
|0%
|Christophe Demko
|
|}
[[Category:Development Working Group]]

Why was Joomla 1.5.20 released so quickly?

2010-07-18T14:19:11Z

AmyStephen: New page: Version 1.5.20 has no new changes from Version 1.5.19. It was released because there were packaging problems with Version 1.5.19. Look at the FAQ's for both versions. [[Category:Version ...

Version 1.5.20 has no new changes from Version 1.5.19. It was released because there were packaging problems with Version 1.5.19. Look at the FAQ's for both versions.

[[Category:Version 1.5.19 FAQ]]

[[Category:Version 1.5.20 FAQ]]

Category:Version 1.5.19 FAQ

2010-07-18T14:03:57Z

AmyStephen:

These FAQs are specific to the Joomla 1.5.19 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the Joomla forums for support requests as this is not a substitute for posting there, but rather a common location for the community to gather release issues.

See [http://docs.joomla.org/Category:Version_1.5.20_FAQ Version 1.5.20 FAQ] for more information. 1.5.20 is a re-release of 1.5.19 which had packaging problems.

[[Category:Version 1.5 FAQ]]

Category:Version 1.5.19 FAQ

2010-07-18T14:03:35Z

AmyStephen:

These FAQs are specific to the Joomla 1.5.19 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the Joomla forums for support requests as this is not a substitute for posting there, but rather a common location for the community to gather release issues.

See [[http://docs.joomla.org/Category:Version_1.5.20_FAQ Version 1.5.20 FAQ]] for more information. 1.5.20 is a re-release of 1.5.19 which had packaging problems.

[[Category:Version 1.5 FAQ]]