tsikorski

Hi,
I would check the version of shibboleth client that you are running. My problem only occurred in an older version of the client. The shib 2.4 client doesn’t have the problem I described in my earlier post. You might want to make sure that you are actually seeing the variables a dump of the variables via
<?php
phpinof();
?>

might help to diagnose the problem.

Hi,
I had to fall back to version 3.6.5 to get saving to work properly again. The author and I traded a few emails on this topic and found that the problem appears to be specific to versions of php. My ISP’s php version seemed be the culprit. I created a test system installed the latest version of php, WP and suffusion and my test system didn’t have the problem. I am happy with 3.6.5 and will be staying there until my ISP upgrades it’s version of PHP. Hope this helps.

Ted

Thanks. I’ll consider doing that if I run into difficulties with 3.6.5 which would require me to upgrade to 3.6.6.

Found it and 3.6.5 does not have the problem. So this must somehow be releated to specific combination of LAMP environment of my ISP.

I might go and look at logs to see if there is anything obvious there but I don’t have a lot of hope. I guess I will have to wait for a newer version of PHP which is probably the culprit here. Thanks for you help.

Ted

Well it looks like this bug is somehow ISP related. I created a subdomain in which I installed wordpress and your theme. It behaved in exactly the same manner that is can’t change theme skins but can change other visual effects. Here is the relevant information in case you are interested:

Apache 2.2.16
PHP version 5.2.14
MySQL version 5.1.48-log

Do you have previous versions of your theme handy to see if this is 3.6.6 issue?

Regards,
Ted

Tried reseting the page and the entire site same problem.
Tried changing themes even deleted suffusion and re-installed it same thing. Something else in the environment that I am in is causing this but just for Theme Skinning which is most weird.

Tried exporting the mysql database to a test site and did the appropriate things to point wordpress at the exported database. That worked on the test site but when I copied the database back to the production site in a new database I still had the problem.

This problem seemed to have started after I upgraded to 3.6.6 if I have to I can start the site from scratch since there aren’t that many pages on the site yet. I was hoping to avoid doing that. I might install wordpress and your theme in a sub directory and see if this has something to do with my ISP’s environment.

Regards

Hi,
I was getting the same symptom using apache.

I changed line 130 in the file shibboleth.php to read:

$session_headers = array(‘Shib_Session_ID’, ‘HTTP_SHIB_IDENTITY_PROVIDER’);

instead of

$session_headers = array
(‘Shib-Session-ID’, ‘HTTP_SHIB_IDENTITY_PROVIDER’);

That seemed to fix things for me.