Bug 3611

Summary: Convert website to absolute paths (and use MultiViews)
Product: openclipart.org Reporter: Jonathan Leighton <j>
Component: websiteAssignee: default user for a product <clipart>
Status: CLOSED INVALID QA Contact:
Severity: normal    
Priority: medium CC: da
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Jonathan Leighton 2005-06-23 14:01:29 UTC 
We discussed this on the list -- it's not a major problem, but this bug can
serve as a reminder that we want to slowly transition over to absolute paths
from the current relative ones.

Things that need to be done (in order):

 1) Edit wiki page to explain that people need to set up a vhost rather than
putting the website into a directory
 2) Turn on MultiViews -- non MultiViews URIs could be redirected to the
MutiViews version (having multiple URIs for one resource is a bad idea)
 3) Gradually edit the relative paths in the markup to become absolute
 4) Remove the then-redundant $site_root stuff

Again, this is not a top priority so it can be a gradual thing. It would be good
if people start using absolutes by default from now on though; the two can co-exist.
Comment 1 Jonathan Leighton 2005-08-04 04:29:49 UTC 
Right, number 1 and number 2 are done. I realised the redirect thing was a bad
idea because:

a) It would be extra load of fd.o, which we can't justify for *EVERY PAGE* (as
in, once it's converted, it wouldn't be such a bad idea)
b) It messes things up. For instance, if you access /discussion.php as
/discussion/, relative links because /discussion/whatever.

So I'm going to have to embark on the fun activity of going through the entire
site and using absolute paths with no file extensions. Oh well!
Comment 2 Jonadab the Unsightly One 2005-08-17 05:06:41 UTC 
*** Bug 4122 has been marked as a duplicate of this bug. ***
Comment 3 Jon Phillips 2006-09-07 16:10:40 UTC 
Yeah, this is irrelevant now...and is not really a bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.