how to hide the hidden unhidden in webfig

I don’t know where else to report this Bug(?) and if you find the subject confusing, I’m sorry it’s not getting better till the end.

For a webfig customer configuration I gave the user group a skin where almost everything is hidden. Generally it works fine but the users do see some configuration options that are not visible in admin view and therefore are not available in “Design Skin” to be hidden.

I edited the skin.json manually to hide these additonal options. However, that’s a bit painful since:

  • in skin.json you do not see the options you want to hide
  • in admin view you don’t see the options either
  • in skinned user view you actually do see these options but they are the last options you see which makes it difficult to find the propper location in skin.json where to add the “hiding” of these options. (I don’t know if the order matters.)

It seems to be a general problem that options which are not available for a specific thing (wireless card in my case) are hidden in the admin view and therfore are not visible in ‘design skin’ mode. Once the skin has been designed and applied the only hidden options are those listed in skin.json. Thus leaving the unavailabel options in admin view unhidden. Sorry, are you still with me?

RB411 with 2GHz and 5GHz wireless card

Example 1:
webfig admin view:
[] menu/wireless/interfaces/(select 2GHz interface)/… no section HT
[
] menu/wireless/interfaces/(select 5GHz interface)/… section HT exist … (‘Design Skin’ setting: hide)
webfig user view:
[] menu/wireless/interfaces/(select 2GHz interface)/… section HT exist
[
] menu/wireless/interfaces/(select 5GHz interface)/… no section HT … (hidden by ‘Design Skin’)
To fix it I copied the HT section from 5GHz to 2GHz section in skin.json.

            HT: {
                'HT Tx Chains': 0,
                'HT Rx Chains': 0,
                'HT AMSDU Limit': 0,
                'HT AMSDU Threshold': 0,
                'HT Guard Interval': 0,
                'HT AMPDU Priorities': 0
            },

Example 2:
webfig admin view:
[] menu/wireless/interfaces/(select 2GHz interface)/… no section NV2
[
] menu/wireless/interfaces/(select 5GHz interface)/… no section NV2
webfig user view:
[] menu/wireless/interfaces/(select 2GHz interface)/… section NV2 exist
[
] menu/wireless/interfaces/(select 5GHz interface)/… section NV2 exist
To fix it I added in 5GHz and 2GHz section this NV2 section in skin.json. It was a lucky guess and it doesn’t work if only one colon is missing.

            'NV2': {
                'TDMA Period Size': 0,
                'Cell Radius': 0,
                Security: 0,
                'Preshared Key': 0,
                tab: 0,
                'Queue Count': 0,
                QoS: 0
            },

Example 3:
Another thing in skin.json ist the comment which in admin view was to hide in for the 2GHz interface but not for the 5GHz interface. Setting the tick didn’t have any effect. Guessing the syntax in skin.json it turned out that the keyword ‘Comment’ does not work …

            'Comment': 0

… but was replaced by “undefined” in the 2GHz section where the hiding worked in “Design Skin”.

            undefined: 0

Finally it works for now but it’s everything else than comfortable.

options you are mentioning are available in wireless-> advanced mode. Will see if i can get the same behaviour. In the mean time, try to go into advanced mode for wireless and hide unwanted stuff there.

I did check the the Advanced Mode. NV2 isn’t available at all and HT options are available for 5GHz interface only.

Having an option avaiable at one interface and not at the other, gives me the idea that the 2GHz interface does not support “HT” hence RouterOs does not show this option. On the other hand webfig hides only the items listet in skin.json.

It’s been a while, unfortunately the problem hasn’t disappeared. Any news on your ongoing research? :wink:

In v5.22, these problems still persist. I have the same problem, and I can add items manually to the json file, and then they disappear when user logs in, so this must be a bug.

			HT: {
				'HT Guard Interval': 0,
				'HT AMPDU Priorities': 0
			},
			NV2: {
				'TDMA Period Size': 0,
				'Cell Radius': 0,
				'Security': 0,
				'Preshared Key': 0,
				'Queue Count': 0,
				'QoS': 0
			},