Webmin / Bugs / #5106 Buttons not working in 1.881

Kay - 2018-03-29

try the following

update authentic-theme 2 times!

run 'update-from-repo.sh' from within webmin dir

.
2 times updating authentic-theme is needed to get the last version of update script ...

Last edit: Kay 2018-03-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- James Hawkins - 2018-03-29
  
  Which webmin directory?
  
  /etc/webmin
  /var/webmin
  or
  /usr/libexec/webmin
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ilia Rostovtsev - 2018-03-29

Kay, why 2 times? :) The script will be uodated on the first go - always.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kay - 2018-03-29

Theme version Authentic Theme 19.09.2

IIRC this version had not the update for update script implemented 😇

Last edit: Kay 2018-03-29

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- James Hawkins - 2018-03-29
  
  So that will not work? Is there a solution that I can do?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Kay - 2018-03-29
    
    simply ignore side discussion between us ...
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ilia Rostovtsev - 2018-03-29

Ah, right.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kay - 2018-03-29

inside /var/libexec/webmin , give it a try ...

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

James Hawkins - 2018-03-29

Ok I got the theam updated and it still does not work

Authentic Theme 19.11

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kay - 2018-03-29
  
  also run update-from-repo after second theme update?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - James Hawkins - 2018-04-02
    
    I just tried updating again and no change in the way it behaves.
    
    Webmin version 1.881.0401.1726
    Theme version Authentic Theme 19.12
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ilia Rostovtsev - 2018-03-29

Which module you're talking about in particular? Did you try incognito tab in Chrome?

Try to pkill -9 miniserv and then restart Webmin and Usermin (in case you have it)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- James Hawkins - 2018-04-02
  
  I just tried in in "Incognito" mode in chrome and it is not working. I also killed the miniserv process and restarted which did not make a difference.
  
  The quickest way to reporduce it is
  
  "Webmin" --> "Webmin Users" --> "Create new webmin group" --> Fill in group name, description, and select modules --> "Create"
  
  It will not let you click on Create. However it is the same in add users, import users, Creating ISCSI interfaces, etc.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Rick McCarty - 2018-08-25

I saw the same issue with 1.890 (fresh install) on Ubuntu 18.04, but only on an older version of Chrome (v49). I can navigate around and display everything but none of the action buttons work, essentially rendering Webmin unusable. Newer browser versions (Chrome 68. FF 62) seem to work for me. Not sure what version of FF the OP was using, but even FF 52 appears to work fine.

In case it is helpful, on Chrome 49, I see this in the console output (console output on the other browsers I tested is clean):

Navigated to https://aphid:10000/
Welcome to Authentic Theme 19.19
https://github.com/authentic-theme/authentic-theme
jQuery.Deferred exception: Object.values is not a function TypeError: Object.values is not a function
at slider_check_notifications (https://aphid:10000/unauthenticated/js/bundle.min.js?1919999999999911:234:11276)
at HTMLDocument.<anonymous> (https://aphid:10000/unauthenticated/js/bundle.min.js?1919999999999911:246:29050)
at f (https://aphid:10000/unauthenticated/js/bundle.min.js?1919999999999911:3:8915)
at p (https://aphid:10000/unauthenticated/js/bundle.min.js?1919999999999911:3:9218) undefined
Uncaught TypeError: Object.values is not a function
slider_check_notifications @ bundle.min.js?1919999999999911:234
(anonymous function) @ bundle.min.js?1919999999999911:246
f @ bundle.min.js?1919999999999911:3
p @ bundle.min.js?1919999999999911:3
Uncaught TypeError: Object.entries is not a function
render @ VM26185:1
(anonymous function) @ VM26185:1
Uncaught TypeError: Object.values is not a function
slider_check_notifications @ bundle.min.js?1919999999999911:234
(anonymous function) @ bundle.min.js?1919999999999911:234</anonymous>

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ilia Rostovtsev - 2018-08-25

Hi, Chrome 49 is 2.5 years old. Do you believe we should support it? If so, please explain why.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Rick McCarty - 2018-08-26
  
  Hi Ilia,
  
  Not suggesting that, although I do happen to have an old Vista machine I use sometimes for which updates past Chrome 49 are unavailable. I happened to be using it to access my home lab Linux system today when I ran into the issue. (But I also have a FF browser on it that does work.)
  
  That said, in my day job I run a fairly significant commercial web site, and while newer versions of Chrome are more prominent, over 9% of traffic over the past couple of days has surprisingly come from Chrome 44.
  
  However, if you feel supporting older browser versions isn't worth it, it wouldn't be unreasonable, considering the typical Webmin user should be able to get their hands on a browser version which works. But it might be worth considering detecting Chrome 49 or earlier at login and letting the user know they are using an old browser which may not work.
  
  Best regards,
  
  Rick
  
  From: Ilia Rostovtsev qooob@users.sourceforge.net
  Sent: Saturday, August 25, 2018 4:08:41 PM
  To: [webadmin:bugs]
  Subject: [webadmin:bugs] #5106 Buttons not working in 1.881
  
  Hi, Chrome 49 is 2.5 years old. Do you believe we should support it? If so, please explain why.
  
  [bugs:#5106]https://sourceforge.net/p/webadmin/bugs/5106/ Buttons not working in 1.881
  
  Status: open
  Group: 1.880
  Created: Wed Mar 28, 2018 04:12 PM UTC by James Hawkins
  Last Updated: Sat Aug 25, 2018 08:14 PM UTC
  Owner: nobody
  
  Create button not working in lots of places. For example, create webmin user, create webmin group, create a new custom commend, etc. It make the whole thing unusable.
  
  At first I thought it was with the chrome browser I use so I tested it in firefox and get the same responce. I have also tested the 10 servers I have upgraded and all of them seem to be broke now.
  
  Also the button to change the theme does not work and if i try to do it in the miniserver config it failed to load with the following when I changed it to gray-theme.
  
  "
  /unauthenticated/sorttable.js : File not found
  /unauthenticated/gray-reset-fonts-grids-base.css : File not found
  /unauthenticated/gray-virtual-server-style.css : File not found
  "
  
  Under the authentic-theme I only get the following error.
  
  Use of uninitialized value in string eq at /usr/libexec/webmin/acl/edit_group.cgi line 103.
  
  Webmin version 1.881
  Theme version Authentic Theme 19.09.2
  
  Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/webadmin/bugs/5106/
  
  To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
  
  Related
  
  Bugs: #5106
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ilia Rostovtsev - 2018-08-26

Okay, Rick. Letting user know to update their out-dated browser is a good thing to do. You are right.

Thanks, I will do it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ilia Rostovtsev - 2018-08-26

Rick, I have made a patch to address your issue. It will not produce any waring messages, but just should work.

Adding polyfills is easier and user friendlier than a warning message.

Please give it a try in your old Chrome browser and let me know if it works fine for you? You can simply replace /authentic-theme/unauthenticated/js/bundle.min.js with new version, clear browser's cache, and give it a try.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Buttons not working in 1.881

A web-based interface for system administration of UNIX

Group

Searches

Help

#5106 Buttons not working in 1.881

Related

Discussion

Related