-
Notifications
You must be signed in to change notification settings - Fork 72
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
Milestone
Comments
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. |
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
der-workfloh
pushed a commit
that referenced
this issue
Jul 11, 2017
#73 Move backend configuration to customer > customer configuration s…
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
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?
The text was updated successfully, but these errors were encountered: