DaveE

Howdy,

I would start by checking the settings for the English version of the widget. Previous versions of FPW didn’t really distinguish between the different languages in use via WPML. This version does. You may need to just go in and reconfigure the English version of the widget to pull the correct content for your English site. That should fix it.

Sorry for the trouble.

Hi Kerri,

You’d need to adjust your theme’s styles to fix this. FPW doesn’t do any styling of it’s own. Sorry!

Hi Sagar,

Since I haven’t heard back in quite a while I’m closing this thread as resolved. You are welcome to post again if you still need support.

Cheers!

Thanks for the suggestion, Clifford. I’ve got a paid version of FPW in the works that will have more templates (including date display) and options than the free version available here. It’s in progress, but I don’t have a definitive launch date yet.

You can certainly create a custom output template to accomplish this now. The changes to the code to handle this are pretty small.

Thanks again!

Hi ank91,

Please find another avenue for your suggestions. This isn’t helpful as you don’t fully understand where/how this plugin (or other plugins) are used throughout a site. Your suggestion would indeed enqueue the scripts on the widgets & customize screens, but not other locations that the plugin may be in use (post.php, edit.php, etc). I have already tested and been through a long process of testing & development to ensure that my plugin does indeed need to be enqueued throughout the admin area because of these edge cases.

You are welcome to modify how any plugin enqueues it’s scripts as you see fit for your project. That’s why we use the whole enqueue process for plugins in WordPress–so you can customize the output/code as you see fit for your use.

Please stop posting this type of suggestion as a support request. I’ve responded and explained why it is how it is. Thank you.

The reference to $flexible_posts there is a PHP object containing the WordPress query details as well as the results. There is one property in the object called posts which contains the complete set of posts returned by the query. I’d suggest reading over the WP_Query documentation as that is how all result sets are generated in WordPress, including the ones used by FPW.

Hi fcpro,

This isn’t really a topic specific to FPW, but the bottom line is: you can’t. At least not easily. Multisite installations are intensionally designed to be completely separate “silos” of data. The are architecturally separated.

There are some complicated ways to pull data from one multisite instance into another (I’ve done it), but none of them are without their quirks or issues. And none of them are related to FPW.

When a plugin states that it is multisite compatible it means that the plugin will work as both a network activated and single-site activated plugin. It doesn’t ever infer that the plugin will merge data between the sites. Sorry for the confusion.