Editorial Reviews:
DETAIL DESCRIPTION If you're developing a content management system in PHP 5, there are times when you simply have to roll-your-own, for whatever reason. In those situations, this book will be invaluable. If you're looking for an inside guide to putting together the working framework of a flexible, robust content management system in PHP 5, this book is for you. As a former development team leader on the renowned Mambo open-source content management system, author Martin Brampton offers unique insight and practical guidance into the problem of building an architecture for a content management system. Following the scene-setting first chapter, each chapter in the book tackles a different aspect of developing the author's new Aliro PHP 5 CMS framework, with: . A concise statement of the problem . Discussion of the important design issues and problems faced . Creation of the framework solution The framework is built on a strongly object-oriented architecture throughout, including adherence to MVC principles, and you will learn how to create classes for handling such things as menus, modules, components, sessions, and user tracking.Administration and security issues are discussed as an integral part of the design and implementation of framework features. The final chapter discusses the key issues that affect a wide range of specific content handlers and explores a practical example in detail. You will learn about: . The general characteristics of systems to create websites . Effective coding and object architectures to fully exploit PHP 5 . A foundation for database processing to ease further development . Technical functions such as handling sessions, caches, errors, XML, mail, and files . Management of website users . Flexible, practical deployment of role based access control . Internationalization . Handling extensibility beyond the basic framework . General concepts of menus without prior commitments to detail . Delivery and presentation of different kinds of user-oriented content Approach The book includes extensive discussion of the design issues, and how to overcome them in the framework. Each chapter of the book focuses on a particular requirement of the framework. The book will not present the total code for the framework, showing only the parts that raise critical design or implementation issues.For these, detailed explanation is given, leaving the less problematic parts to the code download itself
Customer Reviews:
 should "Aliro" also have been in the title ?
Perhaps "Aliro" should have been in the title? It is the name of a CMS written by the author in PHP5. The entire book can be considered as a case study in how and why to use PHP5 for writing web applications. As opposed to perhaps using PHP4 or another server side scripting language.
The book delves into detailed aspects of Aliro and how it can be customised by you for your particular CMS needs.
En route, Brampton also offers good, general advice about programming, not necessarily even restricted to PHP5. Consider patterns as one example. This is now a dominant paradigm amongst many programmers. He does not argue against patterns or their merit, but cautions that an overdependence might ironically constrain your thinking and subsequent design in ways that avoid finding an optimal solution. I don't recall any recently published book that I have read which even goes so far as to circumspectly say this caveat about them.
Another item of good advice is to warn you against letting your PHP code run dynamically generated code (using "eval"). Dynamic code has a nice conceptual allure and is indeed powerful. But especially when such code might include user supplied input, and where, remember, the code is being run server-side, then there are huge security problems. Don't even think about using dynamic code.
Also, we see that Aliro uses Role Based Access Control. Mostly by partitioning off some key tasks into those only done by an adminstrator. Brampton claims (rightly I believe) that this enhances the security, given the realities of a CMS having multiple users of varying capabilities and intentions remotely accessing it.
|
