Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Rename Objects — The Content UI now allows you to rename an object and its pseudo path, if any. Renaming a versioned object has the effect of marking the existing object as deleted and creating a new object using the new name. The rename dialog alerts you to this behavior if the object being renamed is versioned. (UIC-293)
    See Editing Names, Metadata, and Versions.

  • Delete Versioned Objects —  The Content UI allows precise control over deleting versioned objects, so the object can be deleted (which can be restored), delete the current version from the history, or delete the object entirely, including the version history. (UIC-301)
    See Editing Names, Metadata, and Versions.

  • Fixed: Deleting an object appeared to succeed despite the user lacking delete permission; refreshing the browser revealed that the object was not deleted. (UIC-317)

  • Known issue:

    • After upgrading the Content UI (Portal) and/or Storage UI, the cache must be cleared to get the new version. Either shift-Reload the page or clear the browser cache, then verify that the About page shows the new version. A logout does not fix it nor is it necessary. (UIC-222)

    • A COPY on an erasure-coded object does not succeed if it requests a Content-MD5. This issue affects the Metadata Editor. (SWAR-7980)

...