From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. bef7ad5bbecbb3ed36d8c3c38fcca67b84487213
Date: Mon, 09 Oct 2017 14:35:33 +0100 [thread overview]
Message-ID: <20171009133534.009BF1081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via bef7ad5bbecbb3ed36d8c3c38fcca67b84487213 (commit)
from 6772cc8035ba6a03b2251380f61cc9a4100d9229 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit bef7ad5bbecbb3ed36d8c3c38fcca67b84487213
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Oct 9 14:34:21 2017 +0100
captive: Fix saving empty terms
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/captive.cgi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/html/cgi-bin/captive.cgi b/html/cgi-bin/captive.cgi
index 92ce453..ae3ebbf 100755
--- a/html/cgi-bin/captive.cgi
+++ b/html/cgi-bin/captive.cgi
@@ -97,7 +97,7 @@ if ($cgiparams{'ACTION'} eq $Lang::tr{'save'}) {
&General::writehash("$settingsfile", \%settings);
# Save terms
- if ($cgiparams{'TERMS'}){
+ if ($settings{'AUTH'} eq 'TERMS') {
$cgiparams{'TERMS'} = &Header::escape($cgiparams{'TERMS'});
open(FH, ">:utf8", "/var/ipfire/captive/terms.txt") or die("$!");
print FH $cgiparams{'TERMS'};
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-10-09 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171009133534.009BF1081BCF@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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