AFAIK, we still need to check out CSP maps to add new topics, but an "Edit the CSP Map" link would be very useful for minor edits such as: * moving around topics/sections/chapters * commenting out topics, uncommenting topics * changing book metadata I know a UI is being developed for the CSProcessor but maybe a greasemonkey script or something like that could be created in the interim for minor content spec changes?
*** Bug 1008292 has been marked as a duplicate of this bug. ***
I'm changing the priority in an attempt to point out that this feature is sorely needed. All that's needed here is a small link that allows you to Edit <Current CSP MAP> in the CCMS rather than open up a new CCMS tab, paste the CSP Map manually and edit it.
You can do this from the index by clicking the ID, as for inside the book it should be implemented in the csprocessor builder. I'll make a note of bringing it up when we have the next sprint planning meeting.
Created attachment 833394 [details] Edit this spec link
Marking this as ON_QA as what Matt implemented is probably better then including it along side the "Edit this topic" link.
Awesome, thanks team!
The content specs popover lists the content specs that the topic is included in, including the current spec. The pencil icon to the left of the spec is a link to edit the spec in the web ui.
Created attachment 833402 [details] Edit content spec
FailedQA: I tried to edit this spec (Infinispan Query Guide for JDG). It took me to edit the Content Spec Map for the Hibernate Search Guide for WFK. These two guides share a lot of content but I'm not sure why it can't tell the IDs apart. Additionally, just a RFE, it would be great if this opened the map in a new tab by default.
Adding to this, the spec id used in the "Report a bug" links is also incorrect.
Fixed in the Docbuilder-Next, however a mass rebuild will need to be performed to fix any existing books. Cause: The id that was being set for SPEC_ID was being pulled from the "specId" variable however it should have been using "id" variable since it was in a callback and id was the reference what "specId" was when the process was started. As such there was a race condition and "specId" was being changed before the callback was executed.
Moving to ON_QA since a mass rebuild has been triggered.
Tried a couple of books and the edit spec link worked ok in all cases.
Looks like this is the offending commit that caused this regression: https://github.com/pressgang-ccms/DocBuilder2/commit/f74130af4c26a0c3b5a826e272c1b2f4b5a2973e
Regression has been fixed and DocBuilder has been updated. Moving to CLOSED CURRENTRELEASE. See: https://github.com/pressgang-ccms/DocBuilder2/commit/8eb2afc51616f051a9fb9f95b2a144a6fa19ec4c