To use skins you have to assign skin to the group. When that is done users of that group will automatically > use the selected skin as their default when logging into > WebFig or > Winbox> .
This would be amazing but doesn’t appear to be true. Is this on the roadmap to allow skins created to apply to both the web interface and winbox? I have industrial clients that are electricians using mikrotik as a cheaper more feature rich option to what they were using, however, I’d love to trim back the interface to just what they need while still allowing them to use winbox for discovery, MAC access, and improved GUI that has easy use copy rule functions.
it does work in v7, though I haven’t tested enough to actually allow anyone to actually access winbox with a skin as the function/security limiting function (though I do with webfig). It’s on my product roadmap to test for later this year.
You haven’t tested it, but I have on 7.8, it doesn’t work. The same account logging into web GUI worked great but logging into winbox everything is there.
I actually did just 20 minutes before writing that have a v7.7 skin apply to my login… You are correct that I have not tested v7.8, but it does work on v7.7. If it’s not working for you I’d say check webfig and see if the skin works there or not. You might be trying to apply a broken skin, I’ve seen them be very temperamental when editing / making the skins where they get corrupted sometimes.
FYI, I forgot that if you’re loading the skin via branding maker, there’s a bug where it writes the skin as a hidden file and can’t be seen/accessed, so from my testing you need to also load it as a custom file in branding maker, which allows it to work for webfib, but not winbox. Winbox requires the skin visible in the skins folder, which cannot be achieved entirely through branding maker at the moment.
i.e. branding maker & skins are a bit of a cluster right now. I’ve submitted support info but was told they couldn’t reproduce any problems and that it was all me, despite them clearly NOT reproducing the steps I provided them. If you can reproduce the issue, please submit a ticket as well and note this thread, hopefully they’ll fix it.
But if you get it all correct, it does work.
edited to add picture I forgot.
It is not enough to create a skin (with the supported version of RouterOS and WinBox),
it must also be set on the Users / Groups of the system, to be used.
Come on man, I linked the reference article on setting it up which includes that info and provided twice in short order that "The same account logging into web GUI worked great but logging into winbox everything is there.". This implies I applied the skin to the group/user as instructed and it works in the web GUI but not in winbox... I'll include a picture, people like pictures.
some days ago i tried Winbox Skin on a remote device and not worked, but reading this topic i tested on local device using 7.6 and worked OK, if i find why does not worked in my remote device i will post it
So I just deleted the skin, downgraded to 7.6, recreated a more basic skin, and applied it to an account. It worked for trimming out options in web, it still doesn’t for winbox.
@normis I also confirm this issue. I checked it on CHR and wAP R. Custom skin works only on WebFig, Winbox shows all tabs (downgrade from 7.8 to 7.7 - 7.6 nothing changes)
Tested on a fresh box again today, out of the box I upgraded to 7.8 OS and RB firmware, factory defaulted, loaded a config file and skin, setup a new group and associated the skin file, created a new user under that group. Then I logged in for the first time with that user on winbox and everything is there, login on web and only what I want is there.
If you can reproduce the issue, please submit a ticket as well and note this thread, hopefully they’ll fix it.
