FIX re-enable TinyMCE anchor plugin #245
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The default profile in Silverstripe CMS 4 does not have the anchor plugin enabled, and it also seems that the copy-pasted config is not actually 'inheriting' the default editor settings, and thus the CWP editor config did not have the anchor plugin enabled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default profile in Silverstripe CMS 4 does not have the anchor
plugin enabled. It also seems that the copy-pasted config is not
actually 'inheriting' the default editor settings (as is the nature
of a re-definition), and thus the CWP editor config did not have the
anchor plugin enabled.
Perhaps the CWP config could be made to 'inherit' from the default
CMS config, via getOptions and setOptions, but this should be a
separate issue.
Resolves #244