Last modified: 2012-09-16 07:46:24 UTC
It would be nice if the pagename functions like {{PAGENAME:}} or {{FULLPAGENAME:}}, when used with a parameter, would return an error that's parsable for {{#iferror:}}, instead of failing silently, so that we can get an easy way of determining if a page name is valid and stop using ugly hacks (http://en.wiktionary.org/wiki/Template:isValidPageName for example).
PAGENAME/FULLPAGENAME and its friends returning an empty string, if the title is invalid. You can use {{#if:{{PAGENAME:{{{1}}}}}|valid|invalid}} to check for a valid pagename and does not need a template construct with {{raw:}} Support INVALID
The raw thing is an interesting hack... I don't necessarily think this is invalid imho (since you can't detect an error condition using the #iferror parser func, like you arguably should. Also I more consider invalid bugs to be things that are nonsensical as opposed to things we just don't want to do.) However, it is something that I would consider low-ish priority unless it can be demonstrated it is needed (like for example if duplicatebug's solution is insufficient. I would consider needing to use raw: in such a different way than its desired functionality to be a demonstration its needed) . Before changing this though, one would want to check to see if people are relying on the current behaviour. However, this is super easy to do...
WONTFIX, see comment 1 for alternatives This will break b/c
