[DOCS-1517] use of only:: website causes no navigation to be built on certain pages Created: 15/May/13 Updated: 16/May/13 Resolved: 16/May/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | production |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Ed Costello | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 10 years, 39 weeks, 6 days ago |
| Description |
|
If you build docs using make html or make dirhtml certain pages end up with no actual navigation now because the includes are done only if the target is website. Not sure anyone outside 10gen builds the docs but if they do it’s sort of annoying. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 16/May/13 ] |
|
I've rerun publication a few times on linux and darwin, and can't reproduce this result. As an aside there are now nitpick build targets, so you ran run make html-nitpick (or any other builder, so dirhtml-nitpick works, etc), which might make things a bit... better. Cheers, |
| Comment by Ed Costello [ 15/May/13 ] |
|
Example screenshot |
| Comment by Ed Costello [ 15/May/13 ] |
|
/manual/reference/method/ was the page I saw this on (except as http://localhost/manual/reference/method). If the tables don't get included then there's no links into the individual methods. After changing website to html I get the tables included in /reference/method but just noticed that the includes failed on pages like http://localhost/manual/reference/method/js-collection/ even though /includes/table-method-collection.rst exists. Running with NITPICK=1 didn't throw any obvious errors on the includes. |
| Comment by Sam Kleinman (Inactive) [ 15/May/13 ] |
|
pages like, http://docs.mongodb.org/manual/reference/method/, which is the main use of the website tag, have the desired navigation. Orphan pages will drop navigational context, as you'd expect but that's nothing new... |
| Comment by Sam Kleinman (Inactive) [ 15/May/13 ] |
|
Can you provide an example? |