I'm not one to complain, but...

[rant]

Yet again I find that one of the most intuitive, flexible site templates is hobbled for no good reason. Why on earth is the Multipage Meeting Workspace so restricted compared to the Team Site???

To begin with, lets take the function for 'save site as a template'....
- Team Site - 'save site as template' allows for inclusion of content. Great, nice one, useful feature that.
- Multipage Meeting Workspace - 'save site as template' DOES NOT allow for inclusion of content. WTF?? why on earth should I be restricted in this site?? maybe some people use this template for other things than meetings because we find the page tab layout extremely useful. This was a problem in 2003, why the hell hasn't it been fixed in 2007??

And then today I discovered another shortcoming that may not be quite so apparent. The new 2007 feature 'Send to location'...
- Team Site - document: Send to > Other location, add location (by typing instead of a browse function, hello? is this 2007??), send - file is copied. Ok. 
- Multipage Meeting Workspace - document: Send to > Other location, add location (grr), send - ERROR! "There were errors copying to this location. The destination is in a meeting workspace, which does not support this action."  DoH!!
I'm speechless. No, really.
Hello!!?? is there any light on in the MOSS development office??? WHY is this not possible in the Multipage Meeting Workspace site??? For what possible reason would I not want this feature available in this site template???

And do you know how I discovered this?? In testing the workflow features of SharePoint Designer in a Multipage Meeting Workspace site.

cue..

[subrant]

Somehow the development team for SharePoint Designer forgot to include the workflow function to allow MOVE document from one location to another. Instead you have to COPY the document to the destination location and then DELETE the original!!

Words begin to fail me at this point. Why on earth was this feature overlooked?? 9 times out of 10 a user will probably want to move a document rather than duplicate it. Surely this can't have been difficult for the development team to include??

Now I have to deal with a substandard method for getting a document from one location to another and finding that the DELETE step in the custom workflow causes the document in the target location as well as the origin location to be deleted!! Probably because this is a, you guessed it... Multipage Meeting Workspace site.

[/subrant]

And in case you're wondering, yes, the workflow function for copying a document from one location to another on a Multipage Meeting Workspace site works even though you can't do it via the drop menu 'Send to > Other location' options in the library!!!  o_0

[/rant]