« How to file a bug | Main | Getting started with 3.2 »

Support for the beta

This is an archived entry from the Movable Type 3.2 beta test.
Entries from the current beta release (v3.3) can be found here.

One important thing to remember about 3.2 Beta is that it's officially unsupported software. While we'd love to be able to help everyone who wants to give it a spin, our primary purpose in allowing this sneak peek is to ferret out pesky bugs that may need to be eliminated prior to the final release.

The Movable Type Team will be concentrating heavily during the beta test only on issues or problems arising from the software itself, and thus, we're unable to provide assistance with "normal" support issues.

So, while we encourage you to use this weblog, the commenting features, etc. to discuss the beta version with one another if you need help, we ask that you not open support tickets or leave posts in the Community Forum for assistance with the beta version of our software.

[UPDATE: We have created an entry to be used for user-to-user support which should give you an outlet for help if you're having trouble.]

As Jay mentioned in our Welcome announcement, this blog is the central location for beta testing activities and discussion, and we need your assistance and cooperation to make it valuable to our development team.

Comments

yes but... configuring plugins in the new version does not appear to work (for me)... whenever i try to activate my plugins that have worked in all previous versions i am asked to log back in and get an "Unknown object type" error message.

arrrgggggg!

arrrgggggg!

Chad Don Blake Dude -- this is a beta. If it bothers you that much sit this time out while we find the bugs.

nope, beta isn't 'bothering me' at all... was just being expressive. my bad... and trying to navigate my way around to find the appropriate place to post/email bugs.sorry if i came across as rude.

peash, --cdb

a) What is /php/ for? b) Was 3.2 a "scratch-old-and-make-new" platform?

/php/ is the dynamic publishing subsystem which is powered by Smarty.

I don't think I understand #2.

hmm.. so if dont make use of dynamic content, I can delete that php directory entirely? ..or is it still required for some other processes?

I get this error when i try to run the mt.cgi and i have set my mysql params fine: Got an error: Bad ObjectDriver config: Your DataSource directory ('removed name here \www\mt./db') does not exist.

Comment out (put a # in front of) the line that says DataSource ./db although it sounds like you're still using mt.cfg. You're better to transfer the details from the old style files mt.cfg and mt-db-pass.cgi to the new mt-config.cgi files, and then delete both the old files.

sorry, that should say "..to the new mt-config.cgi file,..", not files (there's only one mt-config.cgi file).

Jay Allen,

What I ment by part 2 was Movable Type 3.2 coded from scratch (not using the framework of 3.1).

What does this mean? "Can't call method "is_superuser" without a package or object reference at lib/MT/Permission.pm line 78."

What's the syntax for individual archives by entry id?! The new filename archiving removed all the links to my old-style individual entries!

Please help, this is a nightmare!

I think the last bit of the Archive File Path for the Individual Archive Entry mapping would be:

<$MTEntryID pad="1"$>.html

to get numbered individual entries.. try it, it was that at one stage anyway if not still.

You could use an MTEntryID tag, but then you wouldn't be able to use any of the other new '%' codes (you can't mix the '%' codes with MT tags in an archive file name template).

This what I'm currently using on my install:

archives/%y/%m/%e%x

'%e' is the code for <$MTEntryID pad="1"$> '%x' is the code for <$MTBlogFileExtension$> (the "." is automatically added)

I updated my Blog to Beta 3.2 and everything went fine, except I get logged out everytime I do anything. So I Login again and the task gets performed, and I end up where I was supposed to be, but something is obviously wrong.

Oops, sorry Jay (for posting on the wrong thread) but since I'm here; I determined that deleted cookies (from adware scan) were causing Netscape to have problems with publishing, using the awesome new 3.2.4 - switched to my trusty Firefox and everything was perfect. Thanks for your great work!

I found a little bug in b5.

In ContextHandlers.pm at line 414 :

'h' => "<MTArchiveDate format='%h'>",

I think it must be as below.

'h' => "<MTArchiveDate format='%H'>",

I'm trying to put 3.2 on my site, and I'm getting a 500 Internal Server Error. Everything's been uploaded correctly, mt-config has the correct info and mt.cfg and mt-db-pass.cgi are deleted. Help?

I can't figure this out.. when I try to open mt.cgi I get the following "Got an error: Bad ObjectDriver config" Doesn't tell me what so I could fix it..

I'm trying to upgrade from 3.17. I've configured the config file, renamed it, commented out what needed to be.. I'm lost. Help please!

Upgrading from 3.2b1 to 3.2b5 (mt-upgrade.cgi) shows this error. How to fix it? -

Loading template 'upgraderunner.tmpl' failed: HTML::Template->new() : Cannot open included file upgraderunner.tmpl : file not found. at /home/DOMAINNAME/publichtml/mt/extlib/HTML/Template.pm line 1500 HTML::Template::inittemplate('HTML::Template=HASH(0x9e5fe04)') called at /home/DOMAINNAME/publichtml/mt/extlib/HTML/Template.pm line 1105 HTML::Template::init('HTML::Template=HASH(0x9e5fe04)') called at /home/DOMAINNAME/publichtml/mt/extlib/HTML/Template.pm line 999 HTML::Template::new('HTML::Template', 'type', 'filename', 'source', 'upgraderunner.tmpl', 'path', 'ARRAY(0x996f270)', 'searchpathoninclude', 1, ...) called at lib/MT/App.pm line 719 eval {...} called at lib/MT/App.pm line 718 MT::App::loadtmpl('MT::App::Upgrader=HASH(0x991b18c)', 'upgraderunner.tmpl') called at lib/MT/App.pm line 784 MT::App::buildpage('MT::App::Upgrader=HASH(0x991b18c)', 'upgraderunner.tmpl', 'HASH(0x9e64024)') called at lib/MT/App/Upgrader.pm line 348 MT::App::Upgrader::buildpage('MT::App::Upgrader=HASH(0x991b18c)', 'upgraderunner.tmpl', 'HASH(0x9e64024)') called at lib/MT/App/Upgrader.pm line 161 MT::App::Upgrader::upgrade('MT::App::Upgrader=HASH(0x991b18c)') called at lib/MT/App.pm line 595 eval {...} called at lib/MT/App.pm line 559 MT::App::run('MT::App::Upgrader=HASH(0x991b18c)') called at lib/MT/Bootstrap.pm line 44 eval {...} called at lib/MT/Bootstrap.pm line 39 MT::Bootstrap::import('MT::Bootstrap', 'App', 'MT::App::Upgrader') called at mt-upgrade.cgi line 11 main::BEGIN() called at /home/DOMAINNAME/publichtml/mt/extlib/HTML/Template.pm line 11 eval {...} called at /home/DOMAINNAME/publichtml/mt/extlib/HTML/Template.pm line 11

Looks like I was missing the new TMPL folder. After having copied all folders anew, I now have this error:

Couldn't load blog; perhaps you have not upgraded your MT database? - at lib/MT/App/CMS.pm line 367.

Isn't MT-UPGRADE.CGI supposed to upgrade all the scehema etc? What's the separate database upgrade?

Post a comment



Six Apart
Makers of weblog software and services for individuals, organizations and businesses.
This website is powered by Movable Type.