Movable Type 4.0
I'm not sure I really like it, after finally getting around to customizing my templates. Didn't they say that the template system is supposed to be easier with the new release?
For those of you who don't know, the default templates that come with this new release are divided into modules, which can be great for lists and other items that appear on more than one page. The problem here is that every single thing is controlled by a module, which contains more modules, and the result is a highly confusing and virtually indecipherable set of code.
So, trying to learn the new template system by looking at the default templates is a task that would require days of reading and re-reading and, well, time that I just don't happen to have.
I tried moving my 3.2 template code into this new version, but it didn't work. The archive templates work much differently in MT 4.0, and I'm beginning to think it's to the detriment of the system. The Category and Date archive templates have been melded into one -- and that is a major issue as I can't figure out how it's possible to have both. In fact, even on the default template I started with, the categories list didn't link anywhere...it just listed the categories. What's the point of that?
Tags could take the place of categories, but again, I haven't figured out how I can place the code I managed to find in the default templates onto a separate page so that they work properly.
I know there is a solution, but the code is strung over several templates and modules and the documentation for this release is of course worse than with previous releases, as no one has had the time yet to create documentation for them.
My company is considering the upgrade from 3.2 to 4.0, but I think the upgrade will more than likely not happen just because of the template problems. We have over 100 blogs, and none of them will be able to just be moved over to the new version...they will all have to be re-coded. That's something I wish Six Apart would have taken into consideration with this upgrade -- surely we aren't the only company with that many active blogs that use their software. The ability to move the blogs over with as little re-coding and trouble as possible should have been a major consideration.
I give up for the night. My blog is at least re-skinned.
For those of you who don't know, the default templates that come with this new release are divided into modules, which can be great for lists and other items that appear on more than one page. The problem here is that every single thing is controlled by a module, which contains more modules, and the result is a highly confusing and virtually indecipherable set of code.
So, trying to learn the new template system by looking at the default templates is a task that would require days of reading and re-reading and, well, time that I just don't happen to have.
I tried moving my 3.2 template code into this new version, but it didn't work. The archive templates work much differently in MT 4.0, and I'm beginning to think it's to the detriment of the system. The Category and Date archive templates have been melded into one -- and that is a major issue as I can't figure out how it's possible to have both. In fact, even on the default template I started with, the categories list didn't link anywhere...it just listed the categories. What's the point of that?
Tags could take the place of categories, but again, I haven't figured out how I can place the code I managed to find in the default templates onto a separate page so that they work properly.
I know there is a solution, but the code is strung over several templates and modules and the documentation for this release is of course worse than with previous releases, as no one has had the time yet to create documentation for them.
My company is considering the upgrade from 3.2 to 4.0, but I think the upgrade will more than likely not happen just because of the template problems. We have over 100 blogs, and none of them will be able to just be moved over to the new version...they will all have to be re-coded. That's something I wish Six Apart would have taken into consideration with this upgrade -- surely we aren't the only company with that many active blogs that use their software. The ability to move the blogs over with as little re-coding and trouble as possible should have been a major consideration.
I give up for the night. My blog is at least re-skinned.
Leave a comment