Illegal strong offset 'file' (output buffers?)

I think I’m having the same issue (or similar) since upgrade to WordPress 4.4

I’ve noticed that a google search for Illegal string offset ‘file’ in functions.php line 3373 returns a lot of pages displaying the error — all appear to be recent happenings.

I’ve figured out that in my situation, the error only occurs on pages with an image, and deleting the image removes the error… but that’s not a fix obviously, just curious if your situation shows the same pattern.

I have several multisite networks, and this error is only occurring on one of them, so I’ve been trying to do the ole compare and contrast to identify the problem, no such luck yet. For me, it is only occurring on child sites.

I don’t understand what the error code itself means and haven’t found anything or anyone to generally explain it, which may be helpful in trying to figure out what is going on.

Can’t believe I have a typo in the title of the post “string error” obviously – thought you could edit those things, but see no option.

Xblade, thanks, I did remove the photo, but no change.

I’m also having the same error since last WP update, any luck till yet to fix this insane error?

@mcgrathlaw, when you removed the picture did you do so in the visual or text mode of the wordpress editor? I’m just wondering as I removed the pictures using the text mode, to make sure I had captured all the associated code. But we could be experiencing different causes of the error.

What ever is causing the errors my site is generating, it does not seem to be interfering with any other functioning. I found this code that removes the error display (errors are still occurring but at least not displaying for everyone to see):

ini_set('log_errors','On');
ini_set('display_errors','Off');
ini_set('error_reporting', E_ALL );
define('WP_DEBUG', false);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Put it in your wp-config.php file, replacing the line that originally reads define('WP_DEBUG', false);. Then at least your site looks ok as you continue to try to figure what the problem is.