Previous versions of File Storage have not included folder -permissions. (However they did have a concept of private group +permissions. (However, they did have a concept of private group trees.) The reasons for this were to simplify the code and the user experience. However, this system actually caused some confusion (e.g., explicitly granting permission to an outsider on a file in a @@ -192,7 +192,7 @@ The main objects of File Storage are "folders" and "files". A "folder" is analogous to a subdirectory in the Unix/Windows-world filesystem. -Folder objects are stored as Content Repostory folders, thus folders +Folder objects are stored as Content Repository folders, thus folders are stored "as is" in the Content Repository.
@@ -216,7 +216,7 @@ stored in the "title" attribute of cr_revisions. Note that "title" is also used as the (unique within a folder) identifier of the file stored in cr_items. Thus, wrappers to the Content Repository API -makes sure that the naming convention is corect: cr_items.name +makes sure that the naming convention is correct: cr_items.name attribute stores the title of a file and all its versions, while the cr_revisions.title attribute stores the filename of the version uploaded into the Content Repository. @@ -432,7 +432,7 @@ trigger walks through all the contents of the instance of File Storage, and starts deleting from the "leaves" or end nodes of the file tree up to the root folder. Later improvements in Content -Repository will allow archiving of the contents instaed of actually +Repository will allow archiving of the contents instead of actually deleting them from the database.