DaveE

Hi Johanna,

I’n not sure I understand your issue. Are you referring to the text that appears when you click on a post link shown in FPW from the home page such as the post titled This is not just an app? In that case, the layout and contents of the page are driven by your site’s theme. FPW has no control over that content.

If you’re referring to the text that appears on your website’s homepage inside the FPW itself, such as the text that appears for the same post and says, “Sagan om Skype har nog inte gått någon förbi? En av medgrundarna till Skype ,Janus Friis har åter gett sig…” then the issue would be that your FPW template is using the_excerpt() instead of the_content(). These are both standard WordPress functions and not used by FPW by default. Your FPW template must be custom, so you would need to edit your custom template to adjust that output.

Hopefully that helps. Thanks for using the plugin!

Hi Sagar,

I’m sorry, but I really don’t understand your issue or question. Can you try to clarify things for me a bit?

Thanks!

Glad you got it figured out!

I’m not sure I understand your question here, but there are many ways that different file sizes can/could be created and WordPress will always pick the next largest size available for the size requested. So, if you request a 150×150 image and the only size available is a 600×600 version, than this the one it will use.

There are tools like the Regenerate Thumbnails plugin that will check through your image assets (media posts) and for each one make sure the correct sizes are created based on the current image sizes defined by your site’s settings and the plugin & theme declarations for image sizes.

It is possible to adjust the query called by the widget via a hook that is in place just before the widget runs the query: $args = apply_filters( 'dpe_fpw_args', $args ); Here’s a thread with example usage.

Cheers,

Sorry for the delay,

I had a chance to test out the filter using the Genesis framework and their sample theme (the sample child theme StudioPress bundles with the Genesis Framework) and it works fine. Copied the code above into the genesis-sample theme’s functions.php file.

However, there is an exception. Are you getting posts by Post Type and Taxonomy & Term or by Post ID in the widget? If you’re getting posts by ID, then the filter wouldn’t apply. In that case, you’d want to adjust the filter as follows:

function current_recent_post( $args ) {
	if( is_singular() )
		$args['post__not_in'] = array( get_the_ID() );

	return $args;
}
add_filter( 'dpe_fpw_args', 'current_recent_post' );

If you aren’t getting posts by ID and the filter isn’t working, then the only other suggestion I have is that maybe another plugin or theme filter is causing the issue? I’ve found that other plugins/filters have been known to override FPW’s query settings when they use filters that are too lenient (apply to too many queries).

Hopefully that helps.

Hi Mppeter,

You’d need to paste this code into your theme’s functions.php file. Cheers!

Thanks for being willing. Yes, explaining in more detail would be helpful. Here are my thoughts after playing a bit more with Polylang & WPML.

I think it would almost make the most sense for a widget instance to be defined for each language (not mixed) and then only displayed on the front end for that specific language using the multilingual plugin’s setting for when to show a widget.

For example, you’d create one widget that gets English posts from an English category and only shows when English is selected and a second widget to get corresponding Spanish posts from the corresponding Spanish category and only show that widget when Spanish is the selected language. Of course, that means that for each supported language a new widget would need to be created. if there are 5 supported languages, the instance management becomes tedious.

On the other side, it becomes difficult for me to figure out how best to handle showing posts from multiple languages within the same widget instance as the number of possible combinations becomes exponential.

1. What are your expectations for how the term selector works with terms for each language (only show the admin language, show all language’s terms, etc)?
2. What should happen to a widget that has no results from the current public language?

Thanks again for being willing to help me figure this out. I appreciate it!