jtpolk
05-01-06, 04:37 PM
I was testing out the versioning of files and I set a file version to final - disallowing any further checkout.
When I did that, I could still see the file(s), but I lost the edit icon and check out icons - all fine and well, but that meant that I also lost the ability to delete the file.
When I went to the database, I noticed that the word "final" was in the file_checkout column of the files table in the database.
When I removed the word final, then the edit icons re-appeared and I had access to the edit icon where I could go in and edit the file - in this case, deleting the file(s) - going through the versions.
I've not worked with it more, but the file was not attached to any project - it was under "all".
Is there another way to delete a "final" version of a file other than directly accessing the database and then removing the "final" word? Does this behavior change when it is associated with a project?
I can easily imagine some team member labeling a file as final, but then the client of a project changes their mind and the file will not be used, or someone prematurely labeling a file "final" and then there being a need to "unfinal" the final stamp.
thanks....
Jim Tom Polk
When I did that, I could still see the file(s), but I lost the edit icon and check out icons - all fine and well, but that meant that I also lost the ability to delete the file.
When I went to the database, I noticed that the word "final" was in the file_checkout column of the files table in the database.
When I removed the word final, then the edit icons re-appeared and I had access to the edit icon where I could go in and edit the file - in this case, deleting the file(s) - going through the versions.
I've not worked with it more, but the file was not attached to any project - it was under "all".
Is there another way to delete a "final" version of a file other than directly accessing the database and then removing the "final" word? Does this behavior change when it is associated with a project?
I can easily imagine some team member labeling a file as final, but then the client of a project changes their mind and the file will not be used, or someone prematurely labeling a file "final" and then there being a need to "unfinal" the final stamp.
thanks....
Jim Tom Polk