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
-
Thanks for the reply.
WordPress 4.6.1
Edit Flow 0.8.1The 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?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?
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
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 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 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!)
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-compatDoes that have anything to do with it?
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?
The topic ‘JetPack Conflicts with Edit Flow –’ is closed to new replies.
