The importance of filtering and sanitising input in a web based application cannot be overstated. The Joomla Framework provides a class called JRequest to fulfill this very important role.
The key to successfully developing in Joomla 1.5 (and it’s significant advantages over 1.0) is the Joomla Framework. While other frameworks such as Zend, phpCake and others attempt to be general frameworks on which you can build an application, the Joomla Framework is specifically targeted at being suitable to build a web-based Content Management System (although it is certainly possible to build other types of applications).
Login boxes can take up valuable space on your web site, or just detract from the overall feel of the site. A popular technique for addressing this problem is to show a modal popup login box. The idea is that you replace the page hungry username and password fields with a “login” link that, when clicked, opens a modal popup login box. This can all be achieved out-of-the-box with Mootools and Joomla layout overrides.
This execution trace begins with at the User Component Controller method for login,
UserController::login (called within the application dispatch method)
Joomla general development
When you start out as a Web site designer or developer, managing sites on your local workstation is not too hard, but as the workload increases, and other consultants and contractors become involved, things get more complicated. How can everyone deploy the same staging site? How can I get my work back which someone else just overwrote? What do you do when the client comes back to me 18 months after the project has finished and asks for a copy of the site because they accidentally deleted a few files and you’ve misplaced them yourself? One way to address these questions is to store your projects in a source code repository. There are several different types of repository available but this tutorial will focus on using Subversion (SVN) and how to store the minimum amount of information to conserve repository space as much as possible (because, after all, space is money).
Layout overrides are a powerful feature in Joomla 1.5 but they can be used for much more than creating semantic, accessible markup, or for moving content fields around the page. Since we have access to the rest of the Joomla Framework API in our layouts, we have the option of pulling in either individual modules, or a whole module position. This can be used for any number of purposes such as for advertising banners or displaying modules only in articles where you’ve given up on trying to get them to show on the correct page all of the time. In the content component, you can do this on an Article layout, but you could also do it for the Frontpage layout (have modules loaded between articles), or the Section or Category layouts just to make them a bit more interesting.