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.

 

Dear Joomla Extension Developers

We need your to help spread the word!

We are currently planning the Joomla 2.5 marketing campaign. Joomla 2.5.28 is scheduled to be released on December 10th. As part of our campaign, we are asking extension developers to write a blog (of any length) that explains 2.5.28 will be the final release of the 2.5 series. Additionally, it would be helpful for your users if you provide documentation on how to upgrade your extension within your blog post.

Here is documentation by Jennifer Gress, Tom Hutchison, and Connie Lippert to help people plan for upgrading http://docs.joomla.org/Why_Migrate. The marketing team is preparing an information pack that explains 2.5.28.

Our goal for this campaign is to work together to help the community find the resources they need for successful upgrade planning. If you have suggestions on how else we can assist in this transition, please post here


Joomla Extension Developers, what resources do you need for the final release of 2.5

The Joomla! Production Leadership Team (PLT) is responsible for leading and coordinating the development of the Joomla CMS and Framework. This includes releasing new versions, fixing bugs, adding new features, and creating documentation and translations.

We are looking for your nominations for new PLT members. We acknowledge that the greater worldwide Joomla community can help us a lot in this election process, and make us aware of potential candidates we might otherwise overlook.

Although the nomination form is available permanently to continuously gather suggestions, a number of PLT members are stepping down this month and we are additionally looking to fill some gaps in our skills base.  Consequently we are blogging this reminder that we need your nominations because we are actively looking to recruit new PLT members soon.

You can nominate yourself or someone else at any time. If you nominate someone else, please ask them first if they are interested and have the time available.


Call for Production Leadership Team Nominations

While we strive to be as efficient as possible, there are times when things don't go smoothly, causing stress and headaches for our user base and the community members who test and prepare our releases. This last week has been an example of some rough times for our releases, and though no single person or group is to blame for any of the issues that we've experienced with these last releases, they do highlight areas where our teams and workflows can improve.


Release Postmortem

The Joomla PLT is happy to announce that contributions to the CMS will no longer require a JoomlaCode tracker item. We’re now ready to start using our brand new issue tracker issues.joomla.org.

New bug reports and feature requests should be created either at issues.joomla.org or directly on GitHub. Code contributions made via Github will automatically create the issue for you (no more duplication required). All outstanding JoomlaCode items will require a corresponding Github issue.

Due to technical limitations of the JoomlaCode software, we cannot disable the JoomlaCode tracker for just the Joomla CMS project. We ask that contributors stop using it immediately to create new issues or comment on existing issues. We will make all the necessary process changes to reinforce that.

NOTE: This change will not have any impact on other projects using JoomlaCode.org.


Easing the contribution process

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

Current Release

Legacy 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