I just performed an upgrade from 4.1 to 4.21 for a blog using the Universal template set (backed up my database before upgrading just to be safe).
When I republished the Universal template set I got some publishing errors noting that it couldn't find some index templates by id.
To fix the issue I took the following steps:
- Cloned the blog so that I could easily reference the old templates.
- Refreshed the blog templates to use the Professional template set (formerly the Universal template set)
- Chose the Green theme for the Professional templates set
- Copied the template edits which I had previously made:
- updated to the Navigation widget to list all pages with the tag @nav
- added an additional stylesheet and included it into the main stylesheet template
Upgrading should not have broken my templates, but at least the fix was easy.
Reported on Movable Type 4.2
My upgrade from Universal to Professional did not work also. I had my host, pair networks, do my upgrade to 4.2 Pro, and I went in and switched to the new "Professional" template (which I was told is the same as the old Universal). Although it is supposed to be a 2 column layout, everything that is supposed to be in my right smaller column, was being put at the very end of the content in the main column... My host said there is an incompatibility, and I'd have to redo my blog from scratch.
I don't think I'd recommend upgrading to the new Pro 4.2 until more testing and fixing is done.
Nick, I'm really not sure what Pair meant by "redo [your] blog from scratch". Can you expand on this?
If you refresh your templates to use the Professional template set, which is the same as Universal (with a few new features added in MT4.2) then your blog will look the same as when you first installed the Universal template set.
Was just able to repro this again locally. Also found this bug with an excellent description of the issue from David Phillips: [http://bugs.movabletype.org/default.asp?81430](http://bugs.movabletype.org/default.asp?81430)
+1 for this issue, exactly as described in the bug report (and mentioned [here](http://forums.movabletype.org/2008/07/rc4-big-problems-1.html)
I didn't do any refreshing of templates, as they had done it all for me. I will see if they can redo my sites backup and then reupdate to MT 4.2 Pro for me. Then I can try to do these steps myself and hope it works.
If you have phpMyAdmin or another tool to access the Movable Type database, running the following SQL query should immediately resolve this issue:
UPDATE mt_blog_meta SET blog_meta_vchar = 'professional_website'
WHERE blog_meta_type = 'template_set'
AND blog_meta_vchar = 'universal_website';
Thanks for this SQL code David
David you are my hero!
Thanks so much for that.