Beta 2 coming; nightlies on hold
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.
We will most likely be releasing a beta-2 version on Monday as well as the beta version of the new documentation. This should help shed light on anything that is unclear with the new version.
Aside from the bug fixes, one of the most important changes (in terms of MT setup) is that we are combining mt.cfg and mt-db-pass.cgi into one file called mt-config.cgi. We will be distributing this file as mt-config.cgi-original. Because of the -original suffix, new users will be required to rename the file (to mt-config.cgi upon upload) and existing users won't have to worry about overwriting their config file. The CGI extension eliminates the possibility of viewing the file in the browser.
Because we are undergoing this rearrangement, I've held up the nightly builds, to avoid having anyone confused by this.
We thank you again for your patience and your participation in the beta.
Posted on July 17, 2005 2:14 PM in Announcements
Comments
I understand the .original suffix to avoid some of the problems with files getting overwritten during an upgrade. What is the purpose of the combining the files though? Also, isn't this a rather significant change to be making at this late juncture? Seems like asking for trouble for little to no gain to me.
Posted by: Timothy Appnel![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
July 18, 2005 8:30 AM
My guess is that it'll help stem the tide of users overwriting their existing mt.cfg file and losing all their settings (for the many who are still on 3.17 or less). It's easier (more time/cost effective) to get people to just copy the info over from mt.cfg than to allow the possibility of users accidenatally wiping mt.cfg and then having to help them figure out what the settings should be. The lesser of two evils basically :) Of course the reason(s) may be completely different.
Posted by: demonsurfer![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
July 18, 2005 9:07 AM
oh, the question was about combining the files.. hmm. probably same reason? Novice users not knowing their DB password and overwriting the file maybe? shrug I guess for new and future users it makes more sense having everything in one place..
Posted by: demonsurfer![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
July 18, 2005 9:11 AM
"-original" to avoid overwriting. We never want to do that again and we apologize the problems that any of you had with beta-1 (although we did warn users not to install it on a production site and not to do anything without full backups...)
Combination of the two files just makes things easier. You should not have to edit two files to specify four or five config directives necessary for startup. The new mt-config.cgi will include a new directive called DBPassword.
The .cgi extension stops viewing via a web browser which is important for keeping your database password protected.
Just to be clear, all of the current plugins and MT scripts which specify mt.cfg in their bootstrapping will continue to work as MT will first search for the specified config file (mt.cfg) and if it's not found will roll over to mt-config.cgi.
Posted by: Jay Allen![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
July 18, 2005 1:16 PM