Submitted by Locutus on Fri, 06/10/2011 - 03:58
Maybe I'm understanding the function of these (newly introduced? can't recall them from before) buttons incorrectly, but...
In the "Install Scripts" screen, each script now has a green "go!" button besides the version number. I was assuming that those should call up the installation screen for the respective script immediately, without having to select the script via radio button and scrolling down to "Show install options".
But clicking a green button without selecting the script's radio button says
Failed to install script : None selected
And when I e.g. radio-select "Typo" and click the green button besides "WordPress", it wants to install Typo.
This does look like a little bug to me. :)
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 06/10/2011 - 15:27 Comment #1
Yes, that is now they are supposed to work .. and they do work OK for me.
Which browser and version are you using there?
Submitted by Locutus on Fri, 06/10/2011 - 18:37 Comment #2
My first test was only with Opera 11.11, but I just additionally tried it with Firefox 4.0.1 and IE 8.0. Same behavior on both.
It occurs both on my production and the experimental installation which are completely independent. Both systems are Ubuntu 10.04 64-bit and Virtualmin 3.86.
Would you like a login to the system so you can make some tests for yourself?
EDIT: Actually, your login to "lyra.tianet.de" is still active from last time you tested stuff. ;)
Submitted by JamieCameron on Fri, 06/10/2011 - 18:57 Comment #3
Yes, a login would be useful ... but please re-send me the IP and password, as I get so many messages about customer systems that I may not be able to find yours :-)
Submitted by Locutus on Fri, 06/10/2011 - 19:24 Comment #4
:-)
No problem, I'll disable and re-enable it (using the Support Login Privileges function). That should send you a notice, as far as the execution log told me. :)
Submitted by JamieCameron on Fri, 06/10/2011 - 23:54 Comment #5
Ok, I see the bug that is causing this now .. it is browser-specific, and unfortunately worked fine in my browsers :-( I will fix it int the 3.87 release.
Submitted by Locutus on Sat, 06/11/2011 - 03:51 Comment #6
Okidoki, thanks, and no biggie! I sure understand browser issues like this; also it was merely a little inconvenience and not a real problem.
Out of curiosity: with which browser(s) did you test it? I though that IE+Firefox+Opera would quite cover most of the active browsers out there? :)
Submitted by JamieCameron on Sat, 06/11/2011 - 12:12 Comment #7
Mainly Chrome ..
Submitted by Issues on Sat, 06/25/2011 - 16:51 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.