Shared drafts created by the user but never publishedĭrafts that have a corresponding published page won't appear in the drafts list - users can access those drafts by editing the corresponding page. How do shared drafts behave in the drafts list?Ī user's drafts list will be populated with the following drafts: Opening a personal draft will display it in a read-only dialog, from which the user can copy the content into a new page. They won't, however, be able to resume editing the draft in the editor. Personal drafts will still be accessible from users' drafts list. What happens to personal drafts once shared drafts have been rolled out? Once shared drafts have been rolled out to instances, they won't be disabled. What happens when shared drafts are disabled? To find out if shared drafts are supported using client-side Javascript: Checking for shared drafts using Javascript You should ensure that future calls are made to getContentDraft, which will only return shared drafts and doesn't provide support for personal drafts. This allows actions to maintain compatibility with instances that haven't been upgraded to collaborative editing. In order to support shared drafts you need to replace calls to getDraft with getDraftAsCEO, which will return a shared draft on instances that support them or a personal draft on other instances. This method - to be deprecated - only returns the old Draft class, which is incompatible with shared drafts. Prior to shared drafts, actions could access drafts by calling getDraft(). Shared draft support is provided to actions that extend the AbstractCreateAndEditPageAction. This is similar to SharedDraftUpdatedEvent, except that it's fired from the client side and is triggered for both personal and shared drafts. This normally happens at regular intervals in an editing session when a draft is auto-saved. Triggered when a shared draft is updated. Triggered when a new shared draft gets created. We're deprecating the Draft class in favor of using the existing Page and Blogpost classes, where a contentStatus field of draft will indicate the object is a draft.Ĭomparing the personal draft and shared draft models: Personal drafts were represented by a Draft class, which extends ContentEntityObject and contains a draftType field indicating whether the draft was a page or blogpost.Using collaborative editing a single shared draft is created for each page, and anyone editing the page will see the same draft. When editing a page prior to collaborative editing a new personal draft was created for each user, and the changes couldn't be seen by other users as personal drafts are private.We'll call the outgoing model, used prior to collaborative editing, personal drafts, and the new model shared drafts. We're changing the way drafts behave, and moving to a model that's more consistent with how content should be stored for collaborative editing. Shared drafts The shared draft vs personal draft model This page provides an overview of the various components that make up collaborative editing. We'll go through how each component works, and how you can build apps to integrate with them.ĭeveloping for Confluence Server? Head to Collaborative editing for Confluence Server. When using collaborative editing, a page editor will see the avatar(s) of others editing the page, and the changes they make will appear in the editor in real time. Collaborative editing allows multiple people to concurrently edit a single Confluence page or blog post (we'll just call them pages from here on).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |