DaveE

Hi EdmundoZ,

Just a heads up that it doesn’t work to add “Standard” as a Post Format option. The reason for this is that WordPress doesn’t actually create a “Standard” term. Instead, any posts without one of the other formats assigned to it defaults to “Standard.” In essence, Standard is the absence of a post format. I can’t do a query for: all posts without a post format term AND all posts with the post format “Gallery” (for example). That’s not logically possible.

So, that being said, the best solution will be to use a tag or another taxonomy & term and assign the same term to posts with the “Standard” and another post format. Then, with FPW, just use the tag or tax&term you assigned to all the posts you’d like to show.

Hopefully that work around will help. Cheers!

Hi EdmundoZ,

Since I haven’t heard back from you in over 2 weeks, I’m going to mark this topic as resolved. Please feel free to re-open it if you continue to have questions.

Thanks!

Hi cgsciandra,

Flexible Posts widget doesn’t do any styling. All styling is controlled by your theme, even WooThemes. If something isn’t appearing right, then you’ll need to verify it with the theme provider.

If you’d like more help from me, please provide a link where I can review what you’re having trouble with. That way, I can give you specific feedback related to the theme you’re using instead of just guessing.

Cheers!

Hi EdmundoZ,

Unfortunately, the way that WordPress core handles sticky posts is very, very specific and there isn’t an easy way for me me to work around it. The quick answer is yes, adding a tax & term to any WordPress query will ignore the sticky post functionality for that query. This applies to FPW and even writing your own WP_Query directly.

The way I’ve worked around this on several projects is to setup two FPW’s one right after the other. In the first widget, I’ve used a simple tag called “sticky” or even created a separate taxonomy & term specifically for this and also set the number of posts to display to 1. This in effect is your “sticky” post. In the second widget, I don’t set a widget title so the listing look like it is still part of the previous widget (this may require some minor styling work as well – depending on your theme) and then gotten the regular post results as if they were a continuation of the previous widget, but not including the “sticky” post. Hopefully that makes sense. I realize the explanation is a little difficult.

As for the Post Formats issue, you’re correct. I am missing a “Standard” option. (It’s a technical issue with the way the “Standard” post format works in core.) I’ll get that fixed in the next release of the plugin. Thanks for bringing that to my attention.

Cheers,

Hi Jason,

In thaikick’s original post, he specifically states that the custom templates he coded from scratch (but didn’t move from the plugin’s folder into his theme folder) were lost, so I doubt he was referring to the settings which get stored in the database.

In your case, unfortunately I don’t have an upgrade process in place when moving between MAJOR versions of the plugin. If you’re already running version 3.0 or above, then going to 3.0.2 won’t cause any issues.

And, even when moving between version 1.x.x or version 2.x.x and version 3.x.x not all settings will be lost. It really depends on what you’ve configured for each widget. I use the plugin on about a half dozen live sites, some of them with multiple instances of the widget. Even with the ~12+ widgets out there, it didn’t take me long to reset the post types & tax/terms selected for each widget. These are the only settings that should cause issues. Any titles, ordering, counts, thumbnails & custom template settings should remain intact.

I’m sorry there isn’t an easier/better way. Hopefully the plugin has matured enough where I will no longer need to make code changes that will cause upgrade issues at all. That’s one of the goals from v3.

Sorry for the trouble,

Hi ilbobbi,

It’s hard to say what could be the issue without knowing a little more.

First, do you have a feature image set for the portfolio items you’re trying to display? FPW will only try to show the feature image, not other images attached to the post.

Second, are you using the default widget template that is included with the plugin or are you using a custom template? If you’re using a custom template, make sure that the post_thumbail code is properly placed as it is in the default template.

Third, have you double-checked the HTML source of the page where the image should appear? The image could be in the source, but your theme’s styles may prevent it from appearing.

Hopefully one or more of these ideas will get it fixed for you. Cheers!