Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

Forums » Features / Usability » Old Problem: Slash in Page Names
 
Thread actions
Print this page
  • Print all pages

    • Old Problem: Slash in Page Names

    Posted by Kya posts: 2

    Hello,

    I've seen this problem isn't new, but none of the replies to earlier threads seem to apply resp. solve our problem.

    We recently upgraded from 3.9 to 12 (*cough*, I know). We ran into problems regarding the formatting of page names. A lot of our old page names have "/" in them, and they do seem to work all right. (They're being linked to within the wiki by using "%20" url encoding.)

    But in the new version we can no longer create page names with "/" in them, we get the error message:

    The page name specified contains unallowed characters. It will not be possible to save the page until those are removed: /?#[]@text+;=

    Since the old pages still seem to work, we're wondering if there is a way to enable the use of slashes in the (current) version 12?

    Special characters like accented characters and punctuation marks can be used in page names without causing problems. It's really just those characters listed in the error message that, well, cause the error message. :P

    A suggested workaround with URL or HTML encoding (%20 resp. /) doesn't work, as the html encoding contains invalid characters and the url encoding is not parsed and appears as "%20" in the page name on the page itself.

    It's not really that much of a big issue with totally new pages, but during the upgrade process we lost some pages and also some of the special character encoding in existing name pages and we cannot fix those because we cannot save fixed name pages that contain "/". (It's a problem because we'll have to manually fix all the referring links on other pages if we rename/re-create the pages.)

    Reads: 2512

    Posted by Tom Jarvis posts: 215

    In addition to Rick's instructions, if you use page names with slashes, you can not use the "Search engine friendly URL" option. Make sure you do not select that option in Features, Global Features tab.

    Tom


    Posted by Kya posts: 2

    Hi guys,

    thanks for your replies.

    Special characters like accented characters and punctuation marks (those only allowed under the "Complete" option according to the documentation) are already working, so I thought there may be another trick to it.

    We'll try turning off the Search engine friendly URL feature.