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.
Right, number 1 and number 2 are done. I realised the redirect thing was a bad
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!
*** Bug 4122 has been marked as a duplicate of this bug. ***
Yeah, this is irrelevant now...and is not really a bug.
on Jan 24, 2017 at 21:24:54.
(provided by the Example extension).