jreeseUMD

mpionahq,
You’ve fixed your site, it looks like. How did you do it? I’m getting the same problem on our site. I’ve tried most of the same things that you did before I found this.

The version that causes the panic crashes is version 1.4 of Broken Link Checker on 3.3.1. I can get the server to fail by forcing the plugin (1.4) to execute, so we’re pretty confident that the current mix is the problem.

We don’t know about 1.5.4 yet, but will soon. I’ve got 1.5.4 loaded in our test server. We have hopes that it will fix the problem.

My predecessor got cas-plugin 2.2 to work with WordPressMU 2.8 in our environment. I’m trying to upgrade with cas-plugin 2.4 on 3.2.1. The cas server does get called, but the redirect back always ends up in a reauth state where you have to authenticate with the WordPress login screen. It seems like the token doesn’t get passed. In the cas-authentication.php script, it looks like $user is returned as true, but that’s not getting tied into the WordPress authentication hook somehow.

WordPress 3.3 came out about 2 days ago, so I’ll probably start hacking at the plugin with 3.3.

If there’s some simple edit that you made, please let the world know. This is the only game in town for CAS authentication on WordPress, it seems.

How did you get it to work? I’ve been over the cas-authentication.php script until my eyes bled, but no joy yet.