roadlittledawn
Forum Replies Created
-
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Plugin still broken in WP 4.3Oi, that’s no good. I never lost changes switching between Text and Visual mode.
It’s been working fine for me after clearing cache and reinstalling the plugin. Did you try that?
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Plugin still broken in WP 4.3Damn browser cache! That did the trick (of course). I cleared cache and reinstalled the plugin. Tested in Chrome and Safari. Back to normal. Thanks for the response!
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Plugin still broken in WP 4.3FWIW, still broken in WordPress version 4.3.1 released today.
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Plugin still broken in WP 4.3I don’t quite have the technical depth to accurately assess the cause and solution here, BUT I dug up some info that seems relevant.
WordPress 4.3 tweaked how content is prepared in the Visual and Text editor modes. Both are now prepared/escaped the same (runing the textarea content through the JavaScript
wpautop()
before initializing TinyMCE).
WP 4.3 release notes (annotated)Maybe that’s the cause of the error?
Looking at before (WP 4.2.3) and after (4.3) versions of wp-admin/js/editor.min.js, it changed quite a bit, moving the
switchEditors
function to the end. Like I said, don’t have the technical depth to know if/how that affects HTML Editor Syntax Highlighter plugin, maybe a good place to start?Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Plugin still broken in WP 4.3Yep, I’m on v1.6.8.
Browser is Chrome v 45.0.2454.85 (64-bit).
Steps:
1. Access /wp-admin.
2. Go to edit post.
3. On edit post page, select Text tab.Text area disappears and boxes below crunch up near top of where toolbar normally is.
I disabled TinyMCE Advanced plugin, and it still occurs.
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] A possible issue with upcoming WP 4.3I see an error in Chrome web dev console that reads:
Uncaught TypeError: switchEditors.switchto is not a function
I think it’s originating in HTML Editor Syntax Highlighter plugin file hesh.min.js.
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] A possible issue with upcoming WP 4.3Thanks for the update and the fix. Buuut it’s still broken for me. Can’t think of any other plugins I’m using that would be conflicting with this.
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] A possible issue with upcoming WP 4.3Yep, it’s broken in 4.3 for me, too. Also using TinyMCE Advanced plugin.
Forum: Plugins
In reply to: [Secure Custom Fields] ACF4.0 IE9 Compatibility View = ProblemExcellent. Thanks much, ionainteractive. It’s fixed for me.
Forum: Plugins
In reply to: [Secure Custom Fields] ACF4.0 IE9 Compatibility View = ProblemI checked all the above, tried striking that line with return in it to no avail either. Some of my users use IE8, and it’s still generating an error at that line, so no metaboxes will load based on the rule I provided (when a certain category is checked off). The error message reads: Expected identifier, string or number.
Forum: Plugins
In reply to: [Analyticator] [Plugin: Google Analyticator] Not working, error messageAgh, figured it out. Saw previous posts and remembered I had to do it with another blog I admin. For the record:
1) Make sure you’re logged into Google Account that has the analytics account.
2) Go to the plugins page, click reset on Google Analyticator plugin.
3) Go to Google Analyticator plugin settings page. At very top click where it says click here.
4) A popup box will appear and you have to grant your site access to the Google Analytics account. It will generate a key and you have to copy that and paste it into the box in the settings page.
Forum: Fixing WordPress
In reply to: Category checkboxes not working correctly in Edit Post screen in IE8Follow up: Resolved the issue. I have Advanced Custom Fields plugin installed. I disabled this plugin and had the same issue; however, I saw the release notes for the latest version. They reported this bug in the plugin, which was causing this. I updated to the latest version, and now all’s well again.