Posts tagged ‘Mango Blog’

Welcome to v4 of my blog! Sort of. The first version I made myself. After 5 years of using it, it became weak and sloppy. So I moved to CFBloggy. The person that wrote that pissed me off by not answering my questions. So then I moved to BlogCFC. I hadn’t even released the BlogCFC version when someone told me about the greatness that is Mango Blog. It’s only about a year old but it seems like features for it are going to be coming down for it left and right. So I decided to jump on the bandwagon now. My biggest problem with it is code blocks. You have to disable Javascript in order to add a block of code so it colors it. Once you have submitted the post you can re-enable Javascript. What a hassle!

Mango Blog 1.2.2 came out a couple days ago. I went to upgrade to it and it was a day long issue trying to get my blog back up and running. What I eventually had to do was revert back to Mango Blog 1.1. But I did make the design more wide. Before it was using an 800×600 design. I changed it to 1024×768. I am also going to start posting my source code pretty soon. Stay tuned for that.

I started putting a bunch of my source code in the labs section of the blog. What I started out doing was providing a link to click on to see the demo. From there you could right click and get the source. What I decided was better was to have the demo on the page which you would be able to right click and view source.

The problem I was running into was the “script” tags were getting converted to “InvalidTag” after I submitted the form. So a simple tag like <script type=”text/javascript”> would be converted to <InvalidTag type=”text/javascript”>

At first I thought it was Mango Blog that was at fault. It turns out Coldfusion was the one to blame. It’s called Global Script Protection. It’s in place starting with I think Coldfusion MX 7. It was created as a way to help prevent SQL injection. In Coldfusion Administrator, by default, it is set to “all” which means that script, embed, and I believe, object tags get converted to “InvalidTag.”

Unfortunatly my website is on a shared hosting server. So changing the Global Stript Protection wasn’t an option. I love Adobe! They even put a way to change the Global Script Protection inside the code.

In the cfapplication tag there is a property called scriptProtect. By detfault it is “all” This can be changed to “none” to disable it completely. You can also set it to a comma seperated list of variables to look at like “url, form, cookie”

So for the purposes of Mango Blog in the Application.cfc file in the administration area I added scriptProtect=’url, cookie’ and I am able to post Javascript now. Comments still won’t be able to use Javascript because I only did this for the administration area.