hussong

Thanks for the quick reply and the fix!

I’ve gone ahead and overwritten a lot of styles in my child theme anyway, so I’ll live with the customizer glitch ??

Possibly related, here’s my current experience (WP 4.4, ImageMagick Engine 1.5.2):

• without this patch: transparent PNG backgrounds go black
• with above patch, using command-line: transparent PNG backgrounds go white
• with above patch, using PHP module: transparent PNG backgrounds stay transparent.

I’ve settled for using the PHP module and applying the patch linked above.

Hope this helps!

Replying to myself here, since I found the old (and still valid) solution again to make ImageMagick Engine 1.5.2 play nice with WP 4.4:

In imagemagick-engine.php, line 761, change

if (!gd_edit_image_support($post->post_mime_type))

to

if (!wp_image_editor_supports(array(‘mime_type’ => $post->post_mime_type)))

and it’ll work.

Have been wondering about that as well, thanks for the explanation!
Love your plugin btw ??

Thanks for the overview and comparison, extremely helpful!

Komme etwas sp?t zur Party, habe aber jetzt das gleiche Problem mit Yoast SEO 3.0.7:

PHP Notice: wpseo_pre_analysis_post_content Filter/Aktion ist seit Version WPSEO 3.0 veraltet! Benutze stattdessen javascript. in /var/www/foo/wp-includes/functions.php on line 3406
PHP Notice: wpseo_body_length_score Filter/Aktion ist seit Version WPSEO 3.0 veraltet! Benutze stattdessen javascript. in /var/www/foo/wp-includes/functions.php on line 3406
PHP Notice: wpseo_linkdex_results Filter/Aktion ist seit Version WPSEO 3.0 veraltet! Benutze stattdessen javascript. in /var/www/foo/wp-includes/functions.php on line 3406

Konntet ihr über den Yoast-Support schon etwas in Erfahrung bringen?

@buzztone: Thanks for the pointer, very helpful!

Thanks for clarification!

Sure, it’s just a warning. However, I can’t permanently hide it, and I have no shortage of (mostly useless) plugin warnings in wp-admin. Ignoring simply doesn’t scale beyond 3-5 warnings.

I’d suggest to:
– let at least subdomains pass the configuration test
– add an option to disable configuration validation
– make it easy to permanently disable the warning

I would bet that having parts of the site on different subdomains (e.g. https://support.example.com) and the email address on the main domain (e.g. [email protected]) is a very common setup. I mean, who sets up [email protected]?

Using this plugin on a huge multisite install, with staging server set up on a different subdomain (think staging.example.com).

Configuration validation not very helpful in this case (of course it’s a different subdomain). Is there any way to turn it off via a filter or something?

Would be great to have a workaround here. Before I go ahead and update dozens of contact forms (not even sure how to fix this with staging subdomain), I’d rather ditch the plugin or the forms entirely…

Done, happy to cheer ??

Thanks for the lightning fast reply!

Turns out I still had define('WP_CACHE', false); in wp-config.php, feeling very stupid now, sorry about the false alert. I have deleted and manually re-installed the plugin anyway, works like a charm now.

Keep up the great work and happy holidays!

If you are comfortable with PHPMyAdmin and have a backup of your database, you can also run this sql command:

UPDATE wp_posts SET post_content = REPLACE ( post_content, 'h3>', 'h2>');

Please note that this will not work if your heading tags contain classes (inserted by some crazy visual editor or left over from dirty copy an paste).

Thanks for the kind words, always happy to help ??

Sure, thanks again for providing a fix in no time!