Latest update breaks "Insert Image"

Hey again! It turns out that the latest update also breaks the full-height editor/distraction-free functionality setting in the WordPress screen options. The editor now appears in a dialog with its own scrollbar that can’t be resized.

Same thing happening here.

Hi there, just to reinforce, I’ve got the same issue on the two sites I use this plugin with. I really want to keep this in place (one of my sites is actually about coding, so…help!).

I’ll have to disable it to be able to continue writing posts, but would really appreciate if this could be fixed (if I can’t find a backup of an older version on my system anyway).

Thanks so much!

Just to help you guys, I found 1.6.9 on my machine, so you can revert back until the developers fix this:

https://resource-centre.net/files/html-editor-syntax-highlighter.zip

Hope this helps!

Sweet, thanks Martin!! My own temporary solution was to switch to the “WP Editor” plugin, which I quickly found out is really amazing, because it not only replaces the text editor, but also the theme and plugin editors. It’s also much more configurable. It being more complex might mean it’s also heavier on load times, but I don’t know. Perhaps give it a look.

Hi guys,

I’ve fixed the bugs here in a branch on the github repo(I think I actually created the bugs… sorry).

We will have to wait for Peter/nixdns(who owns the plugin)to update the plugin in the svn repo for the changes to be pushed globally.

BUT

In the meantime, if you want to download the fixed version 1.7.1 you can do that here

Sorry for the troubles,
-James

Wow, thanks so much James! Much appreciated!

I’m closing my dev branch now that its been merged with the master

you can download the fixed version 1.7.1 here now

Hi, James, your fixed version breaks at:
Parse error: syntax error, unexpected ‘[‘ in ../wp-content/plugins/html-editor-syntax-highlighter/html-editor-syntax-highlighter.php on line 41

Have little/no time to look into this, so switching back to 1.6.9. Great plugin, BTW. Many many thanks for your work. Now my team members know how to write HTML with no opened tags left behind (and with no punishment for that) ^_^

this error has now been fixed in v1.7.2

Thanks for letting us know