Suggestion: Admin CP option to remove language selection menu

[Michal H]

In the Admin CP, there is an option to remove the ability for users to select skins for the board. This is useful when you only offer one skin and, therefore, having a skin selection menu is pointless.

However, the option to remove the ability for users to select languages is suspiciously absent, especially since IP.Board only ships with one language pack. Basically, since it is possible to offer only one language choice, there should be an option to remove the language selection menu, since it looks silly when there really is no option.

I am fully aware that one can do this by editing the code, either by deleting it or commenting it out, but it is more elegant to have it as an option, and it makes it more forward-compatible. Plus, some users are not comfortable with making small code alterations.

P.S. I read this suggestion before, but my search failed to find it, so I apologize for the "repost".

[CnCNet]

Why is an option needed? Those fields should be hidden automatically when there's only one entry.

[AndyF]

It has been suggested before :) , but I do agree if there's only one language installed or available at least, the admin should be able to specify that there's no dropdown (the same way as you say you can deny members access to the skin chooser)

[CnCNet]

That doesn't answer my question.

[AndyF]

That doesn't answer my question.

It always does display, there's no conditional check to hide it. :)

If you enabled 'allow members to choose skins' and only had one skin, the skin chooser would still show...

[Jυra]

I thinking editing out a short bit from the skin is elegant.

[CnCNet]

It always does display, there's no conditional check to hide it. :)

If you enabled 'allow members to choose skins' and only had one skin, the skin chooser would still show...

My point is that there's no need to add an option. Code should be added to automatically hide the box without an admin having to tick a checkbox in ACP.

[CnCNet]

Does Invision provide feedback on feature requests?
If not, how does one know whether a request gets accepted?

[absentee]

Another option should be to allow certain groups access to the skin/language selection.

For example, if I want to switch to the default skin for testing or another skin for some edits before I make it live (I keep a second copy of my working skin) I now have to go enable the option to select skins, and then go make my edits.

if there were a permissions field right below that option so I could select admins, moderators, and maybe even offer alternative skins to subscription members, without letting everyone think they can change skins, that would be awesome!


it just kind of sucks having an all-or-nothing choice.

[CnCNet]

if there were a permissions field right below that option so I could select admins, moderators, and maybe even offer alternative skins to subscription members, without letting everyone think they can change skins, that would be awesome!

Don't skins already have an access control list?

[absentee]

Don't skins already have an access control list?

yes, but I was talking about permissions for the visibility of the skin selection menu. I have to disable it and reenable it whenever I want to work on another skin.

[AndyF]

Does Invision provide feedback on feature requests?

If not, how does one know whether a request gets accepted?

The developers do read all the suggestions yes. :)

[bfarber]

Does Invision provide feedback on feature requests?

If not, how does one know whether a request gets accepted?

Yes, frequently. We simply can't reply to every request however.

[CnCNet]

Yes, frequently. We simply can't reply to every request however.

So how does one know whether a request gets accepted?

[absentee]

So how does one know whether a request gets accepted?

Well the best way is when it pops up as a new feature/fix in a future release :P

But that's not necessarily the fastest.

[CnCNet]

Well the best way is when it pops up as a new feature/fix in a future release :P

But that's not necessarily the fastest.

That's the problem. When it doesn't, we won't know until the next release... Then it's probably too late to get anything done.

[bfarber]

We blog about features we have completed as we're working towards a new version.

I'm afraid this is just kind of how software goes. We get thousands (literally) of suggestions and simply don't have the resources to reply to every single one. Couple that with the fact that sometimes a feature may be implemented, but not exactly as originally requested, duplicate suggestions, and the simple fact we don't want to upset anyone with saying "sorry, we won't do that" and there becomes a huge burden to bear.

We reply to suggestions to garner additional feedback or further discussion of an idea when appropriate, but we just can't reply to every single suggestion made. It's a sad fact that's unlikely to change, and is not unique to us - most large software manufacturers work in a similar manner.

[CnCNet]

Lots of products have a tracker for feature requests. That way, you can keep track of the status of your requests.

[bfarber]

That would require one to categorize requests, and that's not realistic in my mind. What may be irrelevant or unimportant today may be tomorrow's next big thing.

[CnCNet]

What kind of categorization do you mean?

[Solar Jet Pro]

We really would like to see ability to remove lang selection menu!
Are there any news about it?
Otherwise we have to hardcode <_< removing this menu is necessary in our case.