kriesi, i am having the same problem so i will post a private reply with a screencast of the error occurring. but in summary, the first time i open a text block, the visual editor works fine. the second time opening a text block (it could be the same one, or another), i get an error in the console:

NS_ERROR_UNEXPECTED: wp-tinymce.php:5

and that row 5 is:

}function i(){“undefined”!=typeof console&&console.log&&console.log(“Failed to load: “+e)}var o=r,a,s;s=o.uniqueId(),a=document.createElement(“script”),a.id=s,a.type=”text/javascript”,a.src=e,”onreadystatechange”in a?a.onreadystatechange=function(){/loaded|complete/.test(a.readyState)&&n()}:a.onload=n, [continues….]

i previously posted to the longer thread about this here: https://kriesi.at/support/topic/visual-editor-not-working-after-update-to-wp-3-9/

i’ve done all the regular things like clearing caches, fresh install of WP, no plugins, etc. there are many threads about similar issues on wordpress.org and luckily for some people, it’s an easy fix when they just disable a plugin. i’ve also checked the master list of conflicts here (http://wordpress.org/support/topic/wordpress-39-master-list?replies=6) but i don’t see any components of enfold that could be causing it.

I had a similar problem – and I edited the user in WordPress and checked the option to disable the WYSIWYG-editor (+ save).
Right after that uncheck the option (+ save).

Result: full editor is back.

Not working for you?
1) Check if there is a newer Enfold version and use that one. 2.7.1 supposedly fixes this problem.
2) Clear cache
2) CTRL-F5
3) Try a different browser to see if it is only browser related and post back here with info of what you see. Post screenshots.

What else did I try (these changes did not solve it immediately but maybe are part of the solution)?

1. Deleted my entire WordPress 3.9 files and re-copied them trough FTP.(EXCLUDE wp-config and wp-content!)
2. Deleted my entire original Enfold 2.7 files and re-copied them trough FTP.
3. I’m using the (unedited!) Enfold-child-theme; but try switching to the 2014 theme and check if that _is_ working.
4. Edited WP-Config and made sure there are no empty lines after the last statement.
5. Disabled all plugins Especially cache-plugins and minify options.
6. Checked all .htaccess files for cache-plugin references and deleted those lines.

• This reply was modified 11 years, 10 months ago by Pixelbits. Reason: updated with releaseinfo of Enfold 2.7.1 version

I’m having this issue too, when upgrading from Enfold 2.6.2 to 2.7. I loaded the entire site by ftp, then reloaded only the layerslider as you suggest above. It is not fixing it.
Any ideas?

Enfold version 2.7.
For iphone 5, when i switch from portrait to landscape mode, about half of the footer is covered with white stripe, i.e. that part of the screen does not seem to be refreshed properly with the color of the footer.

To see this effect, go to http://www.ipinform.ca/ on iphone 5 using portrait mode, scroll down so that the line “Feel Free to Drop Us a Line” is at the top of the screen, now turn to landscape orientation, you will see the above effect wherein the copyright line in the footer is covered with white stripe.

Hi!

Diese Struktur wäre in der Tat schwierig umzusetzen, da Portfolio Einträge und Posts einen Slug benötigen. Ihr könnt daher ohne Anpassung des Theme Codes http://meine-website.com/(jeweilige Versicherung)-vergleich/ nur mit Seiten (bzw. Subseiten) umsetzen. Wenn ihr dafür Posts oder Portfolio Einträge verwendet würde ich den Slug “versicherungsvergleich” verwenden und dann als Titel des Portfolio-Eintrags den Versicherungsnamen wählen. Der Slug wäre dann http://meine-website.com/versicherungsvergleich/(Name der Versicherung). Wenn sich (jeweilige Versicherung) auf eine Gattung von Versicherungen bezieht (Brandschutz, Haftpflicht, etc.), dann würde ich diese auf jeden Fall als Seiten anlegen und dann entweder wieder die einzelnen Versicherungen als Subseiten anlegen, oder zB ein Ajax Portfolio nützen (siehe zB: http://kriesi.at/themes/enfold/portfolio/portfolio-ajax/ ) um auf die einzelnen Versicherungen zu verlinken. Nachteil der letzten Lösung ist jedoch, dass die Permalink Struktur nicht konsistent ist.

heers!
Peter