From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)]
Date: Tue, 5 Jul 2022 11:22:39 +0700 [thread overview]
Message-ID: <ta0eah$bcd$1@ciao.gmane.io> (raw)
In-Reply-To: <87tu7w8dqc.fsf@gmail.com>
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.fsf@gnu.org/
>>> I've now installed the rewrite rules on the server and all these links
>>> are redirecting correctly. Given the amount of Org documentation links
>>> living out there, that's really a good idea.
Tim, is there any chance that Bastien forgot to send you some included
file for nginx configuration? However, the site ignores this file even
it exists somewhere on filesystem.
>> Tim Cross:
>>> At this point, my vote is to just do a basic updated 404 page that
>>> points to the index.html page for orgmode.org
>>
>> For the manual and for the guide directories I still consider links to the table of
>> contents (or even full table of contents) on 404 pages as a better variant.
>
> I don't really care what specific page is linked to - just that we keep
> it simple and have a link for an initial quick fix. Only reason I
> mentioned the index.html page is that it has links to everything - worg,
> git, manual, mail list etc. It is possible that people get to 404 via
> links other than to the manual.
I do not have ready to use snippet, but I am sure it should be possible
to set specific 404 pages for particular directories like the manual and
the guide. Of course, these pages, besides links to table of contents,
may have another link to index.html or a navigation header shared with
other pages on the site.
next prev parent reply other threads:[~2022-07-05 4:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:01 [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)] Rudolf Adamkovič
2022-07-03 11:50 ` Ihor Radchenko
2022-07-03 12:23 ` Tim Cross
2022-07-03 14:01 ` Ihor Radchenko
2022-07-03 16:48 ` Max Nikulin
2022-07-03 21:30 ` Tim Cross
2022-07-04 12:10 ` Ihor Radchenko
2022-07-04 12:27 ` Tim Cross
2022-07-04 12:58 ` Ihor Radchenko
2022-07-04 17:24 ` Max Nikulin
2022-07-04 22:37 ` Tim Cross
2022-07-05 2:39 ` Max Nikulin
2022-07-05 2:54 ` Tim Cross
2022-07-05 4:22 ` Max Nikulin [this message]
2022-07-05 4:36 ` Tim Cross
2022-07-05 5:11 ` Ihor Radchenko
2022-09-18 9:06 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ta0eah$bcd$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).