I just ran into the same issue. Any update on this?
I ran into the same problem as you guys.
It took a lot of digging, but I eventually found this:
http://www.hongkiat.com/blog/wordpress-error-warning-cannot-modify-header-information/
It appears that one of the plugins adds an additional space at the bottom of the wp-config file that causes the stripslash error.
Following those instructions should resolve it.
That didn’t resolve my issue. There were no leading spaces in my wp-config.php file and the close tag on that file was removed 5 years ago.
Running through the list of files associated with this error also didn’t result in finding any leading/trailing spaces.
There were extra spaces in the plugin PHP file, but didn’t resolve the issue either.
Maybe the string the plugin passes is concatenated/malformed and that’s causing Genesis or the core to choke on it?
Plugin Author
Jean
(@jeangalea)
I don’t really know what’s wrong here guys, and I’m extremely busy right now so it won’t be easy to dig deeper. Having said that, if there’s anyone else who can supply a fix, this code is on GitHub so once a patch is supplied I’ll release an update here.
https://github.com/jgalea/genesis-coauthors-plus
I had a look through the code and couldn’t see anything that would obviously be triggering off the stripslash errors.
It appears that the error is being caused by the function that Genesis uses to remove the slashes from numerical HTML entities when they’re being rendered – namely wp_kses_decode_entities.
When I removed the Genesis Co-Authors Plugin, the stripslash errors remained. However removing the Co-Authors plugin itself removes the stripslash error.
That makes me thing the issue is in the Co-Authors Plugin itself rather than the Genesis plugin.
My knowledge of php isn’t great, but I guess you’d need to include a function that unhooks wp_kses_decode_entities when dealing with Co-Authors in Genesis in order to prevent the stripslash error.
If that’s in the right direction, let me know and I’ll keep digging.
Looks like the same problem occurs with Co-Authors Plus (http://wordpress.org/plugins/co-authors-plus/) whether or not you have the Genesis author-box support plugin enabled.
Plugin Author
Jean
(@jeangalea)
Seems like the issue is not directly related to this plugin then.