Complete how to add script tag as a valid element in TinyMCE in Plone 5. #637
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
| @@ -37,8 +37,13 @@ If you need to put a `<script>` tag on your content text in TinyMCE you can disa | |||
|
|
|||
| tal:define="dummy python:checkPermission('Modify portal content', context) and request.RESPONSE.setHeader('X-XSS-Protection', '0');" | |||
|
|
|||
| **Step 3:** (Plone 5 only) Add script tag to the list of `extended_valid_elements` of TinyMCE. Go to the Control Panel, TinyMCE settings, Advanced tab. Add to the Other settings field:: | |||
|
|
|||
There was a problem hiding this comment.
I guess we can remove '(Plone 5 only)' ? Because it will go only into the docs from 5.0 on, meaning currenltu it will go into the branches 5.0 and 5.1 of the docs.
|
@svx done! |
|
@sneridagh thank you ! |
|
Thanks! |
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.
Fixes: #
Improves: The HTML filtering documentation for Plone 5.
Changes proposed in this pull request: