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.

 

Ok, so there’s been some questions about Joomla 3.4, the next big release for Joomla. I’m quite excited to be able to be a part of this release and we have some great things planned. Timelines are always the first thing people want to know; followed closely with what features will be available. In this particular release there are some additional new terms being used which may be helpful to define. Three quick topics, let’s discuss each in order.


An Update on Joomla 3.4

Have some questions that you’ve just got to get answered? The chances are good we've already done it. Check the FAQ below:

For those who love detail - you can see the full development strategy here

For those of you who want the quick, simple to understand overview - read here.

Q: Will 3.5 be the LTS release for the 3.x series?

A: No. The strategies have been modified to not lock in a specific release as the LTS release of a series. Under the revised strategy, unless superseded with a newer minor release, there will be at least two years of support for the last minor release of a series. The concept of an LTS release is being eliminated in favor of this. For example, if 3.4 were to be the final minor release of the 3.x series, it would be supported for at least two years after its release.


FAQ's for Joomla's Improved Release Cycle

Have questions? You can ask us on Twitter

To help answer questions of the development and release cycle of for Joomla 3, we've created a twitter account to help! Ask a question to @askjoomla by sending a tweet. Questions will be updated here  daily so you can keep your Joomla! businesses running smoothly.

1. Introduction

This strategy document sets out what the community of Joomla users, from ordinary non-technical users through to high-level technical developers, can expect from the products that come under the umbrella of the Joomla project.

This is primarily about how we approach and manage change: how we adapt, develop and grow our products in an ever-changing technological landscape; how we communicate to our users and contributors what to expect from our products as they change from one release to the next; and how we guide our contributors towards making the future changes that we want as a community.

The stakeholders in our project have widely varying needs and a balance must be struck between, at one extreme, those for whom any change is unwelcome and all shades to the other extreme of those who thrive on continuous change. Change is essential if our products are to remain relevant to their intended users, so our goal is to manage that change in such a way that we minimise the disruption it can cause.

Since the Joomla project is responsible for more than one product, this strategy is written to be as generic as possible and to allow new products to be added to our portfolio without forcing any extensive re-writes.

This strategy builds on the substantial practical experience of a lot of people over the many years since the project's foundation. The reasoning behind what is written here, and the lessons learned in leading up to it, is outside the scope of the document itself and reference should be made to other sources for that commentary.


Joomla! Development Strategy

Joomla! is a dynamic community driven project and we are always striving to improve and adapt to the changing world of the Internet. We care about long-term stability. We care about adapting to change. We care about providing a solid platform you can be confident in and rely on.

After receiving feedback from the global Joomla community, we are improving the release strategy so that we can better meet our shared goals.

For those who love detail - you can see the full development strategy here. For those of you who want the quick, simple to understand overview - read on.


Joomla! Improved Release Cycle: For the People by the People

The Production Leadership Team (PLT) is pleased to announce that there will be a 3.4 release of the Joomla! CMS, which is planned to be released on July 15, 2014.


Announcing Joomla! CMS 3.4

LTS Release

STS Release

Note: View known compatibility Issues

Current Release: 1.1.0

Upcoming Release: 1.2

Joomla! Reading

Joomla! Programming

Joomla! Programming

Mark Dexter & Louis Landry
Joomla! Templates

Joomla! Templates

Angie Radtke