Customize Sources - add an event / settings to change sources in production environment #11536
-
In my opinion moving all settings for custom sources into the project config was not a good thing. It was an awesome step in Craft 3 to let each user have their own setting and I have no idea why this was reverted. I already spend a few hours to kinda revert your change. {% if currentUser.admin and craft.app.config.general.allowAdminChanges %} condition in your Actually I would really love to revert that like it was in Craft 3. Our clients wish that too and it's my current task to do this before we use Craft 4 more. Just an explanation why that's kinda a dealbreaker: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
That was never the case. Non-admin users could be granted permission to change the global source settings, but it would affect all users, not just their own account. We are considering making it possible for users to customize it to their own needs, though – see #11355.
Not exactly what you’re asking for, but it’s possible to modify the source settings at runtime via the |
Beta Was this translation helpful? Give feedback.
That was never the case. Non-admin users could be granted permission to change the global source settings, but it would affect all users, not just their own account.
We are considering making it possible for users to customize it to their own needs, though – see #11355.
Not exactly what you’re asking for, but it’s possible to modify the source settings at runtime via the
craft\base\Element::EVENT_REGISTER_SOURCES
event.