Forum Replies Created
-
Posts
-
markusperl’s solution worked for me. replaced the one line in avia-builder.js as described.
a client has an older site that i don’t want to be updating everything so it was great to do this temporary fix.
Hi Elliott,
I’m not sure that this would be a new feature request, because this “feature”/behavior used to work fine. As far as I can tell, it seems to have been broken by WordPress 4.1.
I just tested a backup of the same site and the problem is recent.
- WordPress 4.0.1 and Enfold 3.0.4 — When opening a Text Block in avia layout builder, the edit window defaults to the Visual tab.
- WordPress 4.1 and Enfold 3.0.4 — When opening a Text Block in avia layout builder, the edit window defaults to the Text tab.
Thanks
I’m in agreement with the original poster that this issue seems to have only started recently (not sure yet whether it coincided with a WP or theme update) and I actually consider it to be a MAJOR problem.
I have streamlined my client’s site for ease-of-use by their staff, some of whom are not very tech savvy, and this throws an unexpected roadblock in their way.
As I understand from a thread here (https://wordpress.org/support/topic/how-to-make-tinymce-advanced-default-editor-instead-of-html), when it comes to the built-in visual editor, WP sets a cookie with the preferred view and then saves it to the DB.
Can someone confirm whether Enfold’s advanced editor does something similar?
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’m getting similar problems as others have mentioned above. i’ve cleared all history, cookies, etc. in my browsers, and i’ve disabled all the wp plugins. i’m running wp 3.9 and latest enfold.
FIREFOX:
after entering a page to edit, the first time i open any text block, the visual editor works fine. then after i close the text block or save it and open any text block (same or another one on the page), the visual editor doesn’t work (white text on white bg, html formatting and no formatting menu). if i refresh the page to edit, the visual editor will work again, but again, only for the first time i open a text block.IE/CHROME:
a different problem when editing a page. when i click a text block to edit, visual editor shows up fine. then i close the text block, and click to edit another text block on the same page, and it opens up the first text block i opened (the first text block at the top of this page). no matter which element i click to edit on the page, it always pops up the first text block to edit (visual editor actually working though).
