CUNY Academic Commons

Thanks, Boone. I completely understand your concern.

Here's my problem right now: Even after you did the update, my sites are still not rendering properly and I'm pretty sure that it's because one of my theme's php scripts is failing out silently, and I'm almost certain I know which one it is. On my development site everything seems to be working fine and I don't get any php errors, even after forcing full php tags and including all of the same plugins as on the live site.

Would it be possible to send me a copy of the php.ini that is being used on the commons server so that I can make sure that my development server more closely mirrors the live one and I don't keep running into problems that I can't reproduce locally? Or any other suggestions you have for debugging would be greatly appreciated.

I'll see what I can do about getting you a copy of the php.ini file (or seeing if I can think of any better ideas). In the meantime, can you send me a link to the specific page that's causing problems, with a description of what's wrong?

Any page on this site: http://globalization.gc.cuny.edu/ that calls my customized content.php is erroring out, but pages that use any other loop template load fine. I thought the problem was simply my use of a php shortcode (which was also a problem), but fixing that didn't fix the page load issue on the live server.

What should be happening is in the main loop it should load a bunch of posts and display them blog style. It errors out after loading everything up to the main loop.

Right now I'm trying to debug using the samsarin php widget and an error handling function and am just stepping through the code line by line...

figured out my problem.

I was cheating by referencing a function-array (eg foo()[$index]) instead of assigning a temp variable first. My server is running php 5.4 which allows this, while the commons is on 5.3.3, which doesn't allow it.

the commit that fixes this problem is hash 4defa49742d5d7f48fff2e40f0846f7838b53e71

Sorry for all of the headaches. I appreciate your help, Boone.

I just found the same thing, and was blocked in posting because you found it a minute earlier.

I've put in a hotfix, and will update the reference for the next release. Glad we could track down the issue.