Skip to content
This repository has been archived by the owner on Sep 9, 2021. It is now read-only.

new defaultNewAcl is only active after restart of adapter #54

Closed
GermanBluefox opened this issue May 18, 2021 · 7 comments · Fixed by #55
Closed

new defaultNewAcl is only active after restart of adapter #54

GermanBluefox opened this issue May 18, 2021 · 7 comments · Fixed by #55
Labels
bug Something isn't working

Comments

@GermanBluefox
Copy link
Contributor

If user changes in admin the defaultNewAcl in system settings, they are active only after the admin is restarted.
I guess it is valid for javascript too if createState is called.

@Feuer-sturm
Copy link

Feuer-sturm commented May 24, 2021

@GermanBluefox @Apollon77
Behavior which is described in ioBroker/ioBroker.admin#898 and results in this issue is with js-controller 3.3.11 (and Admin 5.1.0) still there.
In iobroker log nothing is shown after saving the changes.

grafik
grafik

@Apollon77
Copy link
Collaborator

Which exact behaviour you mean?

@Feuer-sturm
Copy link

@Apollon77 If default ACL settings are changed (first screenshot) and then new objects are created they have not the new "default ACL" settings. I had expected that the accessright "Jeder lesen" was not set because it is not part in the default ACL.

@ice987987
Copy link

@Apollon77
@GermanBluefox
@Feuer-sturm

This issue still occurs in Admin v5.1.5. Could you please check again this if necessary?

@Apollon77 Apollon77 reopened this May 30, 2021
@Apollon77
Copy link
Collaborator

Yes, js.controller 3.3.12 soon will fix that for good :-) (hopefully)

@Apollon77
Copy link
Collaborator

js-controller 3.3.12 on release (https://github.com/ioBroker/ioBroker.js-controller/actions/runs/916352088) ... should fix it

@Feuer-sturm
Copy link

@Apollon77 Yes it is fixed with js-controller 3.3.12 and Admin 5.1.9 :-)
Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants