A few days ago Joomla! platform version 11.3 was released. More and more people are wondering what Joomla! platform is about. The following article is a chapter of the upcoming Joomla! Development Beginner's Guide which will be released as a free pdf as soon as possible. The term Joomla! platform is quite new. It was introduced with the release of Joomla! 1.6 in January 2011.
If you think this involves a teaspoon and a spirit lamp, take your F and go home. Git's "rebase" command takes advantage of the distributed nature of git to enable you to do some really useful and creative things in your repository. Of course, like all power tools, rebase can be abused. Let's take a closer look at what can be done through rebasing, and where and when you should use it. This article assumes familiarity with software version control systems in general, as well as a basic familiarity with git itself. While it does explore some git fundamentals, it is not intended to be a primer on git usage.
Joomla 1.5 has several sort orders defined to arrange the articles in a specific sequence for displaying in the blog and list layouts. The sort orders are primarily based on the created date, title, hits, and pre-defined order of the articles. There may be situations where one would like to see a combination of articles in the order that has been recently modified and/or created like the option View New Posts in the Joomla forums. Currently, there is no sort order available to handle this situation. This paper discusses about how to implement this new sort order, Recently Touched Date.
If you are a professional site builder, but not a professional developer, then you have likely wished you could quickly build custom Joomla! extensions that would allow you to collect exactly the data needed, presented in the precise manner, as required by your client.
While at JAB11 in May, I heard comments from more than a few developers that it could be difficult to get their code accepted into the Joomla! core. So I committed to publishing a JCM article to try and address those concerns. In the first article of this two part series, I gave an overview of how the existing development process works. In this month's article, Mark Dexter and Louis Landry from the Joomla! Production Leadership Team have responded to questions about the development process that were submitted by other developers in the community.
I'm a firm believer that it's the simple things in life that matter the most. I feel the same way about web sites, software design and development. I find that developing simple solutions which solve complex issues can be a good challenge. One of the biggest challenges one faces when creating "simple" is figuring out where simple stops and where complex starts. It's really a case of learning to tell yourself ‘no’, and that's very hard to do.
While at JAB11 last month, I heard comments from more than a few developers that it could be difficult to get their code accepted into the Joomla! core. So I committed to publishing a JCM article to try and address those concerns. In the first article of this two part series, we will take an overview of how the existing development process works. Developers are encouraged to post their questions and comments below this article throughout the month of June (the earlier the better), so that some of those questions and comments may be used as the basis for next month's concluding article in this series.
When it comes to creating an extension for Joomla — or any type of software — documentation will always be an important part of that extension’s success.
Joomla is a decent CMS with very nice features. It works great for the end user and has many components ready to use from the online world. What I don't like personally, as a developer, is the model implementation in Joomla. For me the way ' model and table' classes are implemented, just doesn't feel right to me. Also it is very difficult to get other models in a controller or an other model class. With Symfony I have worked with Doctrine regularly and in this blog I'll show you how to use Doctrine for your own component in Joomla. Doctrine is an Object Relational Mapping framework and offers you a persistence library. This not the holy grail and you should determine if you need the extra overhead and if you are comfortable with it.
By accepting you will be accessing a service provided by a third-party external to https://magazine.joomla.org/