sam_a

Thanks. Did that change recently?

.tribe-events-ical { display: none !important; }

wp_ob_end_flush_all() can cause this when output compression is on: wp_ob_end_flush_all() hangs the output buffering, during plugin update/install; zlib.output_compression “on” in server conflicts with autoupdate

The notice itself doesn’t necessarily signal a problem, but if it’s getting printed in AJAX responses it will break them. Use your browser’s dev tools to look for bad responses if you see things like image import failing.

Try adding to your wp-config (https://codex.www.ads-software.com/Editing_wp-config.php#Configure_Error_Logging):

ini_set('display_errors', false);

You can disable output compression, but it’s a good feature, not a server misconfiguration.

Hopefully WordPress will fix wp_ob_end_flush_all().

WordPress won’t support MySQL strict mode but 3.9 will “fix” this by disabling NO_ZERO_DATE, ONLY_FULL_GROUP_BY, STRICT_TRANS_TABLES, STRICT_ALL_TABLES, TRADITIONAL modes.

I see it’s in 0.3 now, thanks.

Thanks wycks.

I think I fixed it…

I deleted wp-content/advanced-cache.php, created by an earlier version of W3 Total Cache (the plugin was inactive though).

I just got this error in WP 3.6 somehow… then it went away. Weird.

I think images inserted into posts are handled differently; maybe try the image_send_to_editor filter in get_image_send_to_editor().

wp_get_attachment_image() is used for Featured Images and other images output in templates.

“Post objects are now instances of a WP_Post class” since https://codex.www.ads-software.com/Version_3.5 . They used to be just standard objects.

I think nearlyfreespeech.net is Unix-based (“designed for people who are comfortable with Unix-based web hosting”).

Try

• https://faq.nearlyfreespeech.net/section/nbspgettingstarted/installwordpress
• https://www.jamosmith.com/installing-wordpress-at-nearly-free-speech/

Thanks, Nathan.

I get these errors too (on activation and every pageview thereafter).

I think it’s the same problem described in [resolved] HTTPS update broke my site (not actually “resolved” yet)

I tried downgrading to plugin 2.0.4 but got (in WordPress 3.3.2)

Catchable fatal error: Object of class __PHP_Incomplete_Class could not be converted to string in […]/wordpress-https/wordpress-https.php on line 187

I’m seeing similar errors right after activating the plugin.

Mvied, have you tried using plugin_basename( __FILE__ ) instead of setting include_path?

WARNING: wp-content/plugins/wordpress-https/wordpress-https.php:37 - include(Jetpack.php) [function.include]: failed to open stream: No such file or directory
WARNING: wp-content/plugins/wordpress-https/wordpress-https.php:37 - include() [function.include]: Failed opening 'Jetpack.php' for inclusion (include_path='.:/usr/local/php-5.3.13/share/pear:/home/example.com/html/wp-content/plugins/wordpress-https:/home/example.com/html/wp-content/plugins/wordpress-https/lib')
[…]