Sorry I'm late to fixing this.
I reinstalled the rewrite rules on the server and I configured nginx
to use the errors pages that Tim already created.
We should be covered for most problems, but let me know if we need to
do more.
Thanks!
Ihor Radchenko writes:
> If someone else is willing to
Tim Cross writes:
> If you or others want to look at the 404 page issue, please do so. For
> right now, I'll just do a basic 404 page which Bastien can install
> easily. If you or others come up with something more sophisticated, it
> can be used to replace the simple basic version, otherwise we
Max Nikulin writes:
> On 05/07/2022 09:54, Tim Cross wrote:
>> Max Nikulin writes:
>>> Bastien. Re: Possible bug report: URL capitalization in online manual. Mon,
>>> 10 Feb 2020
>>> 07:48:21 +0100 https://list.orgmode.org/874kvzdjka@gnu.org/
I've now installed the rewrite rules on
On 05/07/2022 09:54, Tim Cross wrote:
Max Nikulin writes:
Bastien. Re: Possible bug report: URL capitalization in online manual. Mon, 10
Feb 2020
07:48:21 +0100 https://list.orgmode.org/874kvzdjka@gnu.org/
I've now installed the rewrite rules on the server and all these links
are
Max Nikulin writes:
> On 05/07/2022 05:37, Tim Cross wrote:
>> Max Nikulin writes:
>>>
>>> However it seems, Bastien earlier configured a set of rewrite rules mapping
>>> old file names
>>> with more lower case letters to new ones. In my opinion it is the best
>>> option and it
>>> should be
On 05/07/2022 05:37, Tim Cross wrote:
Max Nikulin writes:
However it seems, Bastien earlier configured a set of rewrite rules mapping old
file names
with more lower case letters to new ones. In my opinion it is the best option
and it
should be restored. List of files may be committed to git
Max Nikulin writes:
>
> However it seems, Bastien earlier configured a set of rewrite rules mapping
> old file names
> with more lower case letters to new ones. In my opinion it is the best option
> and it
> should be restored. List of files may be committed to git (either Org or
> site) to
On 04/07/2022 19:58, Ihor Radchenko wrote:
If JS is the only option it is still better to have it and fall back to
more generic page if JS is not supported. Of course, given that the JS
code is not going to be too complex and not going to require too much
maintenance.
It is possible to
Tim Cross writes:
>> This sounds like a good idea.
>> I am not sure if it is feasible, but the 404 page could also provide
>> suggestions based on similar existing links. I have something like
>> https://list.orgmode.org/orgmode/83tu89b7pr@gnu.org/ in mind.
>
> Sorry, I don't understand the
Ihor Radchenko writes:
> Tim Cross writes:
>
>> I do have an alternative suggestion which may help. Given that the
>> 'broken' URLs are actually from external links to old documentation
>> which has been removed, what we could do is create a more informative
>> 404 page. Once users are on the
Tim Cross writes:
> I do have an alternative suggestion which may help. Given that the
> 'broken' URLs are actually from external links to old documentation
> which has been removed, what we could do is create a more informative
> 404 page. Once users are on the 'real' site, the case issue does
Max Nikulin writes:
>>
> I noticed that the Org documentation server gives 404 Not Found for a
> large number of links published all over the internet because (1) it
> parses URLs case-sensitively and (2) the case has changed at some point.
> I stumble upon such 404s errors
I noticed that the Org documentation server gives 404 Not Found for a
large number of links published all over the internet because (1) it
parses URLs case-sensitively and (2) the case has changed at some point.
I stumble upon such 404s errors daily. See, for instance, the link to
Column
Tim Cross writes:
>>> I noticed that the Org documentation server gives 404 Not Found for a
>>> large number of links published all over the internet because (1) it
>>> parses URLs case-sensitively and (2) the case has changed at some point.
>>> I stumble upon such 404s errors daily. See, for
Ihor Radchenko writes:
> Rudolf Adamkovič writes:
>
>> I noticed that the Org documentation server gives 404 Not Found for a
>> large number of links published all over the internet because (1) it
>> parses URLs case-sensitively and (2) the case has changed at some point.
>> I stumble upon
Rudolf Adamkovič writes:
> I noticed that the Org documentation server gives 404 Not Found for a
> large number of links published all over the internet because (1) it
> parses URLs case-sensitively and (2) the case has changed at some point.
> I stumble upon such 404s errors daily. See, for
Hello again!
I noticed that the Org documentation server gives 404 Not Found for a
large number of links published all over the internet because (1) it
parses URLs case-sensitively and (2) the case has changed at some point.
I stumble upon such 404s errors daily. See, for instance, the link to
17 matches
Mail list logo
