Anyone else having an issue where it sits on the "Starting upgrade..." screen forever? I can't seem to get past that.

Congratulations... Still wait the final version... I'm just to tested here. Thanks!

Whew, someone else having the same problem (misery loves company). My situation is like Justin's. It sits on the "Starting upgrade..." screen forever as I stare at the moving stripes.

I am going from beta 2 to beta 3, using a MySQL database.

Yay! I'm not the only one. My upgrade is taking a bit long - forever in fact. I guess I'll wait for the final version to be released before using my blog again. Also, has anyone heard anything about MTBlacklist being ported to 3.2? The bots are commenting the ** out of my posts, so for now I had to allow only authenticated users.

Oh wow, beta 3 is great, and I love the new default stylesheet! Will there be more coming, such as optional columns and such? This version also runs a lot faster, too.. very pleased with it thus far.

Justin, Michael and code_zero, first of all, please make sure that you have Javascript enabled in your browser. If so, please file a bug immediately with as many details as you can muster including screenshots if you can.

Oh, just in case it's not obvious, please report the exact make and version of your browser as well, if you file the bug. Thanks.

One last thing, the update process in beta-3 does not scroll quickly like it did in previous versions. We removed most of the individual statements, so it may appear like it's "stuck", but you will notice that the current task is displayed and the percentage completion is updated continuously but in a far less noisy manner.

I just wanted to be clear to make sure that your expectations are in line with what has changed.

Did I say one last thing? Well, I never actually mean that.

If you have a problem with upgrade sticking and javascript is enabled in your browser, please try emptying your cache and reloading. We have a feeling that javascript and CSS caching is at the heart of this problem.

This is becoming a habit...

Also, has anyone heard anything about MTBlacklist being ported to 3.2?

Feel free to do it! It's open-source! :-) Have you tried SpamLookup? If not, you should...

So, what is all this new stuff in the stylesheet (and templates) about typelists and other stuff that looks interesting? I have an idea what it could be, but I don't like to assume in cases like this. Are we getting goodies in the final release we don't get to see during the beta?

poke poke nudge nudge

Not that I'm curious or anything ;P

I think the problem with the upgrade script not running is that they uploaded the mt-static directory into their static directory and not the contents of it into the static directory.

That's cause I did that at first too lol.

I just upgraded to Beta 3. I got no error when doing the upgrade. My previous problem about double post in in the dynamic publishing is solved. Thanks.

But, using the same templates (before I got the double post appears in the page), I only got 2 latest entries in my main index. But, when I go to "next page", there are 6 entries, and this is correct, but not for the main page. I am not sure what causes this. Or, anybody experience this also?

Anyway, thank you 6A!

Okay, I've done this enough times; should have known better (serves me right for doing this while sleep-deprived). My hanging on the upgrade screen problem was because I forgot to replace Beta 2's mt-static folder with the one in Beta 3 (my static folder is outside of the mt directory).

When I went back to the upgrade screen, it hung once more on the "Starting upgrade..." message. I held down the option key and hit the refresh button (Safari), and the upgrade process immediately started, and the progress messages started to list themselves in the gray box. All is well.

--

Sidenote: Created a new test blog to check out Vicksburg. Nice. I'm guessing the template designer is a Safari user (text-shadow property on the blog header).

Michael's option key refresh trick seemed to work for me.

Upgrade went superfast and without a hitch. Love the Vicksburg stylesheet. I already tweaked it "cafe style". You guys are doing an amazing job... MT3.2 is awesome. (The only problem I've had is errors when trying to refresh templates with the new version of TemplateRefresh. I'll report that.)

I think the problem with the upgrade script not running is that they uploaded the mt-static directory into their static directory and not the contents of it into the static directory.

Actually, if you can't have static contents in the MT directory (e.g. because it's in the cgi-bin), you actually move the mt-static itself to some place in your web root and set StaticWebPath in your mt-config.cgi. You do not have to empty out mt-static's contents to that location as long as you set up your StaticWebPath correctly.

My hanging on the upgrade screen problem was because I forgot to replace Beta 2's mt-static folder with the one in Beta 3 (my static folder is outside of the mt directory).

In addition to caching, that would indeed do it.

Sidenote: Created a new test blog to check out Vicksburg. Nice. I'm guessing the template designer is a Safari user (text-shadow property on the blog header).

He uses all browsers. We just like to take advatage of advanced features in certain browsers when we can.

I'm running the MT3 beta in a test blog, but I really want to drop it into my production blog; problem is, all my users have heavily customized thier templates and style sheets.

I'm trying to find info on what is and isn't compatible from Mt 3.1 templates; is it documented someplace?

So far, Beta3 rocks. B^)

After having beta-2 installed for a while without any problems, I tried upgrading to beta-3 and got nothing but a 500 Internal Server Error. I tried installing from scratch, and I'm getting the same thing. I'm trying to use it with a BerkeleyDB... but since it won't even install I can't test out the new beta :(

I've flushed the cache(s) and tried both Firefox 1.0.6 and IE 6. The barberpole is frozen and the only upgrade message is "Starting upgrade..." with no progress shown at all below. Refreshing doesn't help.

I guess I'll upload again and try once more.

Up above, it says that users of a previous Beta version just have to upload the "new files," making it sound like we do not have to install the whole application as we have had to in the past. However, I have downloaded the Zip version and I was wondering how we differentiate between the "new files" and ones that haven't been updated?

Upgraded successfully. I re-uploaded the whole distribution, logged in, the upgrade froze, hit reload and it progressed and finished correctly. So, perhaps a file or two failed to FTP properly on my first try? Seems ok now.

As with other users, after placing the contents of my mt-static folder into my static directory, everything works fine!

Slaps self in face for the mistake

Everyting in beta 3 looks great!

Ah, will I be able to dynamic publish in version 3.2 FINAL? I still can't right now. My templates_c directory is CLEAR!!!

Wow, the new default templates are beautiful. A HUGE improvement over the previous ones.

Well done! :)

I'm trying to find info on what is and isn't compatible from Mt 3.1 templates; is it documented someplace?

The old templates will work fine. The biggest difference is when you change your comment settings, you will have to rebuild (assuming you're using static publishing) all of your individual archives. With the new templates, you only have to rebuild a single index template (although we prompt you to rebuild all of them because it's fast and easy).

After having beta-2 installed for a while without any problems, I tried upgrading to beta-3 and got nothing but a 500 Internal Server Error.

That means that there was an error before the web browser was ready to accept it. When that happens, the real error message is put into your server's error logs right before the "Premature Script headers" message.

Most likely, you didn't upload all of the MT files (aside from images) in ASCII mode.

Up above, it says that users of a previous Beta version just have to upload the "new files," making it sound like we do not have to install the whole application as we have had to in the past.

Let's just pretend for now that they're all new files. That was the intention behind that statement, not that you only would upload the ones which had changed.

Ah, will I be able to dynamic publish in version 3.2 FINAL? I still can't right now. My templates_c directory is CLEAR!!!

There should be no reason that you couldn't do it before now. I've run dynamic templates for about a year. If your templates_c directory is CLEAR, it probably means that it isn't writeable by the webserver. The easiest way to fix that problem is to:

1) Delete it 2) Go into you weblog publishing preferences and everything to build statically 3) Save 4) Set either "build archives dynamically" or "set individually" 5) Save 6) Enjoy.

Thanks Jay, it does appear that I had uploaded using Binary instead of ASCII... although strangely, that has never caused me a problem with any release prior to beta-3.

Hmm, Here's what the error log says in cPanel.

[Sat Aug 6 00:23:08 2005] [error] [client 66.249.71.47] Premature end of script headers: /home//public_html/mtview.php

Michael, "When that happens, the real error message is put into your server's error logs right before the "Premature Script headers" message."

Ok, now it says the following.

[Sat Aug 6 14:20:39 2005] [error] [client [removed]] Directory index forbidden by rule: /home/[removed]/public_html/archives/categories/news/

So, I have a feeling it's something Movable Type put into the .htaccess file.

Ah, yes, the line that is "causing" the error is this one:

DirectoryIndex index.php index.html index.htm default.htm default.html default.asp /movabletype/docs/3.2/mtview.php

I'm pretty sure, judging by your error message, that the reason it's causing the problem is that your host is limiting your ability to do certain things (like set the DirectoryIndex) in your .htaccess file. Try sending an email to your web host asking them about this. This is pretty innocuous and harmless stuff, so it sounds like your host might be a little overcautious, which is fine. A good host however, will give you the functionality you need.

Ok, I just upgraded my production blog (www.moronosphere.com) to mt3.2. God, that was easy, and as Jay pointed out, there are no compatability issues with mt3.1 templates. Great work guys, that was painless.

I just uploaded all the files for MT3.2b3, and when I log in and try to run the upgrade script, I get an MT error message page with "An error occurred: No permissions. Please contact your administrator for upgrading Movable Type." The script itself is chmod'd to 755, so those don't seem to be the permissions in question. What'd I do wrong?

Joel, are ALL your .cgi scripts chmodded to 755?

Joel: Actually, I'm guessing that you don't have rights to create weblogs with the user ID you're using. Log in as a user who has rights to create weblogs, and you'll be able to upgrade.

Karl: That's what we like to hear... :-)

Joel-- I assume you were upgrading from an earlier beta? It shows that error if you were already running 3.2x release and your user account isn't a system administrator account. Do you have another login that has system administration access? Or, perhaps an earlier buggy upgrade left you without any system administrator? The fix for that would be to delete the mt_config table in your MT database (or the config.*) files under a BerekeleyDB datasource directory. Then re-upgrade.

All the .cgi files were already chmod'd to 755 and there's only one user account associated with my blog, so I went ahead and dropped the mt_config table. That seems to have solved my problem nicely, as my upgrade is now complete.

Thanks for the help!

that new stylesheet is beautiful, good work!!

MT-Blacklist doesn't work with beta 3 - I am getting inundated with spam! Whats the best solution? Blacklist used to work wonders - so what is the recommendaed spam plugin for beta 3?

KO: I was able to successfully install MT-Blacklist last night on a fresh install of MT3.2b3 and it worked. There is a little tweak you have to do first to one of the blacklist files, refer this entry.. although I am getting an error message on the comment error screen (details here) but it still does the job ok. Did you do that tweak before trying to install MTB?

I had MT3.2b2 running beautifully (except for minor known bugs) as a fresh install on a new site hosted on a Windows 2003 server, but after uploading MT3.2b3 (all new files), I now just go straight to the much-loved error message when trying to run mt.cgi:

CGI Error - The specified CGI application misbehaved by not returning a complete set of HTTP headers.

Any suggestions very much appreciated.

I get the following error when I try to rebuild a new blog:

mkdir /home/virtual/site252/fst/var/www/[URL REMOVED]: Permission denied at lib/MT/FileMgr/Local.pm line 105

Not a problem in 3.14 which I was using just prior to upgrading. Any ideas?

Ok, never mind. Silly error. I like 3.2!

I upgraded to beta 3 and then tried to rebuild my beta site and I received the following error;

Building entry 'Pictures' failed: Build error in template 'Individual Entry Archive': Error in tag: Can't find template '

If I try to just build index pages, I get this error for the main.index page as well.

Any ideas good people?

(Building entry 'Pictures' failed: Build error in template 'Individual Entry Archive': Error in tag: Can't find template '

<-----Building entry 'Pictures' failed: Build error in template 'Individual Entry Archive': Error in tag: Can't find template '

Hi gang. Testing locally on OS X Tiger. http://test.mt32.dev/ ;)

Wiped out the directory and the ß2 MySQL database to start fresh. I get a Internal Server Error error when mt.cgi redirects to "upgrade mode install" with the following entry in the Apache error log:

[Mon Aug 8 01:07:35 2005] [error] [client 127.0.0.1] mod_rewrite: maximum number of internal redirects reached. Assuming configuration error. Use 'RewriteOptions MaxRedirects' to increase the limit if neccessary.

Swapped back to ß2, installed that without a hitch, then back to ß3 and bang, same error. :\

what da... just started over and it worked... weird. Sorry! ;)

Installation for beta 2 was effortless, as was the subsequent installation of beta 3; well done for making it so much more straightforward.

What has changed for me is that Blacklist no longer functions; I've since deleted it nd installed Spamlookup, but still get notifications of obvious spam that has not been filtered. I can configure either plugin just fine, but they don't actually filter. It's not a huge problem since I've reassigned the mt-tb and mt-comments to different names, which is very effective, but I'm sorry to have lost such an effective means of excluding the nonsense. Am I an isolated case?

MTB requires a little tweak to Blacklist.pl ..have you tried that? Look for this line of code:

return 1 unless $MT::VERSION =~ m(^3\.1);

return 1 unless MT->version_number >= 3.1;

Is "Can't call method 'clear_cache' on an undefined value at lib/MT/App.pm line 606." the caching problem you mentioned? I didn't get it in b2, but I'm getting it only in IE (not Firefox) in b3 when comments are entered.

I assume this is just me being an idiot, and not a bug. I've cleared every cache I can find, and I'm still getting it.

Yeah I think this is something that the plugin author will need to look into, rather than being an issue with MT, however I can't see that happening until a final release of MT3.2 is out, as there may be more changes with MT in the pipeline in the interim. MTB is working anyway, and it seems the only comments that the error message is affecting is spam comments when it is blocked, so no real biggie in the short term. :)

Just to add to my earlier message about my new install of MT3.2beta3 getting a continual error on a Windows 2003 server, namely:

CGI Error - The specified CGI application misbehaved by not returning a complete set of HTTP headers.

I have now reverted to beta2 and everything is running smoothly again. So the problem is somewhere in beta3 (which I uploaded in toto, and all in ASCII apart from the images in mt-static.

I would dearly like to see the latest beta working, but am in need of some advice before this happens.

I'm trying to do a dry run upgrade of a blog from 3.17->3.2b3, and when mt-upgrade.cgi run, it gets as far as "Creating entry category placements..." and errors out there. I'm guessing it might be a permission problem, but no idea what permission problem.

forgot to say, but I'm using sqlite.

if in

lib/MT/Upgrade.pm I comment out, ala

    # < 2.0

the upgrade finishes, and seems to work, but who knows what I messed up.

I'm now getting:

"Can't call method 'clear_cache' on an undefined value at lib/MT/App.pm line 606."

when commenting in Firefox, too. Weirdly, this didn't start until today (I upgraded from b2 to b3 on Friday).

I've just updated the known issues list for MT 3.2b3. Please check it over.

Also, please remember, that if you are experiencing a bug, posting about it here won't get it fixed. Please submit your bugs and, at this point, the sooner the better.

If you are just needing some help or you want to see if anyone else has the same problem you have, please use this thread for that. In this way, you can easily find other with your problems since they are all on one page. It also keeps other threads clutter free for discussion.

Thanks!

Done. Sorry. I was just trying to figure out if that's what you meant by "a few people... are having problems related to cached javascript files" before I filed an unnecessary bug.

if I run mt-config I recieve failed to open log file fopen: Permission denied [Wed Aug 31 21:36:56 2005] [error] [client 80.133.103.162] Premature end of script headers: /home/virtual/site200/fst/var/www/cgi-bin/mt/mt-config.cgi

what do I have to do?

ceejay: mt-config.cgi is not a CGI you execute. It's the new name for the MT configuration file. You don't need to run it.

k but if I run mt.cgi I got this: [Thu Sep 1 20:39:41 2005] [error] [client 80.133.103.162] Premature end of script headers: /home/virtual/site200/fst/var/www/cgi-bin/mt/mt-upgrade.cgi

without any msg in front of it if I rn mt-check.cgi it returns: /usr/bin/perl: relocation error: /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Image/Magick/Magick.so: undefined symbol: InitializeMagick