Publishing status of live docs should be unaffected by document revisions
complete
Stuart Moore
If you make edits to a published document, and save those edits (dont publish) then the current version of the document changes from published to unpublished.
Impact: while documents are being edited, and corrected the document becomes unavailable to users.
Expect the default behaviour to be the published version remains current AND in the published state EVEN when edits are being made and saved that create new versions.
Only after the edited version has been reviewed, and published should the current live version be replaced by the recently published version.
Caleb Scharf
Awesome! Thanks!
Denis Omerovic
complete
Hey folks,
This is now fixed. When a draft writer submits for review or Save Draft button is pressed, the published version will stay visible. We added another option under Save Draft button, Save Draft and Unpublish in case you want to Unpublish the article.
Katy Gerhold
Denis Omerovic: thank you very much! I still have questions about the versioning though. There may be some tweaks needed to have it make sense because now if you create a new version of a published article without first making any edits, it marks the new version as "Published", and then when you publish the new version, both versions display as "Published" under the Versions menu. It can be really confusing for the authors. I already have mentioned this in a help chat.
Amanda Centorbi
Denis Omerovic: THANK YOU!!!!
Denis Omerovic
Merged in a post:
Stop Drafts from Unpublishing Articles
Katy Gerhold
Just adding another request to the pile as I'm not seeing any movement in HelpJuice on the existing posts about this enormous issue.
Making edits to a published article should NOT UNPUBLISH THE EXISTING ARTICLE.
This is a huge issue that needs to be remedied. Some of our articles have near constant edits and our editors like to add little bits at a time and may take weeks before that draft will be ready for publishing. We need for the current articles to remain published as edits are made on the back end. This is crucial for our knowledgebase to be usable.
Denis Omerovic
in progress
Joel Andrews
I think you may be doing what we used to do early on that resulted in unpublishing the articles - clicking the Save Draft button after making changes. This is a very confusing feature, and it doesn't work the way it seems like it would. When you make changes to an existing published article, but aren't ready to publish the updated version of the article, you don't need to do anything at all after making the changes; the system will autosave those changes. Clicking the Save Draft button is what unpublishes an article. The button should actually be named "Unpublish", or something like that.
Katy Gerhold
Joel Andrews: I've lost changes relying on autosave, it would be very difficult for me to resist clicking that button. thank you for the info!
Joel Andrews
Katy Gerhold: We have also lost changes that we thought were the result of autosave not working, but has usually been because someone else had the same article open in the editor and their version overwrote the updated version, so watch out for that. They don't seem to have worked out all of the kinks in collaborative editing.
Katy Gerhold
Joel Andrews: ideally, when you create a new version of a published article, that draft would be saved apart from the published article. I also can't find any way to undo changes that were automatically saved. I like having a save button for insurance and to manage for myself when and how I save changes. I know there is a revision history, but that is an imperfect way to undo things. It is very confusing, but thank you again for the info!
Denis Omerovic
Merged in a post:
"SUBMIT FOR REVIEW" not unpublishing the article
Lisa Schwetlick
I see that there are similar requests and one closed request for this topic. Submitting an article for review removing the article for reviewers is causing a big issues for us. Please consider changing this function, so the article stays published at all times.
Denis Omerovic
Merged in a post:
Rename 'Save Draft' button and distinguish between unpublished content and drafts
Marissa Fegan
As of now, when you draft edits to an existing article and click 'Save Draft', it un-publishes the article. This is misleading as a Draft shouldn't un-publish the article. Considering that when making edits, the drafts that DON'T un-publish the existing content are saved automatically, the 'Save Draft' button should be renamed to 'Unpublish' as that is a more accurate descriptor of what's happening.
Also, it'd be very helpful if the auto-saved drafts actually show that it's a Draft in the dashboard view, the way unpublished "drafts" do now, and then change the Unpublished article to show as that.
Please see my mock-up example attached.
Denis Omerovic
Merged in a post:
Preventing published articles to go on draft
Jesus Guerrero Chacon
When an user is reading a published article on the backend it often changes accidentally to draft and then this user has to publish again if he/she notices the change (then it will show that person made the last update). Is there any way to prevent this constant change from published to draft?
Katy Gerhold
I see this is under review, just left another similar suggestion to keep the ball moving on this. If I had known prior to selecting HelpJuice that editing a published article pulls it from the knowledgebase, I would've gone with a different product. I need for this to be fixed as soon as possible or our knowledgebase will be near unusable!
Katy Gerhold
This really needs to happen HelpJuice, if I had known every time we make changes to an article that it pulls the previous version from being published until the new one is done and published, I frankly would've gone with a different product! This is deal-breaker type stuff. PLEASE fix it.
Load More
→