-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Angle brackets get transformed into htmlentities #127
Comments
Found a solution, but it wasn't: My workflow to see the issue is as follow:
Now my solution is not ideal because I have to edit a core plugin file in order to fix this little issue, I could dequeue the ones added via the plugin and add my own but I would like to know if you plan to solve this issue with a next update before to chose how to implement my solution. |
I'm certain that I've seen this happen before, but I'm unable to reproduce. I'm on version I have no plugin active except for this one and Classic Editor (version 1.5). I am following these steps:
I do not see any escaping of the angle bracket characters. Could you look at my steps above and let me know if there is something I'm missing? I'm sure I've seen this before, and would like to be able to reproduce it so we can add it to our queue. |
Yes on a fresh installation the behaviour is as you describe, there is no angle brackets that get translated into Anyway I confirm what I wrote, if I edit the I tried to dequeue this file and load one of my own but since is loaded as plugin I am unable to replace it properly. |
Ok, so it sounds like this issue is not reproducible anymore? Can we close this and focus on #128? Or am I misunderstanding?
Maybe try using the https://github.com/Automattic/syntaxhighlighter/blob/master/syntaxhighlighter.php#L64 |
I am facing a wired issue because the angle brackets get transformed into htmlentities only if I switch between visual and text editor while using the Classic Editor and only on PHP open and close tags.
If I save the post the code gets back to normal, but I would like to understand why is this happening. I've tried the solution proposed in #108 and I do not think that is related to #98 because I am not using Gutenberg.
I found that maybe the problem is in some replace in
syntaxhighlighter_mce-4.js
but I still have to find my way out.If you have any suggestion I am all hearing.
I am using the latest version of the plugin (3.5.2) and I am on the latest WordPress (5.3.2).
Thank you for the future help.
-- Updates --
Deactivated all plugins but nothing has changed.
Moved "new line issue" to #128
The text was updated successfully, but these errors were encountered: