Closed (fixed)
Project:
Wysiwyg
Version:
7.x-2.x-dev
Component:
Editor - TinyMCE
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Aug 2017 at 04:46 UTC
Updated:
25 Nov 2018 at 00:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
ccjjmartin commentedComment #3
ccjjmartin commentedComment #4
ccjjmartin commentedComment #5
ccjjmartin commentedComment #6
twodI'm trying to keep the internal Wysiwyg instance as the context wherever possible and only use
Drupal.wysiwyg.editor.instance[editorName]to build a prototype for it so let's get it from the main TinyMCE instance instead.Also noticed the TinyMCE 4 implementation wasn't keeping up (fullscreen is no longer a separate instance) so I included fixes for that.
Comment #7
ccjjmartin commentedCode and functional (ajax requests and maintaining content) both look good on TinyMCE 3. Going to look into TinyMCE4.
Comment #8
ccjjmartin commentedWhen testing TinyMCE 4.5.7 + Drupal Core 7.56 I found that when I insert a link it saves the data to the database and displays the link within TinyMCE but when I go to view a node I am seeing:
some text [url=/test]Test[/url]
Maybe the prepare content for the plugins isn't replacing this properly ...
Comment #9
twodDisable the BBCode plugin.
Comment #10
ccjjmartin commentedThat fixed it. Is this a known issue with that plugin?
Comment #11
twodIt's designed to do that. You need a BBCode parser running as a text format filter to have any use for it though. (I don't even know if there are any for D8 yet)
Comment #12
ccjjmartin commentedThis looks good to go then, great work!
Comment #13
dsnopekRTBC +1! This patch works great in my testing and we're now using it in Panopoly :-)
Comment #15
twodThanks for reporting, patching and testing!