Hi Jamie. Of course, I tried all. This is not the first time I'm meeting
this issue. I got 2 servers under debian wheezy. 1 has this problem, the
other does not have...
I clearly identified the problem. I was under the"old webmin them" wich
is coming by default. I just changed my theme for the "BWTheme -
Bootstrap Webmin Theme"... It is perfect.
It means it is only a problem of theme and not Webmin by itself...
Please look the attached piece.
I hate to bump such an old thread, but this "bug" still exists, and I figured it out:
Firstly, the MySQL module works and does not display any errors during most operations if the MySQL configuration file setting is invalid, and everything else is set correctly.
I'm no perl developer, so I can't even begin to implement checks to provide a warning to the user that the module isn't fully configured, but I think this is nevertheless necessary.
Second, the red herring: this isn't a bug, but rather a lack of a feature in such an old, outdated theme — the "old webmin theme" as well as the "gray framed theme" do not support the "Un-used Modules" category. Therefore, all modules will appear in their configured categories, whether such module works at all or not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Even if you click "Refresh Modules" ?
lol... this is the reason I open a new ticket !! TO SOLVE THIS...
2015-03-21 8:25 GMT+02:00 Gmail jycemea@gmail.com:
Related
Bugs:
#4578If you open the Apache module under Un-used Modules, does it report any errors about missing config files or programs?
Jamie,
I clearly identified the problem. I was under the"old webmin them" wich
is coming by default. I just changed my theme for the "BWTheme -
Bootstrap Webmin Theme"... It is perfect.
It means it is only a problem of theme and not Webmin by itself...
Please look the attached piece.
Jean-Yves
That's surprising, as all themes should display the same categories. Perhaps switching themes just refreshed the page?
I hate to bump such an old thread, but this "bug" still exists, and I figured it out:
Firstly, the MySQL module works and does not display any errors during most operations if the MySQL configuration file setting is invalid, and everything else is set correctly.
I'm no perl developer, so I can't even begin to implement checks to provide a warning to the user that the module isn't fully configured, but I think this is nevertheless necessary.
Second, the red herring: this isn't a bug, but rather a lack of a feature in such an old, outdated theme — the "old webmin theme" as well as the "gray framed theme" do not support the "Un-used Modules" category. Therefore, all modules will appear in their configured categories, whether such module works at all or not.
Ok, I see the cause of this now - it will be fixed in the next Webmin release.