From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Possible bug in 'backup.cgi' after these commits!?
Date: Sat, 15 Sep 2018 13:00:56 +0200 [thread overview]
Message-ID: <8c83cb8a-f1d4-f8b0-130e-5e8d47df6dd6@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi,
I don't know if this will become relevant, but...
I tested these two commits:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=7f6257e0a475681ff243ead159cafee2e03f6265
and
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=614764e58af6dd710658fd072ed9b3a1b51f805a
Keen to experiment (as I am), I installed the new 'backup.cgi' on my
running Core 123.
After this, GUI looked normal. I could still make backups. But I
couldn't delete the addon backup files. After clicking on the 'delete'
icon, GUI disappered, came back partially (as it seemed, only the
header) and after hitting 'reload', the addon backup files (*.ipf) were
still there. IPF-file rights seemed to be ok, but I couldn't delete them
through the GUI.
Can anyone confirm? Or is it my mistake?
Best,
Matthias
next reply other threads:[~2018-09-15 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 11:00 Matthias Fischer [this message]
2018-09-15 11:10 ` Michael Tremer
2018-09-16 19:38 ` Matthias Fischer
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=8c83cb8a-f1d4-f8b0-130e-5e8d47df6dd6@ipfire.org \
--to=matthias.fischer@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