getOptions overrides

I have always been under the impressions that using getOptions() will use User Settings, Context settings, then System settings, whichever it finds first. In other words, Context settings will override System Settings, and User settings will override Context settings and System Settings.

Apparently this is not exactly true.

In one case specifically, involving the Ace plugin, context settings must be specifically checked for.

With the original Ace code

will not recognize Context settings. That needs to be changed to


Where do User settings come in here?

So does this mean that all component creators need to specifically check for User and Context settings instead of using $modx->getOption? Is this explained anywhere in the documentation?

https://github.com/modxcms/revolution/issues/11347

I checked, and User settings do override Context or System settings with either version of getOptions. Very odd that Context settings do not override System Settings as expected. [ed. note: sottwell last edited this post 12 years, 5 months ago.]

TinyMCE uses $tiny->context->getOption for some things, and $modx->getOption for others. How is one supposed to know when to use which?