JochenT

Thank you for the info. This is important.

Unfortunately we can not update the plugin as long as external requests are executed without user consent.

We use it on about a dozen websites, mainly with a pre Gutenberg selfmade website builder and for some more automated custom post types where Gutenberg is not so useful.

By the side, the current plugin version has still some problems with the ACF plugin. On the initial load of the post edit page all metaboxes are displayed in the first Tabify tab. After clicking on this tab the metaboxes are sorted properly to there assigned Tabify tab.

For me it works fine now, too. Thanks for the quick updates.

@markussss You are welcome. Makes no sense to create separate posts for this topic.

Hi topi_r,
I’ve created a gist with a class which allows to add/remove redirects programmatically. It is not an easy one liner.

class-redirection-redirects.php

We have the same problem. You should prevent your plugin from updating if it is not compatible any more.

Thank you for the nice plugin and thanks for the quick update.

Hi Doeke, thanks for your fast response and the nice plugin.

There was really a problem with the object cache. On the staging server object cache was activated to use the “Alternative PHP Cache (APC/ApCu)” method in plugin W3 Total Cache but on the hosting server this method was deactivated.

The SQL query has a syntax error at post_date_gmt < 2022-06-07 08:31:22 as the value ‘2022-06-07 08:31:22’ is not enclosed in quotes.

No, this is not anyone trying to hack your site. The SQL query has a syntax error at p.post_type = post as the value ‘post’ is not enclosed in quotes.

Thank you for the fast update. I’ve upgraded the plugin and the site is working properly again.

I am trying to update some legacy WP installments. When updating to the newest plugin version v5.18.2 I encountered a fatal error too. The WP version requirement for this plugin is set to WP 3.7.

Beginning with plugin v5.18.1 I assume that function wp_get_additional_image_sizes() is being used. But this function was introduced much later in WP 4.7. Maybe the plugin author can update the WP version requirement.

Hi Benbodhi, this notice is triggered if in function bodhi_svgs_inline() the value $bodhi_svgs_options['force_inline_svg'] is empty and the else branch ist executed.
WP function wp_localize_script() requires an array as third parameter but the values assigned in the else branch are strings.

I’ve added an excerpt of the stack trace of the PHP notice for the call in line 144:

at 10  /usr/www/users/stagih/wp-includes/class.wp-scripts.php#496 -> _doing_it_wrong(WP_Scripts::localize,Der Parameter <code>$l10n</code> muss ein Array sein. Um beliebige Daten an Skripte zu ??bergeben, verwende stattdessen die Funktion <code>wp_add_inline_script()</code>.,5.7.0)
at 11  /usr/www/users/stagih/wp-includes/functions.wp-scripts.php#221 -> localize(bodhi_svg_inline,cssTarget,img.style-svg)
at 12  /usr/www/users/stagih/wp-content/plugins/svg-support/functions/enqueue.php#144 -> wp_localize_script(bodhi_svg_inline,cssTarget,img.style-svg)
at 13  /usr/www/users/stagih/wp-includes/class-wp-hook.php#292 -> bodhi_svgs_inline()

I’ve send a support request to ACF. Perhaps they can solve the problem without to much hassle.

The reason for this problem is not WP 5.5 but plugin Advanced Custom Fields. Just updated ACF from v5.8.9 (no problems) to v5.9.1 on WordPress v5.4.2 and this behaviour did occur too.
Just have tested some more ACF version. The problem starts with ACF v5.9.0.

I remember that this behaviour already did occur previously on our websites. But I don’t know if much older versions of ACF were the reason at that time.

• This reply was modified 4 years, 6 months ago by JochenT. Reason: More specific info

We have had similiar issues with sending from our domain example.com to a Microsoft Exchange Server since some time. The emails were only for internal use so we set the from email to a none existing mail account (e.g. [email protected]).

Others have confirmed to us that the fake address may be the reason of the problems.

Now we have changed the from address to an actual existing mail account. As the changes have been applied just today I can not yet tell if this works. But this maybe helpful as a hint to a possible reason.