-
- 167 Posts
Is duplicate some "system settings" in "Context setting" is sufficient to override system settings?
For example I created
Name: setting_use_editor
Key: use_editor
Value: No
in "dev" context setting but when I create a new document, CKEditor still enabled.
(I use XRouting for context switching)
MODX lover
-
Développeur MODX / Webdesign / Solutions web
Yes. Context settings will override system settings. As of 2.3, group settings will override context settings. User settings will override group settings. For elements, element settings will override context settings; not sure about group and user settings in this case. Property Sets, then element tag properties override everything else.
The actual setting key is use_editor.
[ed. note: sottwell last edited this post 9 years, 9 months ago.]
-
- 24,544 Posts
As long as the key is use_editor, it doesn't matter what the name is. Mine shows: "Enable Rich Text Editor" for the name.
Be sure you flush permissions and sessions. It may be necessary to manually delete all files in the core/cache directory before your changes take effect.
If that doesn't work, try creating a blank which_editor setting.
(thank you for the correction, Bob. Post edited.)
-
- 24,544 Posts
I figured I owed you one after all the times you've helped by correcting my slips.
-
- 167 Posts
- Flushed perm.
- manually deleted all files in the core/cache
Current Context settings:
Still not working :-/ CKEditor always here for existing & new resources.
MODX lover
-
Développeur MODX / Webdesign / Solutions web
use_editor would only be respected from the mgr Context in this case, since that is the Context which is being used when working in the manager UI.
I almost always set up a system for handling a site's CSS using a context and resources in that context for the CSS. I use context settings so that the CSS-resources context uses the Ace editor, and the main mgr context uses TinyMCE or CKEditor. The keys are use_editor (yes or no) and which_editor (Ace or TinyMCE).