2 posts tagged “mtype”

We're getting closer to crazy delicious. After my post last night about using MovableType as a CMS for the Trizzle Project site, Ben Trott was nice enough to suggest that I try using dynamic publishing. He also supplied a link to the documentation that I probably should have looked at before going ahead... but I didn't, and as a result I completely broke publishing my blog. No matter what I did, I just got an Apache server error, even after following the instructions that Ben had pointed me too. I decided to back off on dynamic publishing until I understand MT better.

So I deleted my existing blog publishing directory, rebuilt my site with static pages, and that fixed the probems. Then I decided to try something else-having MT produce php pages in my site instead of html. My hope was that I could then put the trizzle php code into the

I copied my external main-index.html template file and renamed it main-index.php, then pointed to it in MT's template options for index.html. Rebuilt the site, and everything worked fine. After that, I put some test php code in my main-index.php file and lo and behold, it executed once I rebuilt the file. Now proceeding with more confidence (which required some not very robust editing of php require paths-one thing I am going to have to  figure out how to organize my site directories under this new regime) I put in some code from the old trizzle index.php site, and it worked!

If you look at the screenshot below, you will see a MovableType produced index page, but with a "Trizzle Tags" content module on the left that is producing the Trizzle tag cloud using php code.

Edit: updated the screenshot after more tweaking of the css, and adding some real content.

Trizzle-mt-home-page

crazy delicious? Well, hopefully soon. Today I started creating a new Trizzle Project website, using MovableType as a blogging/content management system for the site-a project which is win-win for me because it both improves the Trizzle site, and also helps me understand how MovableType works and what it's like for a developer using it to run a site.

Right now it's pretty slow going because I'm figuring out how how the CSS and tags work in the MT templates. One of the first things I did was have MT start using external template files instead of one stored in its (database? well, internally in any case) which works well, once you sort out the permissions problems. This is good because then I can examine and edit the template files in a text editor, instead of having to scroll around in a browser textarea, which is pure giznank.

The principal pain I'm experiencing now is having to rebuild my site every time I make a change. I'm one of those developers who, especially when I'm in just starting out, likes to make a few small changes and then see the results. With Mtype this means rebuilding the site, which takes a bit of time and involves several mouse clicks, and a visit to a small pop-up window which is easy to lose.

I wish MT had an option for a "developor" mode where changes made to template files would show up instantly in the site files, so you could just make an edit, then reload the web browser. Then once you actually wanted to put the site on the web, you could put it in "production" mode and build the site, which is more efficient for serving up files.

Obviously this would be a huge architectural change-because the site files couldn't be html while in developer mode, they'd have to be dynamic. It might be more development effort than it's worth.