Title: JetPack Conflicts with Edit Flow –
Last modified: September 8, 2016

---

# JetPack Conflicts with Edit Flow –

 *  [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/)
 * I love this Edit Flow plugin and really hope that I don’t have to remove it.
 * With the current update of JetPack 4.3.1, Edit Flows causes a PHP conflict. When
   both plugins are activated, the following PHP error message appears in the JetPack
   Dashboard.
 * > Warning: Cannot modify header information – headers already sent by (_This 
   > part I left out on purpose_)…wp-admin/includes/template.php:1969) in (_I left
   > this part out on purpose_) …wp-includes/rest-api.php on line 361
 * When I deactivated the plugins and reactivated them one by one, No errors occurred,
   but the moment Edit Flow plugin was activated, the error returned.
 * This says that Edit Flow and Jetpack conflict with each other.
 * Do you have a fix for this?
 * Thanks
    -  This topic was modified 9 years, 8 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).

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

 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8161503)
 * Hrm. What version of WordPress and what version of Edit Flow are you using?
 * If possible, can you provide a few more lines of that warning? The parts that
   you left out might contain useful information.
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8162321)
 * Thanks for the reply.
 * WordPress 4.6.1
    Edit Flow 0.8.1
 * The parts that I left out refer to the root folder and subfolders of the server
   and due to hackers, I do not want to reveal how the folder structure is setup.
 * So it will look like this:
 * > Warning: Cannot modify header information – headers already sent by (output
   > started at server/root/wp-admin/includes/template.php:1969) in server/root/
   > wp-includes/rest-api.php on line 361
 * Without revealing certain folder names, that is what the error said.
    Does that
   help?
    -  This reply was modified 9 years, 8 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
    -  This reply was modified 9 years, 8 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8163889)
 * Still tough to diagnose without more information.
 * What theme are you currently using? Did you try reverting to the default WordPress
   TwentySixteen theme and checking if the issue persists?
 * > the following PHP error message appears in the JetPack Dashboard.
 * Is the JetPack Dashboard the only screen in WordPress where the warning is shown?
    -  This reply was modified 9 years, 8 months ago by [cojennin](https://wordpress.org/support/users/comradefuzz/).
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8164958)
 * _Default WordPress Themes_ – Yes I did test a default theme and the problem remains.
 * _Warning Display _ – the JetPack dashboard is the only place the warning is displayed.
 * So far this error has not effected any other function or part of WordPress, front
   or backend.
 * You can see a screen shot here: [PHP Warning in JetPack Dashboard](http://i1241.photobucket.com/albums/gg518/BattleWarrior/edit-flow-jetpack-conflict.jpg)
    -  This reply was modified 9 years, 8 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
      Reason: correction
 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8165156)
 * Ah, was looking at the wrong version. This is [fixed in the next version](https://github.com/Automattic/Edit-Flow/pull/356)
   of Edit Flow. Looking to get a release out soon.
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8165439)
 * Looking forward to this update. 🙂
 * Thanks.
    -  This reply was modified 9 years, 8 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
      Reason: added content
 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8192246)
 * Next version of Edit Flow is out, let me know if there’s an issue resolving this
   bug!
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8192324)
 * [http://i1241.photobucket.com/albums/gg518/BattleWarrior/dancing-leprechaun.gif](http://i1241.photobucket.com/albums/gg518/BattleWarrior/dancing-leprechaun.gif)
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8192325)
 * So what fixed it? Deactivated the debug in PHP? (curious)
 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8193692)
 * > So what fixed it? Deactivated the debug in PHP?
 * Not sure what hosting platform you use, but you should have control over what
   PHP debug output prints to the screen. [There are some settings](http://php.net/manual/en/errorfunc.configuration.php)
   in your PHP configuration you can tweak (though I always forget which one’s actually
   turn on and off debug output).
 * It’s an odd issue. Edit Flow 0.8.1 was using a deprecated WordPress function.
   It seems like the new(ish?) REST API functionality in WordPress [adds an action that sets a response header](https://core.trac.wordpress.org/browser/tags/4.6.1/src/wp-includes/rest-api.php#L359)
   when a deprecated function is being used (by a plugin, theme, inside WordPress
   core, etc). But the deprecated function was being used after the response had
   already been set. Response headers can’t be sent after the response has already
   been sent (should double check that’s correct…), which is why you saw that debug
   output.
 * The fix was to stop using that deprecated function.
 * Let me know if you’d like more detail! Would be happy to go over it more in depth(
   would help me understand it more too!)
    -  This reply was modified 9 years, 7 months ago by [cojennin](https://wordpress.org/support/users/comradefuzz/).
      Reason: flagging myself
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8193737)
 * Platform is WordPress newest version and it occurred with the newest version.
 * I did find something odd in the file structure of a few WordPress sites, especially
   the install that showed the conflict with Edit Flow. I found the “theme-compat”
   folder under wp-includes. Apparently this folder and PHP files are
 * > The theme-compat directory is comprised of a set of deprecated (since WordPress
   > 3.0) files that WordPress used to use as fallback template-part files, in case
   > the active Theme failed to include them.
   > In other words, if a Theme used the get_header() template tag, but failed to
   > include a header.php template-part file, WordPress would fall back to /wp-includes/
   > theme-compat/header.php.
   > The template-part files in theme_compat are deprecated, unmaintained, incredibly
   > old (by core/current-Theme standards), and should not be relied upon by any
   > current Theme
   >  – [http://wordpress.stackexchange.com/questions/54503/what-is-theme-compat](http://wordpress.stackexchange.com/questions/54503/what-is-theme-compat)
 * Does that have anything to do with it?
    -  This reply was modified 9 years, 7 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
      Reason: Added content
    -  This reply was modified 9 years, 7 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8193870)
 * Don’t think so. When I mentioned “headers” I was referring to [HTTP headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers).
   Thanks for that post though! Didn’t realize that’s how WordPress dealt with theme
   headers. Good to know!
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8194075)
 * Yes, I just checked a new download of WordPress and that folder is there with
   the PHP files. They have apparently been doing this since version 3x. personally,
   I think it is time not to include them because these PHP files can open the door
   to hacking since they are old ones.
 * You suggested to work more along the lines of the initial issue, what did you
   have in mind?
    -  This reply was modified 9 years, 7 months ago by [mwarbinek](https://wordpress.org/support/users/mwarbinek/).
      Reason: Added content
 *  [cojennin](https://wordpress.org/support/users/comradefuzz/)
 * (@comradefuzz)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8194173)
 * > You suggested to work more along the lines of the initial issue, what did you
   > have in mind?
 * Sorry, what do you mean? Are you still encountering the issue after updating 
   Edit Flow?
 *  Thread Starter [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * (@mwarbinek)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8194252)
 * No, the leprechaun is still dancing.
 * I refer to your statement of getting into more detail.

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

The topic ‘JetPack Conflicts with Edit Flow –’ is closed to new replies.

 * ![](https://ps.w.org/edit-flow/assets/icon-256x256.png?rev=3433533)
 * [Edit Flow](https://wordpress.org/plugins/edit-flow/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/edit-flow/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/edit-flow/)
 * [Active Topics](https://wordpress.org/support/plugin/edit-flow/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/edit-flow/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/edit-flow/reviews/)

## Tags

 * [Cannot modify header information](https://wordpress.org/support/topic-tag/cannot-modify-header-information/)
 * [headers already sent](https://wordpress.org/support/topic-tag/headers-already-sent/)

 * 15 replies
 * 2 participants
 * Last reply from: [mwarbinek](https://wordpress.org/support/users/mwarbinek/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/jetpack-conflicts-with-edit-flow/#post-8194252)
 * Status: not resolved