Joomla! Documentation - User contributions [en]

Talk:Htaccess examples (security)

2014-12-09T15:08:03Z

Pentacle: /* Edit Requests 9 Dec 2014 15:03 */ new section

It could be useful to add some explanations of what these settings do. [[User:Jossi|Jossi]] 16:53, 6 March 2009 (UTC)

== move olddomain redirect? ==

Why not move the olddomain redirect section to its own code block, or in the other useful settings code block.

== Edit Requests 9 Dec 2014 15:03 ==

Hi,

This .htaccess file only allows tmpl=system and tmpl=component. It is possible for developers and templates to provide more options as we do in Nooku Framework.

This rule also does not stop people from fingerprinting Joomla sites either as any URL can still be accessed with tmpl=component.

So I would like to request the removal of the |mpl part in the following line:

RewriteCond %{QUERY_STRING} (^|&)t(p|emplate|mpl)= [NC]

More info and explanation can be found in the below links:

https://github.com/nikosdion/master-htaccess/issues/1
https://github.com/nikosdion/master-htaccess/pulls/2

Archived:Joomla! 1.6 Development Status

2009-10-01T14:06:54Z

Pentacle:

{| 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#XML-RPC_changes_in_J1.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
|70%
|Hannes Papenberg
|
|-
|Access control list (ACL)
|Alpha
|10%
|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
|
|0%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
|Comments system
|
|0%
|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
|
|70%
|
|
|-

|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
|
|0%
|Ron Severdia
|
|-
|Reformat translation files to adhere to proper INI specs
|
|0%
|
|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%
|
|
|-
|Add module assignment to menu items creation
|
|100%
|
|
|-
|Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|}
[[Category:Development Working Group]]

Archived:Joomla! 1.6 Development Status

2009-09-10T14:32:17Z

Pentacle:

{| 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#XML-RPC_changes_in_J1.6]].
|-
|Upgrade to Mootools 1.2
|Alpha
|95%
|Louis Landry, Ercan Özkaya
|com_media waits for $ to document.id conversion
|-
|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
|70%
|Hannes Papenberg
|
|-
|Access control list (ACL)
|Alpha
|10%
|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
|
|0%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
|Comments system
|
|0%
|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
|
|70%
|
|
|-

|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
|
|0%
|Ron Severdia
|
|-
|Reformat translation files to adhere to proper INI specs
|
|0%
|
|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%
|
|
|-
|Add module assignment to menu items creation
|
|100%
|
|
|-
|Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|}
[[Category:Development Working Group]]

Archived:Joomla! 1.6 Development Status

2009-09-10T14:28:08Z

Pentacle:

{| 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#XML-RPC_changes_in_J1.6]].
|-
|Upgrade to Mootools 1.2
|Alpha
|95%
|Louis Landry, Ercan Özkaya
|com_media waits for $ to document.id conversion
|-
|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
|70%
|Hannes Papenberg
|
|-
|Access control list (ACL)
|Alpha
|10%
|Hannes Papenberg, Louis Landry
|
|-
|User management system
|Alpha
|5%
|
|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
|
|0%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
|Comments system
|
|0%
|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
|
|70%
|
|
|-

|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
|
|0%
|Ron Severdia
|
|-
|Reformat translation files to adhere to proper INI specs
|
|0%
|
|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%
|
|
|-
|Add module assignment to menu items creation
|
|100%
|
|
|-
|Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|}
[[Category:Development Working Group]]

Archived:Joomla! 1.6 Development Status

2009-08-30T23:03:31Z

Pentacle:

{| 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
|-
|Upgrade to Mootools 1.2
|Alpha
|95%
|Louis Landry, Ercan Özkaya
|com_media waits for $ to document.id conversion
|-
|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
|70%
|Hannes Papenberg
|
|-
|Access control list (ACL)
|Alpha
|10%
|Hannes Papenberg, Louis Landry
|
|-
|User management system
|Alpha
|5%
|
|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
|
|0%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
|Comments system
|
|0%
|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
|
|70%
|
|
|-

|Localising invalid token message
|
|0%
|
|die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
|-
|Ability to select multiple categories for some views
|
|0%
|
|
|-
|New sample content
|
|0%
|Ron Severdia
|
|-
|Reformat translation files to adhere to proper INI specs
|
|0%
|
|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%
|
|
|-
|Add module assignment to menu items creation
|
|100%
|
|
|-
|Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|}
[[Category:Development Working Group]]

Archived:Joomla! 1.6 Development Status

2009-08-03T20:06:55Z

Pentacle:

{| class="wikitable" style="font-size: 95%; padding:4px; width: auto;"
!'''Task'''
!'''Blocker'''
!'''Status'''
!'''Contact person'''
!'''Description'''
|-
|Implement JForm library
|Alpha
|95%
|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
|-
|Upgrade to Mootools 1.2
|Alpha
|95%
|Louis Landry, Ercan Özkaya
|com_media waits for $ to document.id conversion
|-
|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
|80%
|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
|70%
|Hannes Papenberg
|
|-
|Access control list (ACL)
|Alpha
|10%
|Hannes Papenberg, Louis Landry
|
|-
|Replace Contacts with Contact Directory
|Alpha
|30%
|Gergő Erdősi
|Replacement of files is ready, however there are some parts which aren't working
|-
|User management system
|Alpha
|5%
|
|The new com_members needs to be proof checked.
|-
|JContent class
|Alpha
|0%
|Anthony Ferrara
|JContent is a class that will allow us to have a generic way to fire plugins on content
|-
|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
|
|20%
|
|Most of the back-end components have MVC file structure, but they are not fully MVC yet
|-
|Parameters for templates in the database
|
|50%
|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
|
|0%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
|Comments system
|
|0%
|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
|
|-
|Refactoring of cache
|
|0%
|Anthony Ferrara
|
|-
|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
|
|10%
|
|
|-
|JError refactoring
|
|5%
|Anthony Ferrara
|
|-
|Captcha helpers for forms
|
|0%
|
|This will be possible using JForm triggers. We are not going to bundle a Captcha library in core package
|-
|Localising invalid token message
|
|0%
|
|die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
|-
|Ability to select multiple categories for some views
|
|0%
|
|
|-
|New sample content
|
|0%
|Ron Severdia
|
|-
|Reformat translation files to adhere to proper INI specs
|
|0%
|
|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%
|
|
|-
|Consolidating com_content modules into two modules
|
|0%
|Mark Dexter, Hannes Papenberg
|
|-
|Queue redirects
|
|0%
|Anthony Ferrara, Rob Schley
|
|-
|Add module assignment to menu items creation
|
|0%
|
|
|-
|Replace JParameter with JForm-compatibility layer
|
|0%
|
|We did not deeply investigate this yet. It would help to see what is needed for this
|-
|Go to menu instead of menutype when clicking menuname
|
|0%
|
|Usability thing: its not intuitive, that you have to click that small icon in the menu manager to see the actual menu, while you can only change the name of the menutype when clicking the menuname."
|-
|Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|
|-
|Help System Expansion
|
|0%
|Marieke van der Tuin, Chris Davenport
|
|}
[[Category:Development Working Group]]

Archived:Joomla! 1.6 Development Status

2009-05-21T21:49:10Z

Pentacle:

{| class="wikitable" style="font-size: 85%; padding:2px; width: auto;"
!Task
!Blocker
!Status
!Contact person
!Description
|-
!Implement JForm library
|Alpha
|95%
|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
|-
!Upgrade to Mootools 1.2
|Alpha
|90%
|Louis Landry, Ercan Özkaya
|This is mostly finished but there are a few things to do. For example how to load more library. See the discussion at http://tinyurl.com/p5cvbc
|-
!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
|80%
|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
|70%
|Hannes Papenberg
|
|-
!Access control list (ACL)
|Alpha
|10%
|Hannes Papenberg, Louis Landry
|
|-
!Replace Contacts with Contact Directory
|Alpha
|30%
|Gergő Erdősi
|Replacement of files is ready, however there are some parts which aren't working
|-
!User management system
|Alpha
|5%
|
|The new com_members needs to be proof checked.
|-
!JContent class
|Alpha
|0%
|Anthony Ferrara
|JContent is a class that will allow us to have a generic way to fire plugins on content
|-
!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
|
|20%
|
|Most of the back-end components have MVC file structure, but they are not fully MVC yet
|-
!Parameters for templates in the database
|
|50%
|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
|
|0%
|
|A review of the current parameters and implementing new ones for the new category system.
|-
!Comments system
|
|0%
|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
|
|-
!Refactoring of cache
|
|0%
|Anthony Ferrara
|
|-
!PDF generation system
|
|0%
|
|We are thinking of dropping this feature. See the discussion at http://tinyurl.com/obv5j6
|-
!Convert all layouts to semantic and XHTML strict
|
|0%
|Amy Stephen
|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
|
|10%
|
|
|-
!JError refactoring
|
|5%
|Anthony Ferrara
|
|-
!Captcha helpers for forms
|
|0%
|
|This will be possible using JForm triggers. We are not going to bundle a Captcha library in core package
|-
!Localising invalid token message
|
|0%
|
|die('Invalid Token') will be replaced by jexit(JText::_('JInvalid_Token'))
|-
!Ability to select multiple categories for some views
|
|0%
|
|
|-
!New sample content
|
|0%
|
|
|-
!Reformat translation files to adhere to proper INI specs
|
|0%
|
|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%
|
|
|-
!Consolidating com_content modules into two modules
|
|0%
|Mark Dexter, Hannes Papenberg
|
|-
!Queue redirects
|
|0%
|Anthony Ferrara, Rob Schley
|
|-
!Add module assignment to menu items creation
|
|0%
|
|
|-
!Replace JParameter with JForm-compatibilitylayer
|
|0%
|
|We did not deeply investigate this yet. It would help to see what is needed for this
|-
!Go to menu instead of menutype when clicking menuname
|
|0%
|
|Usability thing: its not intuitive, that you have to click that small icon in the menu manager to see the actual menu, while you can only change the name of the menutype when clicking the menuname."
|-
!Ability to load additional layouts with a template
|
|0%
|Hannes Papenberg
|
|-
!Help System Expansion
|
|0%
|Marieke van der Tuin, Chris Davenport
|
|}
[[Category:Development Working Group]]

Archived:Access Control System In Joomla 1.6

2009-04-15T20:39:05Z

Pentacle:

==Overview==
===Sections===
Sections are used to group rules, actions, assets and assetgroups for each extension using the table jos_access_sections. This allows us to have completely seperate ACL systems for different extensions.
===Users===
These are users stored in jos_users table. Please note that gid and usertype fields are only there for legacy purposes and are not used in the current ACL system.
Users can be mapped to rules via jos_user_rule_map table.
in phpGACl, users were called AROs (Access Request Object)
===User Groups===
These are user groups that are hold in table jos_usergroups. You can have nested user groups. Each group obviously can hold an unlimited number of users and each user can be assigned to an unlimited number of user groups. These relations are hold in the table jos_user_usergroup_map.
User groups can be mapped to rules via jos_usergroup_rule_map table.
===Actions===
Actions are things your users will perform such that logging in to backend
===Assets===
Assets are items that you need to set access control on. For example each article on your site can be an asset and you can set edit permission for them. Currently these are not used in core.
===Asset Groups===
These are used for creating different view permissions for a combination of usergroups. (???)
How this is achieved:
* First a view action is created with access type 3. (eg. core.view)
* Then an asset group is created with some user groups in it.
* A rule is set with the name convention {action_name}.{asset_group_id} (eg. core.view.1 for Public)
* Both action, assetgroup and user groups are mapped to this rule.
*When three of them maps to the same rule JUser::getAuthorisedLevels() will also return the new asset group id.
===Rules===
Rules are combinations of actions and usergroups (or users) and optionally assets
There are three types of rules:
* Type 1: These are rules that allow a user or user group to do an action. For example user group X can log in to backend.
* Type 2: These are rules that allow a user or user group to do an action on an asset. For example user group X can edit an article with the id of Y.
* Type 3: These are rules that allow a user or user group to do an action (mostly view) on an asset group. For example user group X can view articles with the asset group of Y. (???)
==Library==
TODO
==Examples==
===Core Access Levels===
There are three access levels in core by default Public, Registered, Special. These are access levels. For them we use the action ''core.view''. Let's use '''Special''' for our example:
First of all there is an asset group named Special. We need to tie some user groups to it and selecting Manager is enough. Because the system will automatically include its child groups (being Administrator and Super Administrator by default) The rule needed for this level is ''core.view.3''. As you remember naming convention is action_name.asset_group_id and here our id is 3.

[[Category:Joomla! 1.6]]

Archived:Access Control System In Joomla 1.6

2009-04-13T20:55:55Z

Pentacle:

==Overview==
===Sections===
Sections are used to group rules, actions for each extension using the table jos_access_sections
===Users===
These are users stored in jos_users table. Please note that gid and usertype fields are only there for legacy purposes and are not used in the current ACL system.
Users can be mapped to rules via jos_user_rule_map table.
in phpGACl, users were called AROs (Access Request Object)
===User Groups===
These are user groups that are hold in table jos_usergroups. You can have nested user groups. Each group obviously can hold an unlimited number of users and each user can be assigned to an unlimited number of user groups. These relations are hold in the table jos_user_usergroup_map.
User groups can be mapped to rules via jos_usergroup_rule_map table.
===Actions===
Actions are things your users will perform such that logging in to backend
===Assets===
Assets are items that you need to set access control on. For example each article on your site can be an asset and you can set edit permission for them. Currently these are not used in core.
===Asset Groups===
These are used for creating different view permissions for a combination of usergroups. (???)
How this is achieved:
* First a view action is created with access type 3. (eg. core.view)
* Then an asset group is created with some user groups in it.
* A rule is set with the name convention {action_name}.{asset_group_id} (eg. core.view.1 for Public)
* Both action, assetgroup and user groups are mapped to this rule.
*When three of them maps to the same rule JUser::getAuthorisedLevels() will also return the new asset group id.
===Rules===
Rules are combinations of actions and usergroups (or users) and optionally assets
There are three types of rules:
* Type 1: These are rules that allow a user or user group to do an action. For example user group X can log in to backend.
* Type 2: These are rules that allow a user or user group to do an action on an asset. For example user group X can edit an article with the id of Y.
* Type 3: These are rules that allow a user or user group to do an action (mostly view) on an asset group. For example user group X can view articles with the asset group of Y. (???)
==Library==
TODO
==Examples==
===Core Access Levels===
There are three access levels in core by default Public, Registered, Special. These are access levels. For them we use the action ''core.view''. Let's use '''Special''' for our example:
First of all there is an asset group named Special. We need to tie some user groups to it and selecting Manager is enough. Because the system will automatically include its child groups (being Administrator and Super Administrator by default) The rule needed for this level is ''core.view.3''. As you remember naming convention is action_name.asset_group_id and here our id is 3.

Archived:Access Control System In Joomla 1.6

2009-04-13T20:17:08Z

Pentacle: New page: ==Overview== ===Sections=== Sections are used to group rules, actions for each extension using the table jos_access_sections ===Users=== These are users stored in jos_users table. Please n...

J1.5:Plugin/Events/Content

2009-01-14T16:18:36Z

Pentacle:

{{incomplete}}
[[Category:Development]]
[[Category:Plugins]]
=5.5 Content Events for Plugin System=
==5.5.1 Overview==
Content events are triggered during the content creation process. This may occur
in views in the com_content component, or in other components or modules.

==5.5.2 onBeforeContentSave==
===5.5.2.1 Description===
This is an event that is called right before the content is saved into the database. Since the article object is passed by reference, you can make any changes you wish to the data. You can also abort the save by returning false. In this case the error set by calling $article->setError($message); will be displayed to user.
===5.5.2.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.2.3 Return Value===
Boolean. Result will affect the saving process. See description for details.
===5.5.4.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.3 onAfterContentSave==
===5.5.3.1 Description===
This is an event that is called after the content is saved into the database. Even though article object is passed by reference, changes will not be saved since storing data into database phase is past. An example use case would be redirecting user to the appropriate place after saving.
===5.5.3.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.3.3 Return Value===
None. Result will be omitted.
===5.5.3.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.4 onPrepareContent==
===5.5.4.1 Description===
This is the first stage in preparing content for output and is the most common point
for content orientated plugins to do their work. Since the article and related parameters
are passed by reference, event handlers can modify them prior to display.
===5.5.4.2 Parameters===
*article A reference to the article that is being rendered by the view.
*params A reference to an associative array of relevant parameters. The view determines what it considers to be relevant and passes that information along.
*limitstart An integer that determines the "page" of the content that is to be generated. Note that in the context of views that might not generate HTML output, a page is a reasonably abstract concept that depends on the context.
===5.5.4.3 Return Value===
None. Results are returned by modifying the referenced arguments.
===5.5.4.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/article/view.pdf.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*plugins/content/code.php
*plugins/content/emailcloak.php
*plugins/content/geshi.php
*plugins/content/image.php
*plugins/content/loadmodule.php
*plugins/content/pagebreak.php
*plugins/content/sef.php

==5.5.5 onAfterDisplayTitle==
===5.5.5.1 Description===
This is a request for information that should be placed between the content title and
the content body.
Although parameters are passed by reference, this is not the event to modify article data. Use onPrepareContent for that purpose.
===5.5.5.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.5.3 Return Value===
String. Returned value from this event will be displayed in a placeholder. Most templates display this placeholder after the article separator.
===5.5.5.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.5.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.6 onBeforeDisplayContent==
===5.5.6.1 Description===
This is a request for information that should be placed immediately before the generated content. For views that generate XHTML/HTML, this might include the use of styles that are specified as part of the content or related parameters.
Although parameters are passed by reference, this is not the event to modify article data. Use onPrepareContent for that purpose.
===5.5.6.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that
unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.6.3 Return Value===
String. Returned value from this event will be displayed in a placeholder. Most templates display this placeholder after the article separator.
===5.5.6.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.6.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.7 onAfterDisplayContent==
===5.5.7.1 Description===
This is a request for information that should be placed immediately after the generated content. For views that generate XHTML/HTML, this might include the closure of styles that are specified as part of the content or related parameters.
Although parameters are passed by reference, this is not the event to modify article data. Use onPrepareContent for that purpose.
===5.5.7.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.7.3 Return Value===
String. Returned value from this event will be displayed in a placeholder. Most templates display this placeholder after the article separator.
===5.5.7.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
===5.5.7.5 See Also===
*components/com_content/views/article/tmpl/default.php

J3.x:Triggering content plugins in your extension

2009-01-14T15:57:53Z

Pentacle:

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

Using the plugin system in your addon is fairly simple. The most important part is good planning because, to some degree, you're defining an interface for other people to use.

To activate the plugins for your addon, you just have to use the following code:
<source lang="php">
$dispatcher =& JDispatcher::getInstance();
$results = $dispatcher->trigger('onSomething', $params);
</source>
This function calls every plugin that has registered itself for the event 'onSomething' and hands over the array $param as parameter.

As a return value you get an array of results from these plugins. All this is of course optional, you could also use the system without parameters and/or a result.

You can also pass arguments by reference to allow plugins to edit the passed data. For example:
<source lang="php">
$dispatcher =& JDispatcher::getInstance();
$dispatcher->trigger('onSomething', &$params);
</source>

You might want to look at core components (for example com_content) for an example.

J1.5:Plugin/Events/Contact

2009-01-14T15:54:01Z

Pentacle: New page: Category:Development Category:Plugins ===Overview=== Contact events are triggered during the contact form submitting process. === onValidateContact === '''Description''' This ev...

[[Category:Development]]
[[Category:Plugins]]
===Overview===
Contact events are triggered during the contact form submitting process.

=== onValidateContact ===
'''Description'''

This event is triggered after a contact form has been submitted.
An example use case would be validating a captcha. If you return a JError, JException or Exception object form submission will be terminated.

'''Parameters'''

*contact A reference to the person who will receive the form.
*post A reference to the $_POST variable.

'''Return Value'''

None or object. See description for details.

'''Called in files'''

*components/com_contact/controller.php

=== onSubmitContact ===
'''Description'''

This event is triggered after a contact form has been submitted. You can use this for sending additional mails etc.

'''Parameters'''

*contact A reference to the person who will receive the form.
*post A reference to the $_POST variable.

'''Return Value'''

None.

'''Called in files'''

*components/com_contact/controller.php

Plugin

2009-01-14T15:37:44Z

Pentacle:

[[Category:Bin]]
====== Plugins ======
Joomla! plugins enable you to execute code in response to certain events, either Joomla! core events or custom events that are triggered from your own code. This is a powerful way of extending the basic Joomla! functionality. To see where plugins fit in with the overall Joomla! architecture, look at [[http://dev.joomla.org/content/view/1137/80/|Framework overview]].

The Joomla! plugin architecture follows the [http://en.wikipedia.org/wiki/Observer_pattern Observer] design pattern. The [[references:joomla.framework:application:jplugin|JPlugin]] class is derived from [[references:joomla.framework:base:jobserver|JObserver]] and provides the means to register custom plugin code with core or custom events. The [[references:joomla.framework:application:jeventdispatcher|JEventDispatcher]] class, derived from [[references:joomla.framework:base:jobservable|JObservable]], is an event handler which calls all plugins registered for a particular event, when that event is triggered.

* [[Tutorial:Creating_a_Plugin_for_Joomla_1.5]]
* [[How_to_create_a_content_plugin]]
* [[plugins:using_plugins|How to use plugins in your own code]]
* [[Tutorial:Creating_an_Authentication_Plugin_for_Joomla_1.5]]

Useful reference: [[http://codex.gallery2.org/index.php/Gallery2:Embedding:Event-Based_Loose-Coupled_Integration|Gallery 2: Embedding: Event-Based Loose-Coupled Integration]]

Prior to Joomla! 1.5 plugins were known as mambots. Mambots were able to change content only and were based on certain signal words. Since then their scope has been stretched and extended to such an extent that to enhance the meaning of the new functionality the developers decided to change the name from mambots to plugins. Joomla! 1.5 includes legacy support for Joomla! 1.0 mambots.

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

======Events======
Joomla! ships with a variety of core events, organised into groups. These are described in the following topics.

* [[Reference:System_Events_for_Plugin_System|System events]]
* [[Reference:User_Events_for_Plugin_System|User events]]
* [[Reference:Editor_Events_for_Plugin_System|Editor events]]
* [[Reference:Content Events for Plugin System|Content events]]
* [[Reference:Contact_Events_for_Plugin_System|Contact events]]

This is an alphabetical list of the core events in Joomla! 1.5 together with the group name to which each belongs. Each event name links to more detailed information.

*[[Reference:Content Events for Plugin System#onAfterContentSave|onAfterContentSave]] (content)
*[[Reference:User_Events_for_Plugin_System#onAfterDeleteUser|onAfterDeleteUser]] (user)
*[[Reference:Content Events for Plugin System#onAfterDisplay|onAfterDisplay]] (content)
*[[Reference:Content Events for Plugin System#onAfterDisplayTitle|onAfterDisplayTitle]] (content)
*[[Reference:Content Events for Plugin System#onAfterDisplayContent|onAfterDisplayContent]] (content)
*[[Reference:System_Events_for_Plugin_System#onAfterInitialise|onAfterInitialise]] (system)
*[[Reference:System_Events_for_Plugin_System#onAfterRoute|onAfterRoute]] (system)
*[[Reference:System_Events_for_Plugin_System#onAfterDispatch|onAfterDispatch]] (system)
*[[Reference:System_Events_for_Plugin_System#onAfterRender|onAfterRender]] (system)
*[[Reference:User_Events_for_Plugin_System#onAfterStoreUser|onAfterStoreUser]] (user)
*[[Reference:User_Events_for_Plugin_System#onAuthenticate|onAuthenticate]] (authentication)
*[[Reference:User_Events_for_Plugin_System#onAuthenticateFailure|onAuthenticateFailure]] (authentication)
*[[Reference:Content Events for Plugin System#onBeforeContentSave|onBeforeContentSave]] (content)
*[[Reference:User_Events_for_Plugin_System#onBeforeDeleteUser|onBeforeDeleteUser]] (user)
*[[Reference:Content Events for Plugin System#onBeforeDisplay|onBeforeDisplay]] (content)
*[[Reference:Content Events for Plugin System#onBeforeDisplayContent|onBeforeDisplayContent]] (content)
*[[Reference:User_Events_for_Plugin_System#onBeforeStoreUser|onBeforeStoreUser]] (user)
*[[Reference:Editor_Events_for_Plugin_System#onCustomEditorButton|onCustomEditorButton]] (editors-xtd)
*[[Reference:Editor_Events_for_Plugin_System#onDisplay|onDisplay]] (editors)
*[[Reference:Editor_Events_for_Plugin_System#onGetContent|onGetContent]] (editors)
*[[Reference:Editor_Events_for_Plugin_System#onGetInsertMethod|onGetInsertMethod]] (editors)
*[[Reference:System_Events_for_Plugin_System#onGetWebServices|onGetWebServices]] (xmlrpc)
*[[Reference:Editor_Events_for_Plugin_System#onInit|onInit]] (editors)
*[[Reference:User_Events_for_Plugin_System#onLoginUser|onLoginUser]] (user)
*[[Reference:User_Events_for_Plugin_System#onLogoutUser|onLogoutUser]] (user)
*[[Reference:Content Events for Plugin System#onPrepareContent|onPrepareContent]] (content)
*[[Reference:Editor_Events_for_Plugin_System#onSave|onSave]] (editors)
*[[Reference:System_Events_for_Plugin_System#onSearch|onSearch]] (search)
*[[Reference:System_Events_for_Plugin_System#onSearchAreas|onSearchAreas]] (search)
*[[Reference:Editor_Events_for_Plugin_System#onSetContent|onSetContent]] (editors)
*[[Reference:Contact_Events_for_Plugin_System#onSubmitContact|onSubmitContact]] (contact)
*[[Reference:Contact_Events_for_Plugin_System#onValidateContact|onValidateContact]] (contact)

J1.5:Plugin/Events/Content

2009-01-14T15:17:53Z

Pentacle:

{{incomplete}}
[[Category:Development]]
[[Category:Plugins]]
=5.5 Content Events for Plugin System=
==5.5.1 Overview==
Content events are triggered during the content creation process. This may occur
in views in the com_content component, or in other components or modules.

==5.5.2 onBeforeContentSave==
===5.5.2.1 Description===
This is an event that is called right before the content is saved into the database. Since the article object is passed by reference, you can make any changes you wish to the data. You can also abort the save by returning false. In this case the error set by calling $article->setError($message); will be displayed to user.
===5.5.2.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.2.3 Return Value===
Boolean. Result will affect the saving process. See description for details.
===5.5.4.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.3 onAfterContentSave==
===5.5.3.1 Description===
This is an event that is called after the content is saved into the database. Even though article object is passed by reference, changes will not be saved since storing data into database phase is past. An example use case would be redirecting user to the appropriate place after saving.
===5.5.3.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.3.3 Return Value===
None. Result will be omitted.
===5.5.3.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.4 onPrepareContent==
===5.5.4.1 Description===
This is the first stage in preparing content for output and is the most common point
for content orientated plugins to do their work. Since the article and related parameters
are passed by reference, event handlers can modify them prior to display.
===5.5.4.2 Parameters===
*article A reference to the article that is being rendered by the view.
*params A reference to an associative array of relevant parameters. The view determines what it considers to be relevant and passes that information along.
*limitstart An integer that determines the "page" of the content that is to be generated. Note that in the context of views that might not generate HTML output, a page is a reasonably abstract concept that depends on the context.
===5.5.4.3 Return Value===
None. Results are returned by modifying the referenced arguments.
===5.5.4.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/article/view.pdf.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*plugins/content/code.php
*plugins/content/emailcloak.php
*plugins/content/geshi.php
*plugins/content/image.php
*plugins/content/loadmodule.php
*plugins/content/pagebreak.php
*plugins/content/sef.php

==5.5.5 onAfterDisplayTitle==
===5.5.5.1 Description===
This is a request for information that should be placed between the content title and
the content body.
Although parameters are passed by reference, this is not the event to modify article data. Use onPrepareContent for that purpose.
===5.5.5.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.5.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.5.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.5.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.6 onBeforeDisplayContent==
===5.5.6.1 Description===
This is a request for information that should be placed immediately before the generated content. For views that generate XHTML/HTML, this might include the use of styles that are specified as part of the content or related parameters.
Although parameters are passed by reference, this is not the event to modify article data. Use onPrepareContent for that purpose.
===5.5.6.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that
unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.6.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.6.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.6.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.7 onAfterDisplayContent==
===5.5.7.1 Description===
This is a request for information that should be placed immediately after the generated content. For views that generate XHTML/HTML, this might include the closure of styles that are specified as part of the content or related parameters.
Although parameters are passed by reference, this is not the event to modify article data. Use onPrepareContent for that purpose.
===5.5.7.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.7.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.7.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
===5.5.7.5 See Also===
*components/com_content/views/article/tmpl/default.php

== Overskrift ==

J1.5:Plugin/Events/Content

2009-01-14T15:08:22Z

Pentacle:

{{incomplete}}
[[Category:Development]]
[[Category:Plugins]]
=5.5 Content Events for Plugin System=
==5.5.1 Overview==
Content events are triggered during the content creation process. This may occur
in views in the com_content component, or in other components or modules.

Note: This article does not yet describe the events onBeforeContentSave and onAfterContentSave that were added in [http://www.joomla.org/content/view/5180/1/1/1/#Content_Trigger_Additions Joomla 1.5.4]

==5.5.2 onBeforeContentSave==
===5.5.2.1 Description===
This is an event that is called right before the content is saved into the database. Since the article object is passed by reference, you can make any changes you wish to the data. You can also abort the save by returning false. In this case the error set by calling $article->setError($message); will be displayed to user.
===5.5.2.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.2.3 Return Value===
Boolean. Result will affect the saving process. See description for details.
===5.5.4.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.3 onAfterContentSave==
===5.5.3.1 Description===
This is an event that is called after the content is saved into the database. Even though article object is passed by reference, changes will not be saved since storing data into database phase is past. An example use case would be redirecting user to the appropriate place after saving.
===5.5.3.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.3.3 Return Value===
None. Result will be omitted.
===5.5.3.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.4 onPrepareContent==
===5.5.4.1 Description===
This is the first stage in preparing content for output and is the most common point
for content orientated plugins to do their work. Since the article and related parameters
are passed by reference, event handlers can modify them prior to display.
===5.5.4.2 Parameters===
*article A reference to the article that is being rendered by the view.
*params A reference to an associative array of relevant parameters. The view determines what it considers to be relevant and passes that information along.
*limitstart An integer that determines the "page" of the content that is to be generated. Note that in the context of views that might not generate HTML output, a page is a reasonably abstract concept that depends on the context.
===5.5.4.3 Return Value===
None. Results are returned by modifying the referenced arguments.
===5.5.4.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/article/view.pdf.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*plugins/content/code.php
*plugins/content/emailcloak.php
*plugins/content/geshi.php
*plugins/content/image.php
*plugins/content/loadmodule.php
*plugins/content/pagebreak.php
*plugins/content/sef.php

==5.5.5 onAfterDisplayTitle==
===5.5.5.1 Description===
This is a request for information that should be placed between the content title and
the content body.
===5.5.5.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that
unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.5.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.5.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.5.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.6 onBeforeDisplayContent==
===5.5.6.1 Description===
This is a request for information that should be placed immediately before the generated content. For views that generate XHTML/HTML, this might include the use of styles that are specified as part of the content or related parameters.
===5.5.6.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that
unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.6.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.6.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.6.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.7 onAfterDisplayContent==
===5.5.7.1 Description===
This is a request for information that should be placed immediately after the generated content. For views that generate XHTML/HTML, this might include the closure of styles that are specified as part of the content or related parameters.
===5.5.7.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.7.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.7.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
===5.5.7.5 See Also===
*components/com_content/views/article/tmpl/default.php

== Overskrift ==

J1.5:Plugin/Events/Content

2009-01-14T15:07:51Z

Pentacle: on(before|after)save events added

{{incomplete}}
[[Category:Development]]
[[Category:Plugins]]
=5.5 Content Events for Plugin System=
==5.5.1 Overview==
Content events are triggered during the content creation process. This may occur
in views in the com_content component, or in other components or modules.

Note: This article does not yet describe the events onBeforeContentSave and onAfterContentSave that were added in [http://www.joomla.org/content/view/5180/1/1/1/#Content_Trigger_Additions Joomla 1.5.4]

==5.5.2 onBeforeContentSave==
===5.5.2.1 Description===
This is an event that is called right before the content is saved into the database. Since the article object is passed by reference, you can make any changes you wish to the data. You can also abort the save by returning false. In this case the error set by calling $article->setError($message); will be displayed to user.
===5.5.2.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.2.3 Return Value===
Boolean. Result will affect the saving process. See description for details.
===5.5.4.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.3 onBeforeContentSave==
===5.5.3.1 Description===
This is an event that is called after the content is saved into the database. Even though article object is passed by reference, changes will not be saved since storing data into database phase is past. An example use case would be redirecting user to the appropriate place after saving.
===5.5.3.2 Parameters===
*article A reference to the JTableContent object that is being saved which holds the article data.
*isNew A boolean which is set to true if the content is about to be created.
===5.5.3.3 Return Value===
None. Result will be omitted.
===5.5.3.4 Used in files===
*administrator/components/com_content/controller.php
*components/com_content/models/article.php

==5.5.4 onPrepareContent==
===5.5.4.1 Description===
This is the first stage in preparing content for output and is the most common point
for content orientated plugins to do their work. Since the article and related parameters
are passed by reference, event handlers can modify them prior to display.
===5.5.4.2 Parameters===
*article A reference to the article that is being rendered by the view.
*params A reference to an associative array of relevant parameters. The view determines what it considers to be relevant and passes that information along.
*limitstart An integer that determines the "page" of the content that is to be generated. Note that in the context of views that might not generate HTML output, a page is a reasonably abstract concept that depends on the context.
===5.5.4.3 Return Value===
None. Results are returned by modifying the referenced arguments.
===5.5.4.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/article/view.pdf.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*plugins/content/code.php
*plugins/content/emailcloak.php
*plugins/content/geshi.php
*plugins/content/image.php
*plugins/content/loadmodule.php
*plugins/content/pagebreak.php
*plugins/content/sef.php

==5.5.5 onAfterDisplayTitle==
===5.5.5.1 Description===
This is a request for information that should be placed between the content title and
the content body.
===5.5.5.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that
unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.5.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.5.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.5.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.6 onBeforeDisplayContent==
===5.5.6.1 Description===
This is a request for information that should be placed immediately before the generated content. For views that generate XHTML/HTML, this might include the use of styles that are specified as part of the content or related parameters.
===5.5.6.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that
unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.6.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.6.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
*modules/mod_newsflash/helper.php
===5.5.6.5 See Also===
*components/com_content/views/article/tmpl/default.php

==5.5.7 onAfterDisplayContent==
===5.5.7.1 Description===
This is a request for information that should be placed immediately after the generated content. For views that generate XHTML/HTML, this might include the closure of styles that are specified as part of the content or related parameters.
===5.5.7.2 Parameters===
See the onPrepareContent event for additional discussion of these parameters. Note that unlike onPrepareContent, these parameters are passed by value.
*article The article that is being rendered by the view.
*params An associative array of relevant parameters.
*limitstart An integer that determines the "page" of the content that is to be generated.
===5.5.7.3 Return Value===
An array. In XHTML/HTML views, this is is an array of strings, each of which becomes a line in the output stream.
===5.5.7.4 Used in files===
*components/com_content/views/article/view.html.php
*components/com_content/views/category/view.html.php
*components/com_content/views/frontpage/view.html.php
*components/com_content/views/section/view.html.php
===5.5.7.5 See Also===
*components/com_content/views/article/tmpl/default.php

== Overskrift ==

Archived:Version 1.6 Developer Notes

2008-11-01T17:51:46Z

Pentacle:

{{incomplete}}
{{RightTOC}}
[[Category:Development]]

Compilation of developer notes on changes in 1.6.

== Schema ==

* Added ACL tables (todo - list them)
* Removed jos_groups table
* Removed [[Tables/plugins|jos_plugins]] table in favour of [[Tables/extensions|jos_extensions]]
* Added update tables
** jos_updates
** jos_update_sites
** jos_update_sites_extensions
** jos_update_categories
* Added backup tables
** jos_backups ?? @TODO
* Added tasks tables
** jos_tasks
** jos_taak_sets

== Framework ==

=== JAuthorization ===

Remove <code>JAuthorization::_mos_add_acl</code>.

Added <code>JAuthorization::getUserAccessLevels( $section [, $action = 'view'] )</code>.

=== JDatabase ===

JDatabase::setQuery casts the sql variable to a string. This allows you to pass an object that implements the __toString magic method.

=== JFile ===

Both JFile::write and JFTP::write now use a reference for its second argument. Code like ''JFile::write($filename,'string');'' will fail, however ''$data = 'string'; JFile::write($filename, $data);'' will work for both 1.5 and 1.6

=== JModel ===

JModel::getState will now take an optional second argument to set the default.
$value = $model->getState( 'foo', 'bar' );

JModel has an addition contruction option and internal variable <code>__state_set</code>. This is used to lazy-load model initialisation.

=== New API ===

Added <code>JTableTree</code> as an abstract class for tree-based tables.

Made JObject abstract. It can no longer be directly instantiated. Use JStdClass instead.

Added <code>JDocumentXML</code> to allow easy generation of valid XML files.

== Components ==

=== Join for access level ===

Before:
<pre>LEFT JOIN #__groups AS g ON g.id = c.access</pre>

After:
<pre>LEFT JOIN #__core_acl_axo_groups AS g ON g.value = a.access</pre>

=== Administrator:Users ===

== Legacy Mode ==

Only available in legacy mode (to be dropped in future versions):

* <code>global $mainframe</code> - Use <code>$app = &JFactory::getApplication()</code> instead.
* JTemplate (patTemplate completely deprecated)

== Files/Features Dropped ==

* Support for constants as language strings with JLanguage

== TODO ==

Don't forget to do this:

* Access Level links in backend lists need to be refactored to support the new levels available in the jos_core_acl_axo_groups table.

FAQ Joomla! 1.5.7

2008-09-17T12:00:51Z

Pentacle:

Moved to
[[Why_do_you_get_a_%22Fatal_error:_Call_to_undefined_function:_stripos()%22_when_editing_Joomla!_1.5.7_Articles_from_the_frontend_when_using_PHP_4%3F]]

[[Why_are_the_front_page_articles_ordered_differently_after_the_upgrade_to_1.5.7%3F]]

[[Why_can%27t_users_login_in_version_1.5.7_with_php_4%3F]]

Portal:Developers

2008-07-20T23:38:44Z

Pentacle: Replaced links to dev site

{{Developer profile}}

== Participation ==

* [[Participating in the community]]: a brief description of how people can get involved.
* [[Coding style and standards]] (To be reviewed).
* [[Patch submission guidelines]].
* [[Filing bugs and issues]].
* [[How to release a distribution tarball]].

== Reference Pages ==

Peruse all pages in the [[:Category:Development]] category.

When creating a new page, ensure you place the following marker at the top of the page so it is included in the category list:

<pre><nowiki>[[Category:Development]]
</nowiki></pre>

If you locate other articles you thing that are relevant to developer, please add this marker to those pages.

== Articles and Tutorials on developer.joomla.org ==

[http://community.joomla.org/magazine/article/508-developer-localization-advancements-in-joomla-15.html Localization Advancements in Joomla! 1.5]

[http://developer.joomla.org/tutorials/165-understanding-output-overrides-in-joomla.html Understanding Output Overrides in Joomla! 1.5]

[http://developer.joomla.org/tutorials/181-preventing-sql-injections.html Preventing SQL Injections]

[http://developer.joomla.org/tutorials/184-how-to-create-a-joomla-plugin.html How to create a Joomla! Plugin]

== Cookie Jar ==

Articles that need to be written.

* Developer guidelines.
* Secure coding guidelines.
* Error message conventions.
* Exception handling.
* Release numbering, compatibility and deprecation.
* Complete/update/review the wiki API reference (assumes this has been moved from DocuWiki to MediaWiki).
* Update developer tutorials and how-to's currently on dev.joomla.org
** Review all material under the tutorials heading at http://dev.joomla.org/component/option,com_jd-wiki/Itemid,32/
** Recommend material to be migrated over to docs.joomla.org
** Update material that is to be migrated over to docs.joomla.org
* [[Adding AJAX to your component]].
** Write a document describing how to add AJAX to an MVC component. If desired, use the MVC Hello World tutorial as a base. Describe where various elements should go in the MVC design pattern. Also describe how to implement MVC in a module (these need supporting components to do AJAX).
* [[Creating a toolbar for your component]].
* [[Adding configuration objects to modules and plugins]].
* [[Storing data in the session between page loads]].
* [[Using the caching system in your component]].
* [[Creating a file uploader in your component]].
* [[Suppressing output of extra HTML]].
* [[Adding view layout configuration parameters]].
** Explain how to create an XML file that will allow users to configure views.
* [[How to implement XML-RPC in a component]]
** There are two ways to do this:
*** Implement it using an XML-RPC plugin
*** Implement it in the component itself using raw views
* [[How to use the filesystem package]]
* [[How to use the filter package]]
** Describe how and when to use the Filter package and explain what needs to be filtered for various situations (for queries, for URLs, etc)
* [[How to use the registry package]]
* [[How to use JSimpleXML]]
** How to load and store XML files and how to work with them
* [[How to add breadcrumbs]]
* [[How to create component feeds]] (RSS/ATOM)
* [[How to create PDF views]]
* [[How to send email from components]]
* [[What's available in the JFactory class]]
* [[How to generate paths for client side and server side]]
* How to access information from the request/browser
** This focuses on using the JBrowser class to retrieve information about the features available in the user's browser.
* [[How to create an editor plugin]]
* [[What can be done with a user plugin]]
* [[How to work with parameters]]
* [[How to use the JToolBar class in the frontend]]
* [[How to use the editor in a component]]
* [[How to cloak email addresses]]

[[Category:Development]]