Bug #18128
special in general: Wrong note on .entryLevel
| Status: | Closed | Start date: | 2008-02-05 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Chris topher | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 4.5.0 | |||
| Votes: | 0 |
Description
This bug is related to #17756:
In front of the tables for the special property there is a note about the usage of .entryLevel which I think is wrong:
NOTE: Don't set .entryLevel for a HMENU when using this option! Also be aware that this selects pages for the first level in the menu. Submenus by menuPbjects 2+ will be created as usual.
I think this is wrong, because you may set .entryLevel with special.keywords.
Solution: Put the entryLevel warning in front of every special.something and leave it out in special.keywords.
Prosit, Uschi
(issue imported from #M7400)
Associated revisions
Fixed bug #18128: special in general: Wrong note on .entryLevel (thanks to Uschi Renziehausen)
History
Updated by Chris topher about 2 years ago
- Project changed from Core to TSref
- Category deleted (
Documentation) - Target version deleted (
0)
Updated by Chris topher about 2 years ago
- Subject changed from TSref, HMENU: splitting up the special table for 4.2 :: special in general to special in general: Wrong note on .entryLevel
- Assignee set to Chris topher
- Target version set to 4.5.0
Updated by Chris topher about 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
I don't think we should add many single notes on which properties are not supported (would give a very long list), but instead better leave it with one note at the beginning of the section only.
I have changed the text to say that entryLevel is generally not supported with the special property except for special.keywords.
Committed in r672.
Updated by Chris topher about 2 years ago
- Status changed from Resolved to Closed