Closed (fixed)
Project:
Documentation
Component:
Installation
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2005 at 03:04 UTC
Updated:
22 Nov 2005 at 16:49 UTC
Documentation coordintor please set these paths
http://drupal.org/node/36996 upgrade
http://drupal.org/node/36999 upgrade/testsite
http://drupal.org/node/37000 upgrade/basic
http://drupal.org/node/37003 upgrade/optional
http://drupal.org/node/37005 upgrade/testing
http://drupal.org/node/37007 upgrade/finish
http://drupal.org/node/37008 upgrade/livesite
http://drupal.org/node/37009 upgrade/testsite/commandline
http://drupal.org/node/37013 upgrade/basic/commandline
http://drupal.org/node/37013 upgrade/livesite/commandline
http://drupal.org/node/37017 upgrade/dbyesno
http://drupal.org/node/37028 upgrade/basic/nodbupgrade
Comments
Comment #1
cel4145 commentedBefore I implement any of the paths, notice that this is the main upgrade page
http://drupal.org/node/496
not
http://drupal.org/node/36996
and would seem the better place to use the path "upgrade."
Assuming this is the case, the logic of the whole path folder stucture you have created is invalid. Now I've always been on the fence about building a path description based on the book structure itself because it seems to suppose that the structure of the handbooks is static. That is, if we ever decide to reorganize pages, this kind of logical structure then breaks down, and we won't want to change them the paths because of legacy urls.
So would it work just to use upgrade/ for each of the page?
Example,
http://drupal.org/node/37009 upgrade/testsite-commandline
Comment #2
Amazon commentedhttp://drupal.org/node/36996 upgrade
can become upgrade/intro
will that work for you?
Comment #3
Amazon commentedI am fine with not have a nested path structure if that's what you want.
Comment #4
cel4145 commentedDone, with SEO friendly URL's.
Comment #5
cel4145 commented