-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Account Details - "View Templates" Button Does Not Filter #10391
Comments
@scottsignal , I'm pretty sure this is as intended, meaning the root admin seeing all templates by default. I am not saying this shouldn't change but that someone did this on purpose and we need to take care to not break other use cases. cc @bernardodemarco |
@DaanHoogland, I don't think that's the case here. When the administrator access an account's page and selects the When those fields are defined but It is important to note that the root admin will still continue seeing all templates by default when directly accessing the Templates page. This filtering will only be performed when the |
@DaanHoogland, what should we do about this one? Should we leave the way it is currently implemented or should we fix it? cc @Pearl1594 |
see my answer at #10392 (comment) as well. If we can add a filter and the default view for root admin is still to view all, we can add the filter during the redirect from account view. This makes total functional sense to me. |
Okay, great. Soon, I'll open a PR adding the filter when redirecting from the account view. |
problem
Clicking on
View Templates
from Account Details as Root Admin does not filter correctly by Domain/Account.Expecting to only see 2 templates:

versions
4.19.1.3 & 4.20.0.0
GUI
KVM
The steps to reproduce the bug
...
What to do about it?
It appears that
templatefilter
is a required field for ListTemplates. If I add&templatefilter=self
to my URL, the filtering then works correctly.The text was updated successfully, but these errors were encountered: