The Joomla! Community Portal ™

Community Blog





Closing Issue 8369
Written by Elin Waring   
Monday, 07 July 2008 03:46

For a long time the oldest unresolved issue in the tracker was # 8369 "Issues with Page Title and Menu Item Layouts." It went into the tracker on December 12, 2007 and  and was actually based on a forum report from June 2007.  I look at the oldest issues in the tracker pretty regularly and this one was really bothering me. Leandro Bergantiños had done a tremendous amount of work just to write the report which makes it just the kind of report that is usually easy to deal with. In the forum Johan said it was important for it to be dealt with before RC2 and then according the the tracker Louis was going to deal with it in January, so plenty of coding power there. Why wasn't it fixed?

So, I decided to really try to understand what Leandro was showing with his spreadsheet. It took me a while to understand what he had discovered. It turned out that there was a tremendous amount of inconsistency in how the menu title parameters were  being handled. In some cases they were being completely ignored.

So then I thought that maybe the issue had been fixed piecemeal, and it was the case that there were a number of reports about issues relating to titles and specific types of menu links. So I recreated Leandro's spreadsheet by looking at each core menu link type. Wow did that give me an appreciation for the work Leandro had done. There are 25 core views and each one had to tested with the 4 possible combinations of "Show Title" (yes or no) and Page Title (blank or not blank). And you had to look two places, at the page title and at the browser or blue bar title. Strangely enough, not that many people volunteered to help me with this.

Once that was done, I realized that before any code was changed what was actually needed was to decide what the intended behavior was. This is an issue that is really important to people like me who are webmasters, but maybe not so very interesting to others, so for a while I felt like I was waving my hands and no one was paying attention. Except, Ian was, so finally I had someone to discuss it with. We looked the spreadsheet over together and came up with some proposed rules. For example, when Show Page Title is set to no, no title should show on the actual page.  Also, when text is entered in the Page Title field and Show Page Title is set to yes, that text should be used.  When the page title is shown, the browser title and the page title should be the same.

Then Ian began to look at the code. Well to make a very long story short, the final patch file has 1199 lines in it. Creating that was a huge job and Ian should get at least an extra week's pay as a bonus for doing it. :)  Third party developers will want to look at that file to see how to make changes so their components behave in the same way as the core components.

Then JBS started testing like crazy. Again, this was really time consuming because of the 100 possible combinations of links and parameters. Thanks especially to Amy for helping with this multiple times as fixes were made to the patch.

Then, we thought we were done, but we realized that because some of the layout over rides in Beez and JA Purity used the old code, we had to decide whether to make changes in those. The whole point of a layout over ride is that a designer can change how the parameters (among other things) work. After some consultation with Jennifer who besides bug squading spends a tremendous amount of time moderating and helping people in the template forums, we decided that they should behave in the same way on this as the core.  So, off to make two more patch files, test them, and we were finally done.

Never was I so happy to see an issue marked "Fixed in SVN."

Amazingly, the next oldest open  issue (9701) was submitted February 10, more than two months after 8369. Wow.

Thanks to everyone who helped to put this one to bed.







We baked new pizza, and it's name is Naiki
Written by Wilco Jansen   
Sunday, 06 July 2008 22:55
So close to the holiday season, and so many people helped out during the second Pizza Bug and Fun event. Let me start by thanking all contributers that helped out during both weekends, we solved numerous issues and also some documentation was written. Best of all is that Airton Torres, Arno Zijlstra, Ben Cessa, Esban Bahnsen, James Anastasios, Jeetu Kataria, Omar Ramos, Robin Muilwijk, and Witchakorn Kamolpornwijit joined the Bug Squad and that is simply mind blowing!

During this PBF event we saw more people joining in remotely this time. There where also venues reserved by people. Italy (Ravanna), United Stated (New York, Atlanta and New Orleans), Netherlands (Wijhe), Canada (Vancouver) and Australia (Sydney) where some of the locations that joined in. As with the previous PBF event collaborating with so many people remotely still amazes me. This cannot be done without proper preparations, and for that I want to thank the Pizza Couriers for the very good work on the preparations.

All of this has lead to another stable release. The newest Joomla! version 1.5 will be named Naiki (version 1.5.4) and could not be released that fast without the help of all volunteers of the second PBF event! Keep an close eye on the announcements on the website, this version is around the corner :-D





CS Teachers and Me
Written by Elin Waring   
Saturday, 05 July 2008 13:39

Last Saturday while lots of people were working on issues in the tracker as part of PBF, I was giving a talk to computer science teachers in San Antonio, Texas at the CS/IT symposium. It was a great coincidence that PBF was going on at the same time since so many students were making important contributions by fixing bugs and creating documentation and my talk a was all about how encouraging their students to participate in free and open source software projects would help them learn computer science.

It was a great event, and it was great to meet so many passionate teachers.  I was stunned to learn that the number of college computer science majors in the United States has been declining. Well, I hope Joomla! can help do something about that, whether through GHOP or just by having a community that is welcoming to students. It was also fun for me to combine my interest in pedagogy with my interest in Joomla! :).

My session had a full house with lots of knowlegable people. The focus of my talk was on how participating in a real project, with hundreds of thousands of users and in which you have to work in a collaborative manner can teach things that are hard to get out of even the best book. It was so hard to chose, but I highlighted two GHOP projects, Marieke van der Tuin's Digg module and Michael Casha's  Narellan Rural Fire Brigade website and the report he wrote on it. I said that I thought these were reasonable kinds of projects for high schools students to undertake.  I also talked about how Miarieke and Michael have become such important contributors to Joomla!.

So why am I posting this in the bug squad blog? Well, we do have a lot of high school and college students in th JBS and we would love to have more. So, come on and join us.

 Here are the slides from my presentation. Thanks to the Computer Science Teacher's Association for inviting me to speak and Leslie Hawthorn from Google for putting them in touch with me.







7 Myths to voting and reviews on the Joomla! Extensions Directory
Written by Ben Rogers   
Friday, 04 July 2008 13:26


What does it take to get your opinion of an extension onto the rating system?


This could be something that is floating in your subconscious whilst you frantically type away, submitting your welcome opinion on an extension you have just installed on your joomla! website. You have now typed up your review, voted for your favourite extensions and after a few days, you realise that only half of your reviews have been approved!


Being apart of the JED administration team, we respect and welcome all reviews and votes whole heartedly, although some measures must be put in place to reflect the utilitarian view we strive to incorporate into the integrity of the Joomla! extensions directory. Lets take a look some scenario's on how when we will approve ratings, voting and reviews.


1. Questions vs Reviews


Have you recently installed a new extension on your site, and found that it does not work or there is some feature of the extension which you can't figure out? This is a constant question we are presented with in the reviews section. Questions about the extension will not be published in the reviews section. These enquiries should forwarded to the developer. If you feel there is no response to an extension and it is in violation of the joomla Listing Rules report so or state the error within your review. The JED team will promptly adhere to your response. Just remember you are helping us keep the integrity of the Joomla! extensions in order!


2. Can I vote for my own extensions


Joomla! developers may not vote for their own extensions. Once you have released your extension through GPL or commercial licensing the popularity and stability of your extension will be decided through the voting system by the community.

3. How do I know if the voting on my extension is honest or a fallacy!


This is a question that the JED team takes very seriously. The directory is the centre for joomla developers to promote their products. For many developers the Joomla! extensions directory is the sole source for traffic to enable them to sell or release their extensions.


What does this have to do with voting and why is this of such importance?


When viewing a Component, Module or Plugin, nine times out of ten, people will base their decision for downloading the product on the previous votes of fellow community members. The voting and authenticity of the votes will be extensively and painfully monitored by the JED team to ensure that competitors are not voting down other peoples extensions whilst promoting their own. This creates a balance which is viable for the joomla guidelines.

4. Hey! how come my extension was not approved!


First of all we would like to say that we we appreciate, value and welcome all extensions. These are the pieces to the puzzle that makes joomla! what is is today. Before an extensions is published the team will firstly check the download link, install the extensions and check that it works on the platform the developer has specified when he has submitted it to the directory. Once everything has been verified, we will approve the submission.

5. Wait a second! I checked my submission everything works and my download link is valid, why is it not approved!


Once your extensions has been tested and prompted for approval, the last step we will take is checking the validity of your website. There could be one minor problem, your extension could work perfectly but your website may have some implementations which does not fit is so well with the joomla! collective community and rules.


Extension Download Websites should not have


  • Adult Material
  • Modifications of the joomla! logo
  • Modifications of the joomla! font type in relation to the logo
  • Explicit swearing or pornographic images
  • Misleading download link areas


6. I have just taken over the development of an extension which was GPL/GNU licensed. I think I might release it as a commercial extension?


This happens frequently, developers create an extensions and it changes hands to another developer.


In this instance lets look at a few factors


Originally the extension was developed as an open source GNU/GPL extension, the reviews and votes tied to this extensions were based on these facts. The corollary would be that they should stay with the original developer based on his preference in releasing the extension.

In such instances the original version of the extension will be unpublished. The JED team will contact the latest developer to submit the extensions again. We feel that in changing the licensing for an extension this should entail providing a clean sheet for voting / ratings for that extensions. This ensures the joomla! community is not mislead by previous statements for the GNU/GPL licensed extension.


7. This extension does not work and the website provides no support?


As the Joomla! extensions directory grows, developers will stop developing a product or it may become outdated. In this case submit your review or report the directory listing to an administrator. We will review the extension and make sure it fits within the joomla! Listing Rules. If the extensions no longer works we will unpublish it await a reply from the developer.






JoomlaCode Maintainence - 5th July, 2008
Written by Sam Moffatt   
Friday, 04 July 2008 12:07

JoomlaCode is scheduled for software upgrades for three hours at midday GMT on the 5th July, 2008. This is get JoomlaCode up to date and provide some performance improvements. Additionally we will be performing some limited database maintainence as well following the success of the maintainence completed earlier in the week.

Check out for more information about the downtime and any further notices related to this down time.

Check out for up to date information on down time related to JoomlaCode.


Page 131 of 137