The secrets of a system integrator. My Journey of Startup, Product + Project Development
Given that I’ve recently released some slides and material on building plugins / applications using the Mura FW/1 plugin, the demo gods continue to smile down on me, except in a good way this time.
One of the things I’m really liking about Mura is the number of very, very smart people who care about making Mura as easy and painless to use as possible to do amazing things. Many are developers who are outside of Blue River and it’s a testament to the team behind Mura as well the codebase.
The long and short of it is this: As we’re using Mura FW/1 plugin template, and plugins in general, we’re seeing some places we could enhance and have some benefit. One area is ensuring multiple Mura plugins can work and play side by side without little issue.
I had the chance to take part in a conversation with some of the Blue River team and a few of us heavy Mura Developers, and the result of that conversation was to implement a simple change to the official Mura FW/1 Plugin. There is a notable difference in the Mura FW/1 template moving forward should you download it moving forward from today: Instead of appending an ?action=CfcName.FunctionName, the action has been expanded to be [packagename]action=CFCname.FunctionName.
I had the pleasure of presenting at MuraCon 2011 last week in Sacramento, California. It was nice to put a face to so many names and get to know the Blue River Team behind Mura CMS much better, and start so many new friendships.
I presented two main Plugin topics for designers, developers and managers.
Why Plugins are important not just for you, but Mura,
How easy Plugins are to build for Mura using FW/1.
A few folks asked for the links from my presentation to start building their own quick plugin while attending Muracon. Below are the quicklinks I shared for accessing Mura and FW/1 resources to build your plugins.
Let’s talk after the last presentation of the day is is over to get your plugin released and on github!
Hi everyone,
This is a bit of an overdue blog post — I have written a lot of drafts and a recent spell of travel has meant I haven’t been able to polish and publish much.. Sorry!
I do have one big piece of news to announce, the gang over at Mura CMS (Blue River Interactive) have asked me to speak at MuraCon 2011 in Sacramento, California on August 25-26th!
Instead of having a link that says http://www.yoursite.com/siteid/index.cfm/about-us, I want it to be:
http://www.yoursite.com/about-us
Recently I decided to move a Mura CMS site to linux. Off I went to pickup a VPS and transfer my installation.
After installing CentOS with the Apache/MySQL/Railo trimmings, I downloaded Mura directly to my server and started installing and learnt a few steps that may or may not be documented somewhere.
It seems that if your CFML engine of choice is running as nobody in Linux (I know ACF does install as nobody as default), You will have to go to your root htdocs/html directory and run the following:
The Mura gang over at Blue River have slotted me in to guest host a Mura Show!
The Mura show has been a big help for me in both of it’s formats when there’s a set topic and open help for anything I’ve been working on. Several times I learnt to solve or avoid problems I didn’t know I’d be having when someone else asked.
I’m going to walk through a basic introduction to using the Mura FW/1 Template Plugin. It’s been recently re-written and provides some cool functionality.
When working with Mura’s built in forms on the public side, there’s a few notes to self to keep in mind:
1) Mura’s public side (admin, built in display objects) are kind of legacy code. The code is well written and pretty straight forward to follow, but some of the conventions you might get used to on the plugin side of things aren’t quite the same. Fingers crossed that this can all be written as FW/1 logic eventually, but in the meantime, just know that tracing through display objects will be different than working on your own plugins.
Sometimes we need to include a custom header in the HTML tags on just one page.
One example is caching. When it comes to making every browser do the same thing (not cache a page), we end up with a number of commands that need to be placed at the top of a page only when it shouldn’t be cached.
Here’s some tags that could belong in the head tag of a specific page… (I’m sure this can be accomplished much easier in another way but I picked the first example that came to my head)..
This post is more of a quick note to self..
Often, we’ll see http://www.mysite.com/siteid/index.cfm?display=something on our public site, say, when creating a new user profile.
When we want to log out that particular user, simply place a