Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force login top level system config tab is overkill #73

Closed
maderlock opened this issue Jul 10, 2017 · 3 comments
Closed

Force login top level system config tab is overkill #73

maderlock opened this issue Jul 10, 2017 · 3 comments
Milestone

Comments

@maderlock
Copy link

It's great that we now have the ability to enable/disable by scope, but system admin is getting unusable with every developer putting in another top level tab.

Any chance that the very small number of config options could be put in as a group under the Customer system config tab?

@der-workfloh
Copy link
Contributor

Hi @maderlock ,

I see your point. Interested in providing a PR for this? In other ways, I will provide a change as soon as possible.

@der-workfloh der-workfloh added this to the 2.1 milestone Jul 10, 2017
@maderlock
Copy link
Author

I should have made one before when I implemented scoping in a fork. I'll take a look at this when I have a moment - let's see who gets to it first :)

der-workfloh pushed a commit that referenced this issue Jul 11, 2017
der-workfloh pushed a commit that referenced this issue Jul 11, 2017
der-workfloh pushed a commit that referenced this issue Jul 11, 2017
der-workfloh pushed a commit that referenced this issue Jul 11, 2017
#73 Move backend configuration to customer > customer configuration s…
@der-workfloh
Copy link
Contributor

Fixed this issue with RC3 of v2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants