- Allows blog admins to re-attribute authorship to DRAFT posts in a blog
- Additional configuration exists to require that new authors must follow the administrator making the change in order for it to occur. Can be set on a Global or Per Container basis.
- Allows Activate / Deactivate of the Ghost Blog Feature by:
- System-Level (System + User Blogs Share Global Config)
- Space, Group, Project blogs can be configured at the container level
- Note: Group and Project blogs may require the Admin Essentials Plugin to configure
- Audit log support that records authorship changes to the jiveAuditLog table for historical reference (since 1.1.0)
The plugin requires an additional step in the workflow; however, it is quite fluid. Check out this walk-through and instructions to help you get started!
Before you get started:
- Check the Admin Console > Management > Settings > Configure Ghost Blog to insure the feature is activated globally and/or make sure to configure your place specific blogs per the admin UI instructions.
To start ghost authoring a blog post, do these steps:
- Log into your community as yourself, or someone with Blog Admin rights to at least one blog.
- Write a New Blog Post in your desired Blog
- Click the Save Draft button, not Publish
- After the screen refreshes, click on Ghost Publish, (see screenshots, below)
- Start typing the name of the new blog post author, click on the appropriate auto-complete result, and click Save.
- Schedule the Blog Post to be Published sometime in the future
- Note: To avoid mismatches of Activity & Notification authorship, ghost written posts need to be scheduled, and not published manually. (see Known Issues/Disclosures, below)
At this point, the blog post has been created with the authorship attributed to the other user. You can continue to manipulate and modify this blog post given that you are the Blog Admin.
Note: The Ghost Blog Author Switch is only available for Draft blog posts.
Note: Added "Ghost Write this Post" Action Item for DRAFT blog posts
Note: Simple UI to manipulate blog posts authorship for DRAFT blog posts
Known Issues / Disclosures
- Publishing manually after a ghost blog post is scheduled, can result in authorship mismatches between notifications and activity. (See Disclosures, below)
- Ghost written blog posts have to be scheduled to avoid confusion in authorship between Activity and Inbox/Email notifications. If a ghost written blog post is published manually, activity will represent the article author; however, notifications will reflect the ghost author.
- As such, version 220.127.116.11 ads a streamlined workflow that allow scheduling from the Ghost Publish screen.
- Users are advised to make this the last step in the post life-cycle.