public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: menu IPFire > Help goes to help.cgi
Date: Thu, 01 Sep 2022 15:41:10 +0100	[thread overview]
Message-ID: <4276B3F0-844C-4A40-A36A-E05F7F36CC44@ipfire.org> (raw)
In-Reply-To: <B5BF175D-8C4D-44CE-9CF7-29B92C66EB4D@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

Hello Jon,

Very interesting find. There has never been a “help.cgi” file in the code base as far as I can see.

It looks like I added those lines there, but I do not know why and when and what the hell I was thinking.

So, please feel free to create something new.

I am not sure if you will be able to fill a whole page with all those links, but it might be a great place for users to start.

My only thought is that it is probably easier to link the wiki since we can update that a lot easier.

-Michael

> On 26 Aug 2022, at 21:13, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
> 
> All,
> 
> I noticed there is a `help.cgi` WebGUI referenced in the `60-ipfire.menu` file.
> 
> ```
>    $subipfire->{'99.help'} = {'caption' => $Lang::tr{'help'},
> 				  'uri' => '/cgi-bin/help.cgi',
> 				  'title' => "$Lang::tr{'help'}",
> 				  'enabled' => 1,
> 				  };
> ```
> 
> Is this something we can (should?) populate?
> 
> We could add simple items like links to the Wiki, Blog, Community, Bugzilla, etc.
> 
> Or maybe add other items like Location, GitHub, People, Dev Archives, etc.
> 
> Or maybe something else?
> 
> I’m not sure what the original intent was many years ago....
> 
> 
> Jon
> 


      reply	other threads:[~2022-09-01 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 20:13 Jon Murphy
2022-09-01 14:41 ` Michael Tremer [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4276B3F0-844C-4A40-A36A-E05F7F36CC44@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox