-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Prevent unauthorised modules from being moved #48
Comments
Wether moving is allowed depends on the pages sections of the destination page. All I did was adding a pages section with all of the module templates. In other words: it doesn't matter what you do in the parent page. |
Ok, so every module can be moved in every modules folder... |
Yeah, unfortunately it's not so easy. The actual parent of the modules is the modules container while your settings are one level up. What happens if you have two modules sections in the parent page with different For now I can't seem to find an easy solution. |
Are two or more modules sections on one page possible? I did a test and it doesn't seem to work... btw: But yes: Obviously it's not trivial, as it also took longer for pages to implement this... |
It works if you set a different
Absolutely. I normally define what kind of templates are allowed anyway to not have any bad surprises. |
Thanks for the added feature which enables moving modules!
In some pages of my project there are only certain modules allowed which is realised by e.g. "create: module.text".
Nevertheless, you can also move other modules into it.
Can you reproduce this behaviour?
The text was updated successfully, but these errors were encountered: