This is a comment on the module content export function in DNN433

Right now I'm going through the extended drama of exporting portals, templates, file content and actual content.

The dumb bit is that the un-editable file names automatically generated by the module content export functions are inevitably going to cause content to be overwritten and lost unless I make efforts to track the filenames and download each one after each export.

The site I'm exporting has several pages listing cameras. One page has compacts, the next SLRs and the next Video etc. Each page has modules for each brand... Canon, Casio, Canon etc. This is quite typical for a site that lists variations of a product or service.

The module content export function generates identical filenames for these modules even though they are on diferent pages.

Insead of filenames like content.TextandImages.Canon.xml, it should logically at least add the tab/page name to the string, if not the contentpane as well.

content.TextandImages.pagename.panename.Canon.xml would still not be 100% foolproof, but would be a lot more useful.

I'm going to get around it right now by adding a code to each container title manually - the in-place editing of the title makes this feasible. The code I add will be a page and pane reference number.

Them's my 2 cents about that.

Rob