by default, g2 short urls have all a prefix.
e.g. all view (showitem) pages have a /v/ , all downloaditem requests have a /d/ prefix etc.
say you remove this prefix /v/ or /d/ in site admin -> rewrite -> rules.
now a url to album "people" would look like this http://example.com/gallery2/people .
say you create now an album with the name "themes".
the url would look like this http://example.com/gallery2/themes .
now we have a problem since in the gallery2/ folder, we already have a subfolder with the the name "themes" (same for /lib, /modules, ...).
so the webserver would point to the subfolder rather than to the album with the same name.
this is one of the conflicts that could arise. say you still had the /v/ prefix, then the URL would look like this: http://example.com/gallery2/v/themes and there wouldn't be any conflict (in this case).
addtionally, the maintenance task checks the flat URLs for conflicts (if you have the user contributed flat urls module installed).
Posts: 32509
by default, g2 short urls have all a prefix.
e.g. all view (showitem) pages have a /v/ , all downloaditem requests have a /d/ prefix etc.
say you remove this prefix /v/ or /d/ in site admin -> rewrite -> rules.
now a url to album "people" would look like this http://example.com/gallery2/people .
say you create now an album with the name "themes".
the url would look like this http://example.com/gallery2/themes .
now we have a problem since in the gallery2/ folder, we already have a subfolder with the the name "themes" (same for /lib, /modules, ...).
so the webserver would point to the subfolder rather than to the album with the same name.
this is one of the conflicts that could arise. say you still had the /v/ prefix, then the URL would look like this: http://example.com/gallery2/v/themes and there wouldn't be any conflict (in this case).
addtionally, the maintenance task checks the flat URLs for conflicts (if you have the user contributed flat urls module installed).
also see:
FAQ: My Gallery URLs begin with /v/ and /d/, why?