Zena zena → 1.5

Comments and changes to this ticket

• 

  Gaspard Bucher July 15th, 2010 @ 02:45 PM

  • Milestone set to “1.5”
  • State changed from “new” to “open”
  • Tag set to “apache, enhancement, nginx, url”
  • Milestone order changed from “4” to “0”

  Yes and no.

  We need to solve this issue in a way that if the page title changes (or a parent page), old links pointing to the page will still work. There are tons of blog posts on the internet that just point to 404 errors because the author changed the title or moved the article.

  This is why pretty urls are not really encouraged in Zena until we find a good fix to this problem. I see two solutions that could work better then the current implementation.

  1. keep a list of mappings "url" --> zena node (there is another ticket related to this subject #296 that deals with more then one url pointing to the same page)
     
  2. keep the node id in the url

  For "url safety" (avoid 404 errors) I prefer the second solution. Maybe we could have something like this:

  Default url: "/en/zafu/forms/396-captcha" (if you rename "forms" to "input", we can redirect because of the node id).
  Alias urls: "/anything/that/you/want" --> "/en/zafu/forms/396-captcha" (these must not be changed or the client will get 404).

  In order to keep performance at a good level, the urls need to be cached and stored in an "urls" table that could (ideally) be accessed by Apache/nginx during Url rewrite (so that Zena only sees one url and can cache response).