Fatal error with WP 6.3

Just an update- I am on Pantheon and the dev site is working with CAS even with the updates to core and PHP. It might be a plugin conflict but I’m still working with Pantheon on recovering the test site.

Update- Our sites that have gone through a core (6.3) or PHP 8.1 update revert to the generic wp-login.php page after a prescribed period of time or a purposeful logout by the user. CAS fails with the same error as I included in the first post. It is not a plugin conflict.

I initially rolled the dev site back to pre 6.3 and 8.1 updates and recovered the site. Then I updated the site first with the 6.3 update, clearing the cache several times. Then I ran the PHP update, doing the same cache clearing, etc. Dev was still accessible, no issues. I came back to work on the site a few days later, and it had reverted to showing the generic login. CAS was no longer working. The only thing I can think is that my CAS token expired the CAS plugin couldn’t reauthenticate.

Another update. Based on more research on these support forums, the issue may be with PHP 8 rather than core. I can’t verify it but just thought I’d mention it here. There are several tickets going back indicating issues when updating to PHP 8+. No reports of core being a problem.

I am having the same issue with the identical setup; the site in question is on Pantheon. We require login for all users, and the site is now throwing a fatal error. I can confirm that this is a PHP 8-specific issue. Version 8 is more strict about the status of variables passed as arguments, and things that were not fatal in 7.4 are most definitely fatal in 8.

I have done some work on this plugin in the past. If I can get a fix in place, I will post it here.

OK, after digging around in this today, I’ve decided that patching this plugin isn’t the best use of my time. My institution will be switching to a different plugin for managing our CAS integration. In the meantime, since you’re on Pantheon, you can temporarily resolve the problem by adding this line to your pantheon.yml file:

php_version: 7.4

This isn’t a long-term solution, as everything ought to be on PHP 8 now, but it’ll get wp_cassify working again until there’s an update, or until you choose PHP 8-compatible solution.

Thanks, @yarnboy. That’s exactly what I ended up doing but didn’t think to post what I did. Once I rolled back and then locked the PHP version to 7.4 in the .yml file I was able to update everything else and didn’t have any issues. Agreed, it’s a bandaid but happy to at least be able to keep core and plugins going for now. We’re going to have to look for another CAS option, too. If we get something else implemented, I’ll post back to the thread.

Hello again @jewelclark2020. My institution needed to get wp-cassify up and running with PHP8 while we look for a replacement, so I did end up doing some quick fixes. I’ve got a working git repo. Feel free to use if you still need it.

https://github.com/loesberg/wp-cassify-php8/

• This reply was modified 1 year, 2 months ago by yarnboy.

@yarnboy you are a lifesaver! Thank you ??

@jewelclark2020 Glad I could help!