I'm not sure, to be honest - file storage is a mess internally. Maybe cr_import_content shouldn't force the use of an image content type but only do that by default.
Hmmm ... the reason for having the dimensions there is to allow the generation of height and width attributes to IMG tags that reference CR content (this assumes the index.vuh file is working that allows one to access CR content by URL!)
I kinda wonder how useful this is in practice ... usually we just download content, not reference it, certainly that's the file storage paradigm ...
So how about modifying cr_import_content, then, leaving the default behavior unchanged of course?
