Maxime Michaud

Hello, thanks for the quick response, we’ve implemented it.

Unfortunately, it doesn’t seem to resolve the issue.
It only changed the log format, making it a bit harder to diagnose, but the issue remains similar.

[12-Sep-2024 07:04:51 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/*****/wp-includes/functions.php on line 7300
[12-Sep-2024 07:04:51 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/*****/wp-includes/functions.php on line 2189
[12-Sep-2024 07:04:51 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/*****/wp-includes/functions.php on line 7300
[12-Sep-2024 07:04:51 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/*****/wp-includes/functions.php on line 2189
[12-Sep-2024 07:05:25 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/*****/wp-includes/functions.php on line 7300
[12-Sep-2024 07:05:25 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/*****/wp-includes/functions.php on line 2189

These are not errors, but deprecation notices, and they tend to spam quite a lot. ??

I just saw the mention of a GitHub issue on another support topic.
https://github.com/WordPress/performance/issues/132
It’s a shame that it’s not being taken seriously. Personally, I don’t consider it dangerous. Despite being a major schema change that shouldn’t be taken lightly, I believe that a good large-scale implementation, with the right checks, couldn’t hurt for the benefit of WordPress.

Hello,

I am not the plugin developer, just a user, and I’m here to create my own question in a different ticket. However, I’ll answer your query.

It is possible to deactivate the index via this URL: /wp-admin/tools.php?page=imfs_settings

Revert keys: Revert to WordPress’s default keys.

I also imagine it’s possible to do it manually (with raw SQL), but I wouldn’t recommend trying that, so forget I even mentioned it.

For myself, given the importance and volume of my data and to ensure peace of mind, I would use wp-cli with this command:
wp index-mysql disable --all

After all this, you could have seen these options by checking the plugin settings or reading its main page.

Good luck! ??

That’s perfect, thank you for everything!

Hello,

Thank you for addressing the issue with the plugin update. We have automatic updates enabled, so I wanted to confirm: will the new update scheduled for release in August automatically apply?

Looking forward to your confirmation.

Best regards,

Hi,

Thank you for your prompt reply.

I appreciate the update regarding the progress on resolving the deprecation warnings. Could you please provide an estimated release date for the new version that includes these fixes?

Thank you for your support.

Hi, thank you for the fast update. It seems to have been successfully fixed on my end.

Thank you very much !

• This reply was modified 3 years, 1 month ago by Maxime Michaud.

OK.
Done

• This reply was modified 3 years, 3 months ago by Maxime Michaud.

Unfortunately, I am not the owner of the concerned website. I do not own the plugin.
Thank you,

• This reply was modified 3 years, 3 months ago by Maxime Michaud.

They both are. After reactivation of PixelYourSite, error is still happening.

Hi,
PixelYourSite Pinterest

Hi, on my side the latest update was causing a Critical Error on my website.
I don’t have any logs unfortunately, NGINX and WP_DEBUG did not give any.

Thank you !

Thank you, I confirm that the issue has been fixed.

Hi,
Same on my side.
We will await a fix.
Thank you !

2021/10/14 12:26:09 [error] 1173560#1173560: *95690 FastCGI sent in stderr: "PHP message: PHP Warning: require(/var/www/xxxx.fr/wp-content/plugins/webappick-pdf-invoice-for-woocommerce/includes/class-woo-invoice-fonts.php): failed to open stream: No such file or directory in /var/www/xxxx.fr/wp-content/plugins/webappick-pdf-invoice-for-woocommerce/woo-invoice.php on line 198PHP message: PHP Fatal error: require(): Failed opening required '/var/www/xxxx.fr/wp-content/plugins/webappick-pdf-invoice-for-woocommerce/includes/class-woo-invoice-fonts.php' (include_path='.:/usr/share/php') in /var/www/xxxx.fr/wp-content/plugins/webappick-pdf-invoice-for-woocommerce/woo-invoice.php on line 198" while reading response header from upstream, client: xxx.xxx.xxx.xx, server: xxxx.fr, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.4-fpm.sock:", host: "xxxx.tld", referrer: "https://xxxx.tld/"

• This reply was modified 3 years, 5 months ago by Maxime Michaud.