Submitted by pcfreak30 on Tue, 04/23/2013 - 10:10
There are times when you have a command in history, and even sometimes when you do not, that if you submit a command, instead of executing it, it just shows a blank form again.
For us, we always choose all servers.
Also all servers should include the master server in the cluster from which the command is being issued, but it is not.
The issue is a bit sporadic and I have no good way of definitely repeating it, but it has happened too may times to count. I actually have to copy the command or send a fake submission to get around the bug.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Tue, 04/23/2013 - 15:00 Comment #1
Is there a specific command perhaps that causes this, or type of command?
Submitted by pcfreak30 on Tue, 04/23/2013 - 17:11 Comment #2
No, it can be any text.
Submitted by JamieCameron on Tue, 04/23/2013 - 19:21 Comment #3
Ok, I found the cause of this bug, and will include a fix in the next Webmin release.
Thanks for reporting it!
Submitted by pcfreak30 on Tue, 04/23/2013 - 19:22 Comment #4
Would you be willing to tell me what it was. I would have reported months ago, but just got lazy :P.
Submitted by JamieCameron on Tue, 04/23/2013 - 19:39 Comment #5
Basically, if you hit enter after typing in a command instead of clicking the Run button, it is equivalent to clicking the Clear button due to the way the browser decides which button on the form is the default.
The fix is simple - see https://github.com/webmin/webmin/commit/7a95086e401ad7119782f766be021f90...
Submitted by pcfreak30 on Tue, 04/23/2013 - 19:41 Comment #6
Would you be able to copy the real command shell GUI and have a full history for the cluster as at present you can only have 1 history item and can't re-edit it easily.
Submitted by JamieCameron on Wed, 04/24/2013 - 01:08 Comment #7
It does support multiple history items .. at least once the original bug is fixed.
I will also add a button to edit the previous command.
Submitted by Issues on Fri, 05/10/2013 - 06:21 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.