I have created a context setting for tiny.css_selectors to override the system setting, which is completely duplicated from the system setting with the exception of the values.
Key: tiny.css_selectors
Name: setting_tiny.css_selectors
Description: setting_tiny.css_selectors_desc
Field Type: Textfield
Namespace: tinymce
Area Lexicon Entry: advanced-theme
MODX Revolution 2.2.0-pl2 (advanced)
TinyMCE 4.3.2
Is this a bug? Or am I doing something wrong?
This does work if I add the setting to the user, but I want to be able to do this on the context. If the setting can be added on the context, I'm thinking I need to file this as a bug.
-
MODX Staff
- 10,725 Posts
Are you expecting this to override behavior when editing Resources in the mgr? If so, then this may be a bug with the tinymce integration not respecting what is called the "working context" of the Resource being edited.
Yes, I'm expecting the override behavior when editing Resources in the mgr. Is this a bug I should file with MODX or TinyMCE?
-
MODX Staff
- 10,725 Posts
I'd post it in TinyMCE and if it needs adjustments to the core, we can enter a related bug detailed for the Revolution project.
This is the response I received from TinyMCE:
Well, there is actually no TinyMCE integration to MODX made by TinyMCE. So if anything, it's MODX that implemented the integration.
Besides, css_selectors is not a parameter of TinyMCE. So even if we try to help, that doesn't really point us anywhere. If something in TinyMCE is not functioning, then you would need to dig deeper into MODX to find out the exact function called in TinyMCE API so we can look into that.
Okay. I am new to MODX and have only been visiting github when it comes up in searches on Google. I suppose I should sign up for an account there. I'm still learning my way around the MODX Forums, Add-Ons, bug tracking, etc. I will look into posting the issue there. Thanks!
