Title: Version 2.0.11 breaks wp_editor() function
Last modified: August 21, 2016

---

# Version 2.0.11 breaks wp_editor() function

 *  [William Hagan](https://wordpress.org/support/users/william960design/)
 * (@william960design)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/)
 * Updating to Version 2.0.11 breaks the wp_editor() functionality.
    Specifically
   the Tabs Visual and Text. The Text tab is now selected by default and the Visual
   tab is no longer clickable. Also the javascript row of clickable icons are missing
   after updating.
 * Verified by disabling only your plugin and wp_editor() visual and text tabs became
   clickable and icons return.
 * I pretty much use the wp_editor() function for all front-end work for my sites.
   And have used your plugin with quite a few as well.
 * I’m going to grab a beer and debug your hot mess with regards to the front-end
   functionality for my sites.
 * [http://wordpress.org/plugins/nextgen-gallery/](http://wordpress.org/plugins/nextgen-gallery/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [mrcfisher](https://wordpress.org/support/users/mrcfisher/)
 * (@mrcfisher)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/#post-4061675)
 * Did you ever sort this out, I’m having the same problem.
 *  Thread Starter [William Hagan](https://wordpress.org/support/users/william960design/)
 * (@william960design)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/#post-4061676)
 * No I did not. I started searching for the annoying bit of the NextGen gallery
   and decided it would be faster to write my own gallery plugin. Plus I could add
   the features that I wanted: Each user gets their own gallery content area and
   cannot mess up anyone else’s. Admin can CRUD all images or narrow it down to 
   individual editors.
 * So not resolved, but avoided.
 *  [mrcfisher](https://wordpress.org/support/users/mrcfisher/)
 * (@mrcfisher)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/#post-4061677)
 * Thanks for the quick response, That was my next thought as well. Time to role
   my own, unless your is open sourced 😉
 *  Thread Starter [William Hagan](https://wordpress.org/support/users/william960design/)
 * (@william960design)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/#post-4061678)
 * I will make it open sourced, right now it is a quick hack for a client. I’ll 
   clean it up and release it, but not anytime soon. Working on three other projects
   right now. One to complete by end of 2013, next to complete by end of the week.
   Last one just prototyped.
 *  [mrcfisher](https://wordpress.org/support/users/mrcfisher/)
 * (@mrcfisher)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/#post-4061679)
 * I had to ask.. Thx again.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Version 2.0.11 breaks wp_editor() function’ is closed to new replies.

 * ![](https://ps.w.org/nextgen-gallery/assets/icon-256x256.png?rev=2083961)
 * [Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery](https://wordpress.org/plugins/nextgen-gallery/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/nextgen-gallery/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/nextgen-gallery/)
 * [Active Topics](https://wordpress.org/support/plugin/nextgen-gallery/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/nextgen-gallery/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/nextgen-gallery/reviews/)

## Tags

 * [wp_editor](https://wordpress.org/support/topic-tag/wp_editor/)

 * 5 replies
 * 2 participants
 * Last reply from: [mrcfisher](https://wordpress.org/support/users/mrcfisher/)
 * Last activity: [12 years, 6 months ago](https://wordpress.org/support/topic/version-2011-breaks-wp_editor-function/#post-4061679)
 * Status: not resolved