Bigue Nique

In the meantime, the following code snippets will do !

Customize tab title :

add_filter( 'buddytask_get_name', function() { return "Tasks"; });

Customize slug :

add_filter( 'buddytask_get_slug', function() { return "tasks"; });

But how do you add BuddyTask to an existing group ?

EDIT: Ok, got it! The option to activate is available in the BuddyTask tab of the group settings tab.

• This reply was modified 1 year, 6 months ago by Bigue Nique. Reason: found it

You can fix this yourself by creating a permanent redirection (301) from the redundant (old) URL to the new URL. You can set a rewrite rule in .htaccess (Apache) or use a plugin like Redirection.

Ok, thanks a million for looking into my issue. I’ll investigate further on my side when I get a minute. I’m marking the issue as resolved since it’s not caused by LocoTranslate.

Thanks for the quick answer!

I just had the chance to try WPKoi Templates with one of your free themes. Your work is truly outstanding, it is an endless well of free-flowing creativity!

People of Earth: you should definitely take a look at this plugin and the WPKoi themes. Hint: read the theme’s doc to quickly get going.

(I guess I should rather post this in the reviews! K?sz?n?m!)

• This reply was modified 2 years, 2 months ago by Bigue Nique. Reason: typo

Worth noting: network has buddypress activated network-wide.

Hi @centosa,

Under Episode Image, you can simply select manually the same image as the featured image from the media library. SSP creates the appropriate thumbnail format automatically.

From your screenshot, it seems that you have been trying to share a private link, ie. that is only visible to you as a logged-in user on the target site. This is the reason why the link preview display the information from the login page. Try opening the link in a private browser window to see what I mean.

For my share, I can’t find the default options in the Writing Settings page. I need to be able to enable it on specific posts only. That renders the Classic Editor unusable for this particular project.

WP 5.9.3/PHP 7.4.29 on a single site (in a multisite network).

Similar problem here (but I don’t get the second message about different feeds).

I just reported the issue on GitHub: https://github.com/radgeek/feedwordpress/issues/134

I know the author has recently updated the plugin and is going through some massive code cleanup. Hopefully the issue will come to their attention and we’ll get an update soon!

I’ve been using both these plugins on massive aggregated news sites with some satisfaction:

– FeedWordPress Duplicate Post Filter: https://fr-ca.www.ads-software.com/plugins/feedwordpress-duplicate-post-filter/
– Delete Duplicate Posts: https://fr-ca.www.ads-software.com/plugins/delete-duplicate-posts/

The first one works with FeedWordPress and will prevent most duplicates.

The second one will eventually catch those duplicates that slip through the first one. The free version is flexible enough and you can synchronise it with the FeedWordPress update schedule. The worst that could happen is some duplicate that will be visible for some time (between two consecutive updates).

I’ve been using both these plugins on massive aggregated news sites with some satisfaction:

– FeedWordPress Duplicate Post Filter: https://fr-ca.www.ads-software.com/plugins/feedwordpress-duplicate-post-filter/
– Delete Duplicate Posts: https://fr-ca.www.ads-software.com/plugins/delete-duplicate-posts/

The first one works with FeedWordPress and will prevent most duplicates.

The second one will eventually catch those duplicates that slip through the first one. The free version is flexible enough and you can synchronise it with the FeedWordPress update schedule. The worst that could happen is some duplicate that will be visible for some time (between two consecutive updates).

I’ve been using both these plugins on massive aggregated news sites with some satisfaction:

– FeedWordPress Duplicate Post Filter: https://fr-ca.www.ads-software.com/plugins/feedwordpress-duplicate-post-filter/
– Delete Duplicate Posts: https://fr-ca.www.ads-software.com/plugins/delete-duplicate-posts/

The first one works with FeedWordPress and will prevent most duplicates.

The second one will eventually catch those duplicates that slip through the first one. The free version is flexible enough and you can synchronise it with the FeedWordPress update schedule. The worst that could happen is some duplicate that will be visible for some time (between two consecutive updates).

I managed to solve this issue by 1. removing (renaming) /wp-content/object-cache.php, then 2. deactivating and reactivating the Litespeed Cache plugin.

A new object-cache.php then gets created, along with a new .litespeed_conf.dat (on which it relies instead of former .object-cache.ini).

I’ve enabled reCAPTCHA on login and registrations pages for a while on a network-enabled Wordfence, and it works well everywhere else, but now I’m getting this problem (Login Verification Required) on a WooCommerce site on the network.

1. I confirm that disabling reCAPTCHA in Wordfence > Login Security > Settings (or running reCAPTCHA in test mode) apparently solves the problem on the WooCommerce site.

But it sound a bit foolish to disable security on the entire network for a single site. Yet, I need this site to work properly.

My intuition is that reCAPTCHA fails on the WooCommerce login page simply because Wordfence fails to integrate the reCAPTCHA field to it.

In Wordfence documentation about Login Security Options (here), we can read this:

Enable WooCommerce integration
Enable this checkbox if you are using WooCommerce and would like Wordfence Login Security features such as the reCAPTCHA and 2FA to work on the WooCommerce Account page. We recommend testing your login pages after enabling this option, to be sure there are no conflicts with other plugins that modify the login page.

But I can’t find this option anywhere. Does WooCommerce need to be network enabled for this option to show up? Heck, let’s try it! So I just enabled WooCommerce network-wide, just to see, and reloaded the Login Security page. No options shows up, but a little tiny warning message:

We’ve detected that you’re using WooCommerce. reCAPTCHA support is currently incompatible with the WooCommerce login page and should not be enabled. Support may be added in a future version.

Not very helpful. But that sort of confirms my initial assumption.

So, now what? Can we disable reCAPTCHA verification on a single site? Or am I damned to disable it on the entire network?

Any insight welcome.