As a brief sidebar in my Advanced Plugin Development series I'm going to explore the PluginConfig and PluginApplication objects, two very essential components in developing your Mura plugins. The "best practices" methodology of accessing PluginConfig has also recently changed, so if you are developing plugins there are a few important bits of information in here. Also, make sure you've read or have a copy of the programmer's guide to Mura CMS handy as I'll be referring to that document occasionally.
Entries Tagged as 'FW/1'
After many requests (and a few promises) I am finally putting together a series of blog posts on building a complex plugin for the Mura CMS. Plugins are basically stand-alone applications that take advantage of Mura's extensibility hooks to integrate themselves into the CMS and web site. This feature set has matured greatly over the last year, and allows developers a great deal of latitude over how they can achieve this and in what tools they can use. This series of posts will be as much about building the plugin as introducing developers to the many facets of Mura extensibility.
FW/1 is a great place to start your development from, regardless of the size of your application. That being said, it's no-frills foundation and the fact that it is a very new framework (version 1.1 is just peeking into the sunlight as we speak) means there are scaffolding tools that you may have develop yourself to maximize your productivity. It also means that some of its best features (like nested layouts) can also work against you if you are not careful. One of these is the way nested layouts are loaded, and how this can affect <CFHTMLHEAD> calls.