PHP8 Error: Multisite Yoast (redirects) & WordFence incompatibility when network activated (2)

Yoast / wordpress-seo

Yoast SEO for WordPress

https://yoast.com/wordpress/plugins/seo/

Other

1.77k stars 893 forks source link

PHP8 Error: Multisite Yoast (redirects) & WordFence incompatibility when network activated (2) #21519

Closed fiskhandlarn closed 2 months ago

fiskhandlarn commented 3 months ago

[x] I've read and understood the contribution guidelines.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened

To Reproduce

Step-by-step reproduction instructions

Move a page and let Yoast automatically create a redirect
Visit the old URL

Expected results

The redirect happens without errors

Actual results

This error is cast: Undefined constant "SECURE_AUTH_COOKIE"

Technical info

Which browser is affected (or browsers):
[x] Chrome
[x] Firefox
[x] Safari
[x] Other: all of them, this is a serverside error

Used versions

Operating system: Linux
PHP version: 8.1
WordPress version: 6.6.1
WordPress Theme: custom
Yoast SEO version: 23.1
Relevant plugins in case of a bug: WordFence 7.11.7

josevarghese commented 3 months ago

Hi @fiskhandlarn

Thanks for creating the issue. I tried replicating it with Wordfence and Yoast SEO + Yoast SEO Premium (23.1), but the issue is not reproducible. I also noticed that earlier there was a fatal error before with Wordfence on the subsite, and it has been fixed on version 20.3 of the Yoast SEO Premium plugin.

So, please make sure you are using the latest Yoast SEO and Yoast SEO Premium plugins of version 23.1. If yes, please share the exact steps to replicate it on our end with a video to replicate it on our end.

webartistse commented 2 months ago

Had the problem PHP Fatal error: Uncaught Error: Undefined constant "SECURE_AUTH_COOKIE" with following:

Wordpress 6.5.5 with multisite
PHP 8.2.19
Yoast 32.0
Yoast Premium 32.2

I updated Yoast to 32.2 and that solved the problem.

josevarghese commented 2 months ago

Hi @webartistse

Thanks for the comment and for mentioning that updating to 23.2 fixed the issue for you.

I am closing this issue due to inactivity from the issue creator and the issue is fixed for another user. If the issue persists, please provide additional information so that we can investigate it further.