The Joomla! Community Portal ™

Community Blog





The best ingredients for a nice Pizza
Written by Wilco Jansen   
Friday, 20 June 2008 21:17

We're very close to the second Pizza, Bugs and Fun (PBF) event. As you might have noticed, we have extended the PBF event for a second weekend and now have participants from almost every continent. If you are able to join us at one of these venues, we would love to have you. If you can't come to a venue but you still want to help, you can just sign in from your location.

Joining in is fairly easy but only Bug Squad members have access and can manage the tracker. We might consider opening it up for the PBF event, but somehow we think that will become a major mess ;-) Like the first PBF event, we set up an easy way to join the PBF participants. When you arrive in the pizza shop, check into the Bazaar by doing these things:
  1. Sign on to the IRC channel (#joomlapbf on freenode) and introduce yourself to the others. Never used IRC? Learn more here and here.
  2. Join in the discussion and get to know everyone. If you have any questions, feel free to ask! At any point, if you have questions, this is where to ask!
  3. If you plan to help with testing bugs or creating patches, register on JoomlaCode so that you can add comments to the artifacts.
  4. You also need to register on the shared Google Document. When you want to get registered, please ask in IRC and the PBF team will contact you to get your e-mail(g-mail) account.
  5. If you plan to assist with documentation, register on so you update to Wiki.





Creating the Crust for your Pizza
Written by Jennifer Marriott   
Thursday, 19 June 2008 22:30

I am so excited about the Pizza, Bugs and Fun event that is coming up that I though I would share with everyone some info to help get themselves set up and ready to participate.  There are only two main ingredients that you need.  The first is a local server environment.  The second is an SVN client.  Don't think it is too big a slice to take on.  Dig in.

Local Server Environments

A local server environment is basically a web server that you run on your local computer. Lots of people test on live web servers, but you don't have to test on a live server to participate.

WAMP - (Windows, Apache, MySQL, PHP)
For general information on what WAMP is you can check out their Wikipedia entry:, and you can compare different WAMP software on Wikipedia also:
You can find FAQs and Installation help here:

MAMP - (Macintosh, Apache, Mysql, PHP)

MAMP at Wikipedia:
MAMP by living-e AG:
You can find FAQs and Installation help here:

XAMPP - (Multi OS, Apache, MySQL, PHP)
XAMPP Project:
You can find FAQs and Installation help here:
XAMPP is available for Linux, Windows, OS X, and Solaris.

XAMPP is the one I use on both my Mac and Windows systems, but I also like WampServer on Windows.

SVN Clients

The next ingredient for excellent pizza is to have an SVN client. This will allow you to keep your testing Joomla! files up to date as changes happen.  It will also allow you to test patches easily. Wikipedia has an excellent page with information as to what SVN is and how it is used:

EasyEclipse is a good choice for Linux, OS X and Windows:  Nur Aini Rakhmawati has an excellent video tutorial on using JoomlaCode SVN with EasyEclipse here:

Another Windows choice is TortiseSVN:  It is available for download here:  You can find support manuals and FAQs on their site.  Details on how to work with the JoomlaCode repository are located on the Developer site:

With these tools you will now have the foundation or "crust" for your pizza.  Have fun!






What it takes to bake a pizza
Written by Wilco Jansen   
Saturday, 14 June 2008 23:46

Some will think "Why should I participate in the Pizza, Bugs and Fun event? Why not just let others fix bugs and write documentation for Joomla!?" After all, you likely have too many responsibilities in life, as it is. Perhaps you don't see yourself as someone who has the kind of talent needed to help the Joomla! project. Maybe you really would like to help, but you have no idea how to get started. If you are thinking this way, you are not alone. In fact, those are typical reasons people do not participate.






Written by Elin Waring   
Saturday, 14 June 2008 10:41

Test this patch, make a patch, are things you hear when you report an issue or when you're working on bugs. What exactly is a patch?

A patch is a file that indicates which exact lines in which exact files should be changed.

Here's a recent patch from issue 11354 which corrected a simple typo.

Index: plugins/authentication/gmail.php
--- plugins/authentication/gmail.php (revision 10386)
+++ plugins/authentication/gmail.php (working copy)
@@ -87,7 +87,7 @@
else {
- $message = 'curl isn\'t insalled';
+ $message = 'curl isn\'t installed';
if ($success)

Looking more closely, we see that the patch always starts with the name of the changed file relatiive to the Joomla! root. In this case it is the file gmail.php in the plugins/authenticaion folder.

Next we see the file named again in two lines. The number in the first line represents the version of the code base or build on which the patch was created, The working copy is the copy that is changed. What do I mean by build? Every time a change is made to he codebase, that creates a new revision or build. You can find your build number in the changelog.php file in your joomla! root.

Next comes @@ -87,7 +87,7 @@ which tells us that the change will starton line 87 of the file.

Finally we see the code. The old line 87 has a – in front of it and the new line 87 has a +.

The new version of the line will replace the old line in the file.

Of course most patches are much more complex than this, but they really just are repeated instances of this structure.

So if you saw this patch file and wanted to fix your version of Joomla! all you would need to do is find line 87 of gmail.php and make that change. So if someone tells you “There's a patch on the tracker” what they are saying is that you can go download the patch and apply it to your version of Joomla!. However one thing to keep in mind is that if your version does not match the version in the code repository it is possible that that patch will not work because it depends on or impacts other parts of the code.

Now, if you're contributing a bug fix  as opposed to just reporting an issue, the ideal is to submit a patch file that you have tested. However, if you can't do that, at least give this information:


  • The complete names and paths of any files changed
  • The line numbers of the changes
  • The old and new versions of the changed lines


However, making a patch file is even better and  is not complicated if you install a subversion client such as Tortoise or the Subclipse plugin for Eclipse.






The Bug Squad Meets Unit Testing
Written by Anthony Ferrara   
Friday, 13 June 2008 02:51

The Joomla! Bug Squad has been going strong for about five months now, and things couldn't be better. For the most part, we've been using a manual testing technique, simply because it's fast, easy, and flexible. We've had a few people interested in unit testing, especially for maintenance procedures, but for the most part unit testing hasn't caught on.

Okay, I'll admit, even I was skeptical about the value of unit testing. I knew it had benefits, but I really wondered if all the effort required to build unit tests was really worth it. Then, I encountered an issue with JCache. The patch was an easy fix, but I had no idea how to test the patch thoroughly. Then, it occurred to me that perhaps this was a good candidate for the famed unit tests!


Page 131 of 134