Closed (fixed)
Project:
DataBase File Manager
Version:
5.x-2.2
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
20 Mar 2008 at 12:08 UTC
Updated:
2 Jul 2009 at 08:22 UTC
Jump to comment: Most recent file
Comments
Comment #1
rooey commentedHere are some pretty pictures.
Note tho, if you click on the "help" (?) icon you'll get full help with pictures and everything!
Comment #2
rooey commentedokay - we're putting up a test site to show off how great it is :P
check back on the module page in a few days.
Comment #3
rooey commentedTest site is now available at http://dbfmdemo.lineageone.com/ - give it a few hours for DNS to propagate.
Comment #4
rooey commentedComment #5
rooey commentedComment #6
rogdawg commentedJust for clarity...
If you upload a file that already exists...you get a warning. If you continue with the upload you will OVERWRITE the existing file, correct? There is no way to get back to the original file? So this is not a way to do version control on files, right?
I just want to make sure, because the description says that revision control is possible but, when I think of revision control, I think of being able to recall older revisions, etc. I think I am not using the terminology correctly.
Thanks for any response you can give.
Comment #7
geoff_eagles commentedIf you upload a file that already exists...you get a warning. If you continue with the upload you will OVERWRITE the existing file, correct? There is no way to get back to the original file? So this is not a way to do version control on files, right?
NOPE - you're given the option of EITHER overwriting the file OR starting a 'version'. If you choose overwrite the original file will indeed be lost forever. If you choose to create a new version then a new version directory is created, the original file becomes the first revision, the new file you're uploading becomes the 2nd (and by default, the current) revision. You can continue to add later revisions. You can, at all times, access any revision. You can change which revision is considered the current one. You can set access rules for each revision.
I just want to make sure, because the description says that revision control is possible but, when I think of revision control, I think of being able to recall older revisions, etc. I think I am not using the terminology correctly.
Yup, that's what I think of as revision control too. That said, this is an inefficient way of doing it in terms of the space it takes up. Most revision control systems would store the changes between versions. This always stores the entire document