FS#1005 Links for namespaces incorrectly generated with useslash enabled

Backend

• 

  2006-12-16 Selkirk

  When useslash is on, the link [[foo/]] should be equivalent to [[foo:]].  It is not.  instead of linking to "/foo/start" it links to "/foo".
  
  This is caused by a link in the resolve_pageid function that specifically tests for the trailing colon, but not a trailing slash.
  
   // if ends with colon we have a namespace link
   if(substr($page,-1) == ':''){
  
  This can be fixed with:
  
   // if ends with colon or slash we have a namespace link
   if(substr($page,-1) == ':' || substr($page,-1) == '/'){
• 

  2007-02-17 gb

  The change should only apply when useslash is ON, so the line should rather be:
  
  if(substr($page,-1) == ':' || ($conf['useslash'] && substr($page,-1) == '/')){
  
  Testing it on darcs revision, it works. But we still have a problem: [[foo/]] is rendered as "start" in the page (the underlying link and the title of the link are ok)
• 

  2007-02-20 gb

  Try the attached patch which attemps to fix both namespace links and titles

  • fix.patch text/x-patch
• Related tasks:
  • FS#1006 Links with a trailing colon or slash have an inconsistent title.