ah, good… the php error log usually has more insight into what is going wrong when presented with an error…  in this case, not sure there was such an indication so good find… thanks for the update..

to Scott Donihoo: thanks a lot for posting your solution! Worked like a charm for me! (Had the same issue as you on a dedicated server).

We have made changes so that no other more ‘legacy’ php sites have this problem in the forthcoming 5.7 release…