public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a421b8038b927529a4ed08c13539f74f66c18f9e
Date: Mon, 01 Jun 2015 15:59:43 +0200	[thread overview]
Message-ID: <20150601135943.F39D723455@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2840 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  a421b8038b927529a4ed08c13539f74f66c18f9e (commit)
       via  91fc30309fcc929ae3b4b88f6cac67e1214e73a9 (commit)
      from  e97d4c98963477b5247005d33acd9d4b5fe1ca8e (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 a421b8038b927529a4ed08c13539f74f66c18f9e
Merge: 91fc303 e97d4c9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Jun 1 15:59:33 2015 +0200

    Merge branch 'next' of ssh://git.ipfire.org/pub/git/ipfire-2.x into next

commit 91fc30309fcc929ae3b4b88f6cac67e1214e73a9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Jun 1 15:56:46 2015 +0200

    dhcp: Enter edit mode after adding a static lease from list
    
    After a lease has been added from the list of leases it is often
    desirable to edit it right away. It appeared that the system
    was in edit mode after the lease has been added because the form
    had the values of the recently added lease, but hitting the
    "Add" button cause an error message that stated that this is
    a duplicate entry.
    
    This patch will switch to edit more where the user can change
    the values and hit "Update". If he or she chooses to ignore
    that the entry is still saved.

-----------------------------------------------------------------------

Summary of changes:
 html/cgi-bin/dhcp.cgi | 3 +++
 1 file changed, 3 insertions(+)

Difference in files:
diff --git a/html/cgi-bin/dhcp.cgi b/html/cgi-bin/dhcp.cgi
index e75207a..dd48d58 100644
--- a/html/cgi-bin/dhcp.cgi
+++ b/html/cgi-bin/dhcp.cgi
@@ -438,6 +438,9 @@ if ($dhcpsettings{'ACTION'} eq $Lang::tr{'add'}.'2') {
 	if ($dhcpsettings{'KEY2'} eq '') { #add or edit ?
 	    unshift (@current2, "$dhcpsettings{'FIX_MAC'},$dhcpsettings{'FIX_ADDR'},$dhcpsettings{'FIX_ENABLED'},$dhcpsettings{'FIX_NEXTADDR'},$dhcpsettings{'FIX_FILENAME'},$dhcpsettings{'FIX_ROOTPATH'},$dhcpsettings{'FIX_REMARK'}\n");
 	    &General::log($Lang::tr{'fixed ip lease added'});
+
+	    # Enter edit mode
+	    $dhcpsettings{'KEY2'} = $key;
 	} else {
 	    @current2[$dhcpsettings{'KEY2'}] = "$dhcpsettings{'FIX_MAC'},$dhcpsettings{'FIX_ADDR'},$dhcpsettings{'FIX_ENABLED'},$dhcpsettings{'FIX_NEXTADDR'},$dhcpsettings{'FIX_FILENAME'},$dhcpsettings{'FIX_ROOTPATH'},$dhcpsettings{'FIX_REMARK'}\n";
 	    $dhcpsettings{'KEY2'} = '';       # End edit mode


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2015-06-01 13:59 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=20150601135943.F39D723455@argus.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