Jewel

@yarnboy you are a lifesaver! Thank you ??

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.

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.

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.

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.

Wonderful! Thank you!