Joomla! Developer Network

There is always a great deal of Joomla! development activity underway and communicating with other developers in the community is essential. This site is a resource for anyone looking to build or maintain software based on the Joomla platform

Version 11.2 ("Omar") of the Joomla Platform was tagged and released on 26 July 2011.

The following pull requests made by community contributors were merged:

  • #140 ] Minor doc block changes for doc purposes. ( ianmacl )

  • #138 ] Silly fix. ( LouisLandry )

  • #137 ] Updates for 11.2 ( LouisLandry )

  • #136 ] Undefined index: 'CLIENT' in updater/adapters/collection.php ( WebMechanic )

    - take 3 From: http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_id=8103&tracker_item_id=26445

  • #135 ] Code sniffer compliance for access package. ( eddieajau )

    Fixed most phpcs complaints.

  • #132 ] doc blocks cache ( elinw )

    More doc blocks

  • #116 ] JAuthentication updates to block logins and use class constants ( pasamio )

    For a while people have wanted to cancel login from authentication plugins. This complicates the authentication system by providing functionality that isn't true - the user may or may not have successfully been authenticated but this doesn't mean they are authorised to login which is what many want to achieve via the JAUTHENTICATE_STATUS_CANCEL. This updates to provide a new plugin trigger called "onUserAuthorisation". This trigger can be used from either a user plugin or authentication plugin as both are loaded at the same time. This trigger provides the ability to return the following responses: - JAuthentication::STATUS_SUCCESS - JAuthentication::STATUS_EXPIRED - JAuthentication::STATUS_DENIED - JAuthentication::STATUS_UNKNOWN Both success and unknown do not prevent login. Returning expired or denied will halt the login process. Additionally, as you can see above, the constants have been shifted into the class and the prefix "JAUTHENTICATE_" removed from them. The old constants remain for backwards compatibility.

  • #130 ] Make JUpdate also use regular expression for targetplatform ( rvsjoen )

    When using collections in the updater, the tag allows you to specify a targetplatformversion using regular expressions, however the tag does not.

  • #131 ] Fix strict warning in JDatabase ( rvsjoen )

    Fix strict warning in JDatabase, abstract static functions are not allowed. Instead extract the function out into an interface and implement this interface in JDatabase. I would not mind putting that into a separate file, but we need a filename/directory/naming convention for interfaces.

  • #134 ] Fixing up a unit test I broke. ( LouisLandry )

  • #128 ] Code cleaning ( eddieajau )

    Code cleaning (tested against new custom sniff).

  • #133 ] Fixing up the code sniffer and doing a little code cleanup. ( LouisLandry )

  • #120 ] Doc blocks ( elinw )

    work oh html doc blocks.

  • #97 ] System test failure fix ( elinw )

    Correct fatal error when a category id of 0 is passed in; this was exposed as a problem with system test failurs on the CMS whem there was a failure to get the module params correctly. With this hange fall back to default works.

  • #119 ] Allow the infourl to be stored ( mbabker )

    Resubmit of #114 post-repo sync As part of a change I would like to see in the Extension Manager's Update view, I would like to be able to display the infourl from the update stream on the view. This would be more relevant to the user as it would most likely point to a release notification, changelog, or other resource the user should review prior to updating versus displaying the URL of the update stream. Parallel CMS Feature Request - http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=26475

  • #117 ] System test failure fix ( elinw )

    Correct fatal error when a category id of 0 is passed in; this was exposed as a problem with system test failurs on the CMS whem there was a failure to get the module params correctly. With this hange fall back to default works.

  • #127 ] Merge uncaught changes from Joomla SVN trunk. ( eddieajau )

    Merging changes mainly from Installer package but other minor errors found testing 1.7.

  • #122 ] Fix reference o an image in the CMS ( elinw )

    Remove hard coded refernce to bluestork

  • #126 ] Fix up unit tests. ( LouisLandry )

  • #118 ] This is a cms catchup commit for issues 25696 and 26284 As part of ( elinw )

    solving a problem with updating the maximum time was bumped up for zip. However some shared hosting does not permit this and that can cause warnings. Therefore @ is added to supress warnings when this option is not available. Original report and patch for 26284from Brian Towles.

  • #123 ] Jinput ( ianmacl )

    bah. Fixed target branch.

  • #103 ] JForm Telephone Rule ( AmyStephen )

    defined('JPATH_PLATFORM') or die; was commented out

  • #109 ] Fixing unit test issue ( ianmacl )

  • #108 ] Missing bracket ( elinw )

    Missing bracket

  • #107 ] Logging and tests ( elinw )

    As logging to test harness

  • #102 ] Add optional context to JHtmlContent::prepare ( mbabker )

    See CMS Bug Tracker -> http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=26421 This adds an optional context to JHtmlContent::prepare so that in all instances where this method is used to run the onContentPrepare event, a non-generic context can be passed to the event. This will allow developers to better check the data their plugin's event has received to verify they are not accidentally processing data they do not intend to handle. There are no backward compatibility issues as this variable is optional and defaults to the already hard coded context.

  • #105 ] Logging ( elinw )

    Starting work on making sure logging is happening in all deprecated methods and that nothing is marked for removal before 12.1.

  • #101 ] Docblocks ( elinw )

    Some more work whenever you are ready.

  • #106 ] Fixed subclass detection code ( ianmacl )

    instanceof doesn't work for this particular use case.

  • #93 ] Make getTable fill in the prefix like JController::getView ( rvsjoen )

    When using tables in extensions, the default JModel::getTable() method does not automatically include the extension name, instead it uses the prefix 'Table' to for the table to automatically load using getTable it has to be named TableHelloworld and not HelloworldTableHelloworld.

  • #91 ] [#26241] JCacheFIle should not use JFile calls at all ( chdemko )

    Moving from the CMS tracker http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=26241

  • #94 ] Redirect workarounds ( rvsjoen )

    Remove old workaround for webkit browsers, and make the workaround for msie more targeted. Older webkit browsers will still work, but take a performance hit, however I think it is more important to get rid of workarounds. https://groups.google.com/forum/#!topic/joomla-dev-framework/8DPWgYnsSQs http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=26335

  • #100 ] Code cleanup ( elkuku )

    Removing unnecessary empty braces when instancing a new class. Makes the code more readable (i think), reduces download size, helps to save the planet ;) Maybe this is a good time to apply those "cosmetics"

  • #43 ] Improve JRegistry ( chdemko )

    See http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=24472

  • #98 ] Consistent phpdoc subpackage in updater ( rvsjoen )

    Some files in the Updater subpackage are tagged with "@subpackage Update", this makes phpdoc create two different packages for the updater. This patch makes consistent use of "@subpackage Updater"

  • #92 ] Fixes a mistake in mysql and mysqli drivers ( elinw )

    Change concat to concatenate as per mailing list discussion. https://groups.google.com/d/topic/joomla-dev-general/ljR_QkrxEKE/discussion Parallel patch posted in cms tracker

  • #86 ] Catch up commits to CMS ( elinw )

    CMS commit 21571

  • #84 ] Catch up commits to CMS ( elinw )

    CMS Commit 21479

  • #83 ] Commit from CMS that is not in platform ( elinw )

    CMS commit 21442

  • #81 ] Strict standards ( elkuku )

    Strict standards: Calling a non static method statically Also removed 1 unnecessary line

  • #82 ] Code Cleanup ( ianmacl )

    Fixed code to meet standards.

  • #80 ] Sync some changes from Joomla 1.7. ( realityking )

  • #78 ] DBQuery fix that fixes the CMS Installer's use with 11.1 ( AmyStephen )

  • #76 ] Ci ( ianmacl )

    Some changes to get better reporting in CI.

 

In a reorganising of the Joomla! web properties, the PLT has decided to close down the Joomla! User Experience website (https://ux.joomla.org). This news isn’t really new news. Discussions about moving the JUX forum started in 2013 but the steps necessary to move and shut the forum down were never completed. Is the Production Leadership Team still interested in a Joomla! user’s experience? You can bet it is!


JUX is closing

Many of you may have noticed the message "Please note: Due to technical reasons we have had to disable the Install from Web Service. We are working to get it back online as soon as possible. To find extensions please use the Joomla! Extensions Directory at http://extensions.joomla.org"

Install from web


Status of the Install from Web

After an extended period of silence, the Production Leadership Team is happy to announce that we are moving forward with planning, preparing, and ultimately releasing version 2 of the Joomla! Framework. Over the last several weeks, we have begun building a roadmap and vision for the next major version of the Framework and are now ready to share with the community for review and feedback.


Framework v2 Roadmap

We recently received an email from google webmaster tools with the subject line: Hacking suspected: http://joomlacode.org/

Unfortunately, it appears that joomlacode.org is infected with content spam. When we realized this, our only concern is to protect our users. This will involve taking down the service in the very near future. This is an inconvenience for project owners using JoomlaCode to host projects for, and we are truly sorry.


JoomlaCode is closing

Happy New Year from all of us on PLT! We have been busy over the holiday testing, and re-testing Joomla 3.4 alpha. We are delighted to announce we will release Joomla 3.4 beta, January 27th 2015.

We are grateful for all the feedback we received from those who took part in our recent alpha release. This extended alpha phase allowed us to drive attention to testing and creating patches.

All new features contributed to the project will be considered for Joomla 3.5. Features already submitted will be reviewed for the 3.4 release.

Updated Timeline

The following updated timeline is established for the 3.4 release:

  • January 20th 2015 - 3.4 Feature Freeze
  • January 27th 2015 - 3.4 Beta 1
  • February 3rd, 2015 - 3.4 Beta 2
  • February 10th, 2015- 3.4 Release Candidate
  • February 17th, 2015 - 3.4 Stable Release

Joomla 3.4 release timeline update

Joomla! CMS

Current Release 

View known Issues

Development Status

Nightly CMS builds for developers are available for download

Joomla! Framework

Joomla! Reading

Joomla! Programming

Joomla! Programming

Mark Dexter & Louis Landry
Joomla! Templates

Joomla! Templates

Angie Radtke