Suggestion: import/export should include basenames and tags.

Reasoning: while I export my database on a regular basis, I worry about database corruption; further, while I have not had problems myself, I have been told that restoring from database backups can be tricky.

Right now, export files contain neither basenames nor tags. If basenames and tags were properly exported and imported, then I could completely recreate my blog with just a copy of my templates and an export file--plain text files, much less mysterious and easier to deal with.

This would save me a great deal of work in the case of a database crash, and seems like a fairly simple feature to implement.

***

I'm posting this here first, before submitting a ticket, because I'd like input on whether this is actually a difficult thing to do. I'm frankly disappointed to see that people have been asking for basename export for years, literally, without it being incorporated; if it were incredibly difficult, then I would understand a bit better, though I still want it.

The best thing to do is back up your entire database. That way you get the templates, settings, etc plus the tags and basenames.

http://www.learningmovabletype.com/archive...p_your_blog.php

Yes, I know, and I do back up my entire database. However, I am aware that other people have had database crashes/corruption, and so as I said in my original post, "This would save me a great deal of work in the case of a database crash."

Considering that export already includes categories & keywords, among other things, I don't see why it doesn't also include basenames & tags.

Enhancing the import/export routines is on the Feature Request list. I've also read in ProNet that someone is working on a plugin that will export everything into a nice, easy to use format so that you get all of your blog settings in addition to all of the data for your entries and comments. I haven't seen an update on the plugin lately though.

You mention corruption as a reason you don't like to back up the whole database. Your MT install is dependant upon that database, though, and if it does corrupt the export/import function won't help you at all because... well, it's corrupt.

You might find the export/import function more friendly than phpMyAdmin (or whatever you use), but it's certainly no safer.

Dan

An update is coming though it will be quite a while until a solid, public release