| Summary: | Remove hard coded topic IDs for Help Topics | ||
|---|---|---|---|
| Product: | [Community] PressGang CCMS | Reporter: | Lee Newson <lnewson> |
| Component: | Web-UI | Assignee: | pressgang-ccms-dev |
| Status: | NEW --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.2 | CC: | cbredesen |
| 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: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Lee Newson
2013-11-20 02:45:24 UTC
The solution I had in mind for this was to start all auto-increment primary key values (and therefor any topic ids) for custom deployments at something like 100,000. This means that any content in our internal deployment could keep their IDs without being mixed with any content generated in an external instance. This also means that the topics that make up the help ids would serve as an example topics and content specs as they would be an example book. I'll leave this open for discussion though. |