Red Hat Bugzilla – Bug 970822
Injects are not rendered in the doc preview.
Last modified: 2015-08-09 21:23:16 EDT
Firstly your syntax is incorrect for the injection, it should be <!-- Inject: <ID> --> (note the missing colon), so if that was correct then it would appear on the Docbuilder. However it would not appear on the live preview so I'm gonna edit the title to match that (also made your comment private since it has internal links).
*** Bug 971233 has been marked as a duplicate of this bug. ***
I've implemented a first pass at this in Build 201309171700.
Currently the injections aren't resolved fully and will only display the topic ID instead of the topic title (and the links are useless). It is done this way as it would be too slow to have to fetch each topics information and provide the rendering in a reasonable time frame. To do a full rendering we'd have to asynchronously load and replace the content, in the same way that images are loaded.
As an example see topic 3676 on the test server.
Yep, I corrected the injects at the time (as per an IRC with you) and they then rendered in the published doc.
This extra level of functionality in the test topic is actually pretty good. This way, displaying the injects like this shows you that you have structured them correctly.
Early on, I was making the mistake with injects you detected in Comment#1 because I wasn't getting any feedback from the system that the syntax was incorrect. If new users know that they should see an in-line render of the referenced topic, that is a great visual key for them to know they've "done it right".
For now, I think this solution is fine.
Really the XML validation that is done should also check for any incorrect injection references, however we have BZ#997681 open to fix that issue.
I've also made another minor change to the initial pass. The links that are injected will now link to the editor for the injected topic.
I'm going to mark this as complete since it was released as part of 1.2 and if we want the titles instead of just the ids then a new bug/RFE should be opened.