With Scrivito, all processes refer to a specific working copy, an entity not present in Fiona 7. However, since working copies play a central role in the Scrivito world, and since they are required for compatibility with several Scrivito libraries, Fiona 7 emulates two working copies, the “Published Content” and the “Working Copy” (“rtc”).
“Published Content” includes all objects and their released content, “Working Copy” all objects and their edited content. Both emulated working copies are always present and cannot be deleted. It is not possible to create further working copies.
“Published Content” (published) and “Working Copy” (rtc) are the only working copies Fiona 7 uses. The rtc working copy name is historically caused and alludes to earlier versions of Scrivito that were equipped with a runtime configuration for attributes and formats. For editing them, a working copy named rtc (runtime configuration) was required.
In the meantime, the rtc name has become meaningless for Scrivito. However, with Fiona 7, all actions relating to editable or edited content are applied to a working copy with this name. As a user, you do not need to pay attention to it because it's handled transparently for you.
Experienced CMS users may wonder how Scrivito/Fiona-7 widgets are represented in the CMS. To make switching to the new technology as easy as possible, a simple and pragmatic way of modelling widgets was chosen: Every page able to contain widgets is given a subfolder named “_widgets.” In this folder, objects representing widgets are stored.
So, a page that includes several widgets is made up of several objects in the CMS. For strong consistency, the widget objects are linked by the page, making it impossible to inadvertently delete a widget object because link destinations cannot be deleted.
This approach is also advantageous with respect to the access permissions of the widgets. They inherit their permissions from the page containing them.
Binary widget content, e.g. images, may be uploaded using drag and drop. If possible, the uploaded images are stored in the “_uploads” subfolder of the page concerned. If this is not possible, the images are stored in the global “/_uploads” folder. It is essential to grant full access to to this folder to each and every CMS user in order to let them upload and access binary content.
With Fiona 7, content is released on a per-page basis. When releasing, you can select the content associated with the page to be released as well. Widgets are always released. Referenced content (e.g. contacts) and binaries (images, PDF files) are preselected but can be deselected. Linked content can be selected.