Per-context settings? [$250]

[Mark-H]

Possibly by assigning groups to one or more contexts.

---

Did you help close this issue? Go claim the $250 bounty on Bountysource.

[Mark-H]

This will need some use-cases to make sure whatever implementation is going to be used can cater for as many as possible.. thoughts?

[salscode]

This would be the icing on the cake for this extra and at first glance I thought it had already supported context-specific settings. Ideally, I think it would be nice to allow for site-wide and context specific settings and then allow group specification on those independently.

[gadamiak]

Me too, I thought it already supported context settings!

[Mark-H]

Lol, what is it that made you think that? I don't think it even mentions
contexts anywhere :p
Op 10 jan. 2013 13:28 schreef "gadamiak" [email protected] het
volgende:

Me too, I thought it already supported context settings!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-12092305.

[gadamiak]

It doesn't. I guess, I was driven by the standard MODX settings
inheritance/override.

Anyway, that would be very useful.

[chunkyRice]

I could think of 2 possible scenario's in which this would be very useful: multi-language sites and installations serving multiple domains. In the case of a multi-language site, synchronizing settings between all contexts would be very welcome. When using it for multiple domains however, that would probably be exactly what you do not want.

[gadamiak]

I could think of 2 possible scenario's in which this would be very
useful: multi-language sites and installations serving multiple domains.
In the case of a multi-language site, synchronizing settings between all
contexts would be very welcome. When using it for multiple domains
however, that would probably be exactly what you do not want.

I agree with that. In my case it's a multi-domain case. I need context
owners to be able to set their own settings, which differ between contexts.

[Mark-H]

I would like to see if we can make this happen this year. :D There's been some light discussion about it in the forum thread (http://forums.modx.com/thread/81490/clientconfig-custom-configuration-cmp-for-clients?page=6#dis-post-489525) but I'm still having issues scoping out this feature and especially in terms of how to represent it to the users (clients/admins).

Backwards compatibility could also be an issue, but that could be solved by labeling it 2.0.

[jpdevries]

+1

[matdave]

+1

[degoya]

+1

[Mark-H]

I started working on this in #123, a lot more detail is in that pull request.

[sebastian-marinescu]

I'd also love to see a solution to this. Just stumbled upon this while planning a multi-domain-setup.

Right now, if I see correctly, I cannot even use context-specific settings to differ between contexts, because CC will override everything – am I seeing this correctly?

[Mark-H]

Correct.

[Mark-H]

This has been implemented, clientconfig 2.0-rc1 will be available from the modmore provider shortly in the pre-releases channel.

I added #134 to discuss the need for more explicit access to permissions.

[Mark-H]

2.0.0-rc1 is now available from the Pre-releases channel on modmore. Will publish an announcement and update the docs later this week.