Title: "Headers already sent" errors after update
Last modified: August 21, 2016

---

# "Headers already sent" errors after update

 *  [suej1](https://wordpress.org/support/users/suej1/)
 * (@suej1)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/headers-already-sent-errors-after-update/)
 * Hi there … I’ve just updated to version 3.1.4 of WP Jump Menu, and started getting
   a heap of ‘headers already sent’ errors. I tried deactivating, deleting and re-
   installing … at which point WordPress popped up the following message:
 * _The plugin generated 25 characters of unexpected output during activation. If
   you notice “headers already sent” messages, problems with syndication feeds or
   other issues, try deactivating or removing this plugin._
 * I’ve deactivated and removed the plugin again – and the problem has disappeared
   once more.
 * I’m on WordPress version 3.6.1.
 * Any advice or assistance will be very much appreciated! 🙂
 * Cheers
    Sue
 * [http://wordpress.org/plugins/wp-jump-menu/](http://wordpress.org/plugins/wp-jump-menu/)

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

 *  Plugin Author [James Krill](https://wordpress.org/support/users/jkrill/)
 * (@jkrill)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/headers-already-sent-errors-after-update/#post-4120284)
 * Hi Sue,
 * Thanks for the message. Sorry about that. I’m not getting that error on my side.
   Could you respond and let me know what plugins you have activated and what theme
   you are using?
 * Thanks!
 * PS – I just removed a line of code that might have been the problem – but it’s
   a shot int he dark without being able to see the error. Try updating to 3.1.5
   and see if that helps.
 * Thanks!
 *  Thread Starter [suej1](https://wordpress.org/support/users/suej1/)
 * (@suej1)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/headers-already-sent-errors-after-update/#post-4120297)
 * Brilliant – thank you! 🙂 Version 3.1.5 installed, with no problems – and WP 
   Jump Menu is working perfectly again.
 * Looks like it must have that line of code that was the problem after all – and
   your shot in the dark was perfectly on target. 🙂
 * Many thanks for such a fast response!
 * Cheers
    Sue

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

The topic ‘"Headers already sent" errors after update’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-jump-menu_f7f7f7.svg)
 * [WP Jump Menu](https://wordpress.org/plugins/wp-jump-menu/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-jump-menu/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-jump-menu/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-jump-menu/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-jump-menu/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-jump-menu/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [suej1](https://wordpress.org/support/users/suej1/)
 * Last activity: [12 years, 8 months ago](https://wordpress.org/support/topic/headers-already-sent-errors-after-update/#post-4120297)
 * Status: not resolved