DaveE

Thanks a bunch, Invens!

I am *just* about to release a new version of the plugin that has a few text string changes. Would you be willing to take take the updated POT file, update your Polish translation with the changes and repost it?

Sorry for asking you for the old just to replace it with a new version. I had some time to work on the plugin and would love to get the Polish version added this week.

Thanks again for being willing to translate!

Hi all,

I had a chance to dig into this a bit, but I’m not sure of how to resolve it. Basically, it looks like WPML actually sets up a different set of categories for each language, so trying to use it with both sets of categories is virtually impossible (since WPML only allows “access” to one language’s categories at a time).

However, I may be misunderstanding the situation some. I had thought the WPML people were going to help with a resolution, but I’ve never heard back from them. So, for now, I have to let this request stay as it is. Sorry!

Hi genshk,

Displaying the posts a different way would be up to your site’s theme, not FPW. FPW is intentionally design/theme independant so that it won’t ever conflict with the existing theme.

You could add the CSS styles from CHNL7700 to your theme’s stylesheet to get them to display that way.

Thanks for using FPW!

Hi Invens,

Thank you for translating! Unfortunately, I don’t see a link to the download. Can you post it somewhere I can get it via a browser or via http://pastebin.com/? I’ll get it added as soon as I get the translation.

Thanks again!

Hi Douby,

Sorry for the delayed response.

Something must be misconfigured on your site or with the customizations you made to the plugin/template. Without more info, I’m completely in the dark as to what the issue might be. Can you post the customizations you made as well as a link to the site causing the issue?

Thanks!

Hi AppDucate,

FPW doesn’t handle image resizing. FPW already allows you to pick what image size you’d like to display. Therefore, it would be up to your WordPress settings, a specific thumbnail size declaration in your theme’s functions.php or your theme’s styles.css file to work with sizes that are already created.

That being said, just adding another image size to “appease” page speed rankings isn’t always the best solution either. I often use a thumbnail size that is relatively small for a number of different placements, allowing the browser to rescale it a small amount to fit the situation. This is because, minor rescaling is less of a performance hit than having to actually download two different image assets depending on the placement.

Hopefully that all makes sense. Thanks for using the plugin!

Hi mpukit,

Sorry for the slow response. The bottom line is that FPW isn’t build to handling paging.

Specifically, the plugin has specific query vars set to only get the number of posts requested in the widget settings, so paging is effectively disabled. To enable paging, the plugin core would need to be modified to watch for a unique page number query var (or AJAX call) and then add that page number query var to each page/AJAX request.

In this case, you’re probably better off just creating a custom theme archive template and handling the display of posts that way since archive templates already have supoort for paging.

Sorry I’m not more help here. Thanks for trying out the plugin!

Hi sandropel,

I think @darrenparlett was correct in his response (see above). Let me know if this still isn’t working for you.

basically, in your custom template file, You’d want to add the date after the post title like this:

<h4 class="title"><?php the_title(); ?></h4>
<span><?php the_date(); ?></span>
</a>

Cheers!