Bug 839460
Summary: | RFE: xrefstyle on injected links | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Joshua Wulf <jwulf> |
Component: | CSProcessor | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 1.x | CC: | jwulf, lcarlon, mcaspers |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 0.25.2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-07 01:30:04 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: | |||
Bug Depends On: | |||
Bug Blocks: | 842673 |
Description
Joshua Wulf
2012-07-12 02:32:55 UTC
I've added those "xrefstyle" attributes the the xref links for 0.25.2. I'll take a look at command line option at a later stage since it's not very high priority atm. Oops forgot to mention that the only change i made to the xrefstyle names is to call "link-list" instead of "link" Moving this back to MODIFIED as it's not complete. Maybe the thing to do with issues like this is to split them into separate sub-features? That way when something gets released, the bug that tracks it changes state. Just to add to my last comment about what's not complete. I still need to look at the command line option to turn off the xrefstyle injections. However that is a low priority. Also note that it won't be a publican.cfg option as those variables are for publican. If you want it added to there so that publican removes all the xrefstyles then you'll need to create an RFE in the publican bug queue. As per your suggestion I'm splitting this into two bugs to mark this one as ON_QA. New bug for the switch: Bug #843451 Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it. |