Please pardon, I had posted this as a bug, however it seems I was in remiss in that it seems that one discusses a possible bug (as it might not be) and then if it is a bug, posts it as a bug. . My English is not the best, and this is my first (second as I posted this as a bug) posting in a technical forum, so I appreciate everyone’s patience.
This has been the subject of two previous threads, however, one post originator was excessively rude, so I believe a valid concern was buried under disrespect, also, now dealing with a more intensive production environ and legacy sites, I can perhaps shed more light.
A seemingly common method of organizing a site is to have files represented by .html, and a directory represented by an index.html site within that directory.
- Al la: /content/category/index.html
would resolve to:
would resolve to
Now, if one wants to keep large swaths of their legacy content intact in terms of paths and URLS
one can set Ugly URLS to true in their config file.
This allows one to keep their structure in tact for point “2” above.
However, it does not for point “1” above.
This then leads one to:
As this is an existing site, existing blog (well, many existing sites) their are existing structures, directories, links, hardcoded URLs. Tens of thousands.
One then needs to progress into intensive, highly intensive GREPing, Aliases and/or redirects, which are not optimum.
Of note, their seems nothing actually wrong with the described pattern of file paths explicitly represented (/content/category/this.html) and directories (/content/category/) being represented by (/content/category/index.html). Possibly their is something wrong with that system, however it is somewhat widely in use and that then pushes necessity of use.
It seems that their is a bug in that a relatively common or standard system structure is between the two options of “true” and “false” of UglyURLs, and since most production environs will port existing structures and content it seems an option does not exist that possibly should, to standardly implement the above structure.
I will move forward by creating simply Aliases, but that is a workaround. This is a possible incorrect concept, but, I have found truth in Physical Engineering, where a workaround signifies avenues of valid research and thought (though, albeit, this is a small point).
Only in that I believe this thought process could be a small, more seamless, improvement allowing further use of an excellent tool, I wanted to take the time to share this. Thank you for your time.