Dominic Hargreaves wrote:
Some work's been done on this - see
- and I'm just looking for comments on this change really. PerfDave, do
can you explain you reason for wanting this? I think it'll help me
understand the value of having it if so. One thing would be for
translation purposes, I suppose?
My personal interest is in disabling the prefixes entirely. I'm running
into situations where Category Foo is just a @REDIRECT to Foo, or
vice-versa, and the same applies to Locales. I don't see any reason to
prefix the node names with "Category" or "Locale" when that
is presented by whether the node is in category "Category" or category
The node http://manchester.openguides.org/?Category_Hitching
that people are confused by the prefixes. Category Hitching is not a
category, it's just a node with that name in front. I suspect it's
called that because the other links in
all start with
"Category" and the user was merely following suit.
I don't see that dropping prefixes will do any harm, other than the
hassle of refactoring the database for *existing* guides, and I think it
will make OpenGuides more usable. However, when it came to implementing
it, I saw #53 and decided to make the prefix a customisable string
rather than a boolean, since I was mucking around with the code anyway.