CUNY Academic Commons

Hi Matt,

I'll try to take a look at this as soon as I can. I might be able to get to it by the end of the day tomorrow or Friday... I'll have to update my dev environment and debug, using the blog/post in question.

I'll let you know when I get a chance to poke around.

-Michael

Okay -- thanks, Michael!

The problem only seems to be occurring on production. I have requested access to the production error logs.

Cf. https://castiron.basecamphq.com/projects/3111292/posts/39662634/comments

-Michael

Ok, so after doing a little more investigating and examining the production error logs, I think that the most sensible thing to do, at the moment, is to wait until the 1.1 upgrade happens. The only thing that is different between the production environment and the development environments is the core version of WP. The only other thing I can envision doing would be to take a snapshot of the production environment and then debug in a private environment. But, seeing as how 1.1 is scheduled for this Monday, it just doesn't make sense to patch over a version WP that were not going to be using.

Is this acceptable?

It looks like the issue has been resolved with the 1.1 upgrade featuring both the blog and the post now work. I tested this on the home-dev page. I suppose this means that I need to mark the plug-in as only compatible with WP 3.0.2 and up.

I love easy fixes :)

Awesome. I'll test this out later today when I feature a post about the update!

Hi Michael,

I just tried to highlight the new post on the Commons News blog, and I ran into the same error. http://news.commons.gc.cuny.edu/2010/12/06/welcome-to-the-cuny-academic-commons-version-1-1/

Can you test really quickly on production and see if you find the same error? Or is there a better way to trouble shoot this?

Hi Matt,

It looks like the domain field included the protocol (http://) which isn't necessary; that field should take a value without the protocol and without a trailing slash.

The next round of development for the plugin should include some sanitizing functions to remove slashes and other unnecessary characters from field values.

If you select "post" from the content type drop down on the home page widget, the correct values should appear and if you save, the post should appear as expected.

-Michael