I'd like to set up a publically-postable blog using MT.

a) I'd like to hide login requirements (userid/pw).

b) I'd like the posters to be able to select from a category menu.

c) I'd like incoming data to post only to draft status, for review later.

d) I'd like to publish some author data (a la comments) with
the posts.

e) I'd like to hide the mt.cgi address from casual scrutiny

I know I can get a, b, and c implemented by simply properly setting up a form with appropriate hidden fields (with the possible exception of "a"). d will require more legwork, I know. e may be best accomplished by implementing a new instance of the mt.cgi suite in a new location.

Is there a less klugy way to implement a-b-c? For example, can I contol "Draft/Publish" in the blog setup panels, and I'm simply missing it?

You may want to try www.postnuke.com.

No sense in making one software do what it wasn't intended to do when there's stuff out there that does it already.



Vincent

I am looking at the nukes.

I have phpnuke operable, and am looking at postnuke.

What's the difference/scuttlebutt on these systems?

I noticed that phpnuke requires register_globals on which made me unhappy.

The only other aspect of concern for me in using the nukes is that they are overkill for my needs at the moment; I've spent some time learning how to make MT jump through hoops and am reluctant to commit to another system.

Words of wisdom from those in the know?

argh - looks like there's infighting on the postnuke dev team. I'll still poke at what I have but I can't adopt it until I know how stable things are over there.