My first car was a Geo Metro and to save a couple bucks I would change the oil on it myself. It's not hard to do, however I didn't have any real tools beyond a crescent wrench and a robo-wrench. I would try not to strip the plug in the 6 inches of space under the car using the crescent and then catch the oil in milk jugs that I sliced the tops off of. Then, I would attempt to unscrew the filter with the robo wrench. This had a 50-50 chance of mangling it and spilling oil as I torqued it. These tools made the job a 45 minute trial where I would bloody my knuckles, get covered in oil, and end up cleaning puddles of it off the street. Eventually, I wised up and bought a ratchet set, an oil wrench, and a pan to catch the plug and all that oil. The difference was magical: it became a 15 minute job without swearing, blood loss, or environmental catastrophes. And it was all because I used the right tools.
There are terabytes of poorly written code in the Internet's Joomla population. This is because of the nature of Joomla as an extensible application. It's wonderful because anyone can create a solution for it and it's horrible because anyone can create a solution for it. Because Joomla sites interweave the efforts and knowledge of hundreds of developers across space and time the highest virtue that its code can aspire to is cleanliness. If you've never heard of code referred to as clean, what it boils down to is simply code that is easy to read, write, and maintain. In this article, will look at why elegant code should be avoided and three simple principles to writing good, clean, Joomla code.
If you are reading this post, chances are your website is running with an ancient version of PHP. You are not alone, PHP version 5.3 is used by 31.1% of all the websites and 5.4 has 29% share. Both of this PHP version already reached end of its life and no more security update will be provided. That means, you are already in big security risk!
My company worked on a web application that was basically an extension of the Joomla 2.5 core a few years ago. We took over the app from another development company that had gotten stuck (we never would have modified the core.) It was being deployed to AWS and the original developers altered the configuration.php file to return different values from their local environments based upon environmental variables set by Amazon's cloud servers. When I saw this I thought, "There has got to be a better way."
University students from many parts of the world will spend the summer break ("winter break" in some countries) writing code and learning about open source development. Joomla! is one of the selected mentoring organizations in Google Summer of Code 2016 (GSoC 2016). Does it mean that students will be coding to make Joomla! even better? Yes! And we invite you all to join us in the GSoC 2016 journey.
Joomla 3.4.4 is scheduled for release on Monday 7th September and a release candidate is available for testing. Each time there is a new release, whether its a bug fix release or a new feature release, you will always find people asking "have they fixed this yet?" or complaining that "this bug that has been there for years" has still not been fixed.
Last month I described how a new feature was developed to count the number of articles in each category. At the end of the 2nd day of JoomlaDay France 2015, the feature was working… that is, it counted all articles (for com_content) in the Category Manager for Articles. I got it working by adding a hard-coded “if extension = com_content” check in the Category Manager. That’s not a solution but a workaround, I was fully aware of that.
How does a new feature end up in Joomla? This is a story about how a new feature is developed and how it might get into a next version of Joomla. From conception, to development, to community feedback & help, to testing, and (hopefully) to adding it to the core code. The story you are about to hear is true; only the names have not been changed to credit the people who helped me out.