Hi,
I am trying to upgrade my MovableType installation from v3.
Got an error: Can't locate object method "install_properties" via package "MT::Tag" (perhaps you forgot to load "MT::Tag"?) (in cleanup) Can't call method "registry" on an undefined value at lib/MT/Component.pm line 558 during global destruction.
(in cleanup) Can't call method "registry" on an undefined value at lib/MT/Component.pm line 558 during global destruction.
I did see one other post regarding this topic, and I did ensure that there are no zero byte files and all the files did upload successfully. I used my trusty SmartFTP program. I followed the directions and copied the new files over the old ones and then uploaded the new merged set back to the web server.
The web server is Windows based, not UNIX/Linux based, if that makes any differences. Also, MovableType worked perfectly before.
Thoughts?
Thanks,
Sarah
Reported on Movable Type 4.2
Try a clean installation of Movable Type's files, rather than copying over your old installation.
Yes, this thought crossed my mind, but this option is not an option. There are many customized pages, a huge database, and customized this and that.
Unless you customized the CMS, that's not going to be an issue for you. All I'm talking about is uploading a fresh copy of the Movable Type software, not touching your database or published site.
You have an interesting idea / point. I was thinking that a fresh copy of the files would erase / rese the database, but from what you are saying a fresh copy of the file will merely upgrade the database and render only my templates moot, which I can merely place back (edit back).
Your suggestion is intriguing. :-) I will give it a try today.
Thanks!
Sarah
What database are you using?
I tried the experiment and got the same result, namely.
Got an error: Can't locate object method "install_properties" via package "MT::Tag" (perhaps you forgot to load "MT::Tag"?) (in cleanup) Can't call method "registry" on an undefined value at lib/MT/Component.pm line 558 during global destruction.
(in cleanup) Can't call method "registry" on an undefined value at lib/MT/Component.pm line 558 during global destruction.
That means that MovableType does not like something in the database when upgrading, not in the file system.
What **exact** version are you running? 4.26 or 4.261?
Hi Mike,
I downloaded yesterday the latest and greatest, so to speak, from the sixapart website, which was 4.261.
That was supposed to be fixed in 4.261... did you ever install 4.26?
Hi Mike,
Thanks for the quick reply. :-) The blog is at 3.something and I was/am attempted to upgrade to the latest MovableType. I downloaded the latest, 4.261, and proceeded to try and update my blog to no success. To my knowledge, there are no add-ons. It is just a simple MovableType blog, albeit one at 3.whatever. I never touched or tried 4.26.
From your original post, it sounds like you did some process of taking a local copy of 3.X, and overwriting it with 4.261, and then you uploaded that over top of your existing 3.X installation. Can you be more specific about what you actually did?
I did something much simpler. Okay, I added a step. Before I started to do anything, I made a backup copy of the original file systems on the web server and I backed up the MySQL database. After that, I downloaded the latest MovableType files. I tried both set of files to solve my particular problem. I tried the developer version (first column in the downloads area), and then lastly the Pro blogger version (second column in the downloads area).
From here, I extracted the MovableType (MT) files. I then copied the new files, per direction in the upgrade documentation, over the existing files on the file server. I then copied the entire set from my local drive, where I did the copying, back up to the web server, thereby placing the MT v4.261 files on top of the already existing 3.whatever files.
Once the files successfully uploaded, I then went to the site. I saw the login screen (expected), but shortly thereafter, even if doing nothing, I saw the error page.
As I could not go past that (yet), I deleted all the files on the web server and then uploaded the backup copy that I made back to the web server, thereby restoring the older version. That is where I am now.
I tried a couple of different things, but I keep getting this issue.
I just logged into the blog and saw that the current version is v3.2. I am upgrading from v3.2 to v4.261.
Thanks for all the help Mike!
Try this. Delete MT off your host's file system. Upload a fresh copy of MT 4.261, and then copy over your mt-config.cgi and any styles you have created. That should give you a fresh copy of 4.261 that is configured for your host. See if that works. If not, you can keep playing around with it since you have a backup of 3.X.
Hi, I tried that. :-) You had mentioned to me once before to try a fresh copy. That is what I did. I deleted the entire contents. I copied over the mt-config.cgi, and then uploaded over the whole thing. I got the same error, which is why I said that I found out that the problem is an incompatibility with something in the database, not in the file system, although I cannot imagine what, as the current version v3.2 works fine.
I am using MySQL as the database. By the way, the file system is not as simple as you think. There are a zillion files inside folders 2007, 2008, and 209, not to mention other folders that MT created for itself. That is moot anyways, as the upgrade did not work. MovableType (MT) is unhappy with something in the MySQL database.
Hi Sarah -
Taking a step back, that message, from a very general perspective, means that the upgrade process is having an issue when it tries to find a particular file - in this case the MT::Tag module (Tag.pm in lib/MT to be specific).
Since you say you are upgrading from MT3, it might be because you have the old tags plugin installed, as there are some compatibility issues installed. Other than that, it might be that you have some other compatibility issues.
You have mentioned losing data, and that should not be a concern. If your data is stored in the database as you mention (MySQL), then everything is there: Authors, Blogs, Entries, Templates, etc. The only thing you won't have there are things like images and other content that you link from your entries, either on your site or elsewhere.
If you are still having issues, drop me a line here or on my site (everitz.com) and let me know so we can get you fixed up!
Was there ever a resolution to this?
Yes, this specific problem was resolved, although I do not remember any more what the specific resolution was. I can tell you (and others reading this email) of the specific steps that I had to do to make sure that everything worked.
1. MovableType only works with the latest version of PERL. If I remember the numbers correctly, it needs 5.8.8. Some web hosting companies use older ones.
2. MovbleType requires the DBI PERL module.
3. You must create a Virtual Directory if running under IIS that points to the /mt/ folder using a different name. For instance http://www.myblog.com/mt-admin/ would point to the real location http://www.myblog.com/mt/. mt-admin would be the real location.
4. Use latest versions of PHP.
5. mt-check.cgi should report a full report and have no issues.
Try these steps.
Thanks.
Sarah.
5. The MovableType folders need to be able to access the folders.
6. CGI needs execution privilidge.
Many thanks for the reply! MT is very picky indeed.