I’ve upgraded MT loads of times so followed all the usual procedures, backed up the blog, etc and copied the new files over to my existing installation.
However, when I try to access it instead of the usual upgrade checks, I’m getting just the error message shown below:
Got an error: Publish error in template 'error.tmpl': Unknown tag found: setvarblock
Can anyone shed any light on this?
Reported on Movable Type 4.2
Hmmm... seems it did some funny formatting (on my browser at least) with that error message. Here it is in full:
Got an error: Publish error in template 'error.tmpl':
Unknown tag found: setvarblock
This guy had the same problem, and solved it by installing a fresh copy of the Movable Type files on his host.
Thanks Mike, but by "installing a fresh copy" do you mean deleting all old files and reinstalling on a "clean" system?
Otherwise, the upgrade process is pretty much an fresh install as I copied all the files over my existing version (as I have many times before)
I've had this error when one of the config.yaml files in the plugin directory has a dodgy character in it (as simple as a normal newline instead of the funny things that yaml needs).
You could backup your old directory, install the full 4.23 then add your plugins one at a time, no need to change database or anything else.
So I've already copied all the 4.23 files over. If I remove any non-standard plugins from the plugin directory this should do the same as you're suggesting Richard - right?
You may not even have to go that far. Chances are, it's something that went wrong when uploading Movable Type, not with your plugins. If you're using FTP to do this, you really should find a way to get SSH access to your host. With SSH, you can log in, and use the "wget" command to download the zip file directly to your host and unpack it on their server, minimizing the chance of anything going wrong.
Well its seems to be fixed!
Originally I downloaded the ZIP archive, extracted the files, and FTP'd them to my host.
This time I downloaded the GZ archive and did the same thing and its working fine.
Either there's an issue with the ZIP package or a blip happened when I uploaded (although I've had no problems before).
Guess you were right Mike!
I'd say the FTP client is to blame, assuming MikeT's answer is accurate and it sounds that way I would assume that your FTP client transfered text files in binary mode and thus fudged the end of line markers from the zip file onto the server (which expects different end of line markers).
The zip file would have contained DOS line endings (CR/LF) whereas the GZ would have contained unix line endings (LF only) and by binary uploading the files with the correct line endings it "fixed" the file. It is my belief that having your FTP client intelligently transfer text files as ascii should have solved the issue as well.