Bug 836450

Summary: RFE: provide a notice when a book is not editable
Product: [Other] Topic Tool Reporter: Joshua Wulf <jwulf>
Component: FUDCon Docs HackAssignee: Joshua Wulf <jwulf>
Status: CLOSED CURRENTRELEASE QA Contact: Joshua Wulf <jwulf>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.0.xCC: lcarlon, topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-22 09:06:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-06-29 06:42:43 UTC 
To be editable in the system, a book needs to be built with buglinks turned on, which requires  a BZPRODUCT and BZCOMPONENT to be set in the content spec. 

We can't do this client-side unintrusively. (it could be done by saving the current version of the spec, writing a new version with these things turned on, pushing that, building, then restoring the old state; but that's intrusive)

So we rely on the author having the spec setup on the server in a particular way. When a book is built for some other purpose, it may have these things turned off, which will make docs hack system builds uneditable. 

In that case, the system should float a notice on the book saying what's up, and how to fix it.
Comment 1 Joshua Wulf 2013-04-22 09:06:27 UTC 
Fixed now that we can force bug links on.