Project

General

Profile

Bug #419

Blog/Blog Post Featured Content Widget Errors

Added by Matt Gold almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
WordPress (misc)
Target version:
Start date:
2010-11-30
Due date:
% Done:

0%

Estimated time:

Description

Hi Michael,

I tried to feature a blog post tonight using the featured content plugin, but I ran into a problem. When I saved the blog URL and post slug, nothing appeared under the homepage under the "take a tour" link -- it looked like the featured content box just disappeared. (FWIW, I entered http://apicciano.commons.gc.cuny.edu/ (and, alternately, apicciano.commons.gc.cuny.edu/ ) as the blog and world-aids-day-–-dim-our-digital-world/ as the post-slug.

When that didn't work, I thought I'd try to feature the blog. But when I tried to feature Tony's blog, I saw only the subtitle of the blog and no image/text, and then nothing below the featured content widget on the page loaded.

Any idea what is going on?

History

#1 Updated by CIC Michael almost 9 years ago

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

#2 Updated by Matt Gold almost 9 years ago

Okay -- thanks, Michael!

#3 Updated by CIC Michael almost 9 years ago

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

#4 Updated by CIC Michael almost 9 years ago

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?

#5 Updated by Boone Gorges almost 9 years ago

  • Target version changed from 1.1 to 1.1.1

#6 Updated by CIC Michael almost 9 years ago

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.

#7 Updated by Boone Gorges almost 9 years ago

I love easy fixes :)

#8 Updated by Matt Gold almost 9 years ago

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

#9 Updated by Matt Gold almost 9 years ago

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?

#10 Updated by CIC Michael almost 9 years ago

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

#11 Updated by Matt Gold almost 9 years ago

  • Status changed from Assigned to Resolved

Awesome! Thanks, Michael!

Also available in: Atom PDF