without a doubt, UDT is best ever control Ive seen in any CMS. Idea behind is simply GREAT, but the implementation.....
Now in evaluation stage of project, where I want to use UDT (version 5.0.2) as smart document storage I notified few (small) problems ;)
my UDT structure is:
- document (type download)
- document description (richText)
- approval status (text, list of values: sent to ap., wainting for ap., declined, approved)
- county (text)
- source tab (text with [Porta:tabID] token as this table is on multiple tabs)
- some more fields for search, sort eg.
I have 2000 users (potentially 7000) and everybody will upload at least 10 docs (records) per year....
so first file upload dialog has simply horrible design. For unexperienced users overcompliated, only single file upload control would be much better instead of some browse of server folders and picking file from list of thousands....it tooks me 5 minutes to understand that I must confirm new file upload before submit data...
my user always want to upload new and never wants to select from allready uploaded ( I guess that others would agree in this point with me, data type is download not PickFromExistingHorriblyLongListAndMayBeDownload....)
then 2 users will upload document named meetingMinutes.pdf (both with same name but different content), the latest one will imediatelly overwrite first one in same destionation folder (without any warning !). ok I can define separate 2000 folders for 2000 users.... then setup folder rights,....hm it would take too much effort and also I would appreciate to keep all docs at single place even when opereate in database file system.....
breefly looking into source I found that it wouldnt be to difficult to change default URLControl to some other with better GUI but it solves not to much...
I vote for (and I plan to develop now):
enhance UDT settings properties by DefaultDataFolder for upload and img data types (similar as Document module has). If URLControl will find this property it can show just simple file upload control. May be even PreferUploadView property might be good in this case.... what other thinks about it ?
anyway to dont break compatibility and keep current version UDT,.... For store documents with same filename into single folder I plan to create new data type (Document). This would be almost same as download and img, but this will save into table field value 'OrigDocName=filename.ext;FileID=45', instead of only 'fileID=45' as download type do. Uploaded file will be renamed to {msGUID}.ext and saved as normal file in dnn file system on server db. When render url link to file in tableView user will see original filename instead of {msGUID}.ext. This new Document type would use different UrlControl for download to server with only browse button, so original UrlControl can remain same.
This resolves probably and hopefully all my issues + I can still love my UDT ;-)
Is anybody interested or do have similar problems ? Did I missed something ?
Adam.