David Bisset

@callmejud thanks for reaching out – good question!

Yes, you can change the /campaigns/ slug using the charitable_campaign_post_type filter. Drop this into a snippet plugin (like WPCode) or your theme’s functions.php:

add_filter( ‘charitable_campaign_post_type’, function( $args ) {
$args[‘rewrite’][‘slug’] = ‘campanyes’; // your translated slug
return $args;
} );

After saving, go to Settings -> Permalinks and click Save Changes to flush the rewrite rules… otherwise your campaign URLs will 404.

A couple of quick notes:

• Keep the slug lowercase and URL-safe (no spaces or accented characters).
• If your site is already live, set up redirects from the old /campaigns/… URLs to the new ones so you don’t lose links.

Hope that helps! Let me know if you have any questions.

We are going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation.

Thanks!

@fcoerezza thanks for reaching out!

I want to start by reassuring your Stripe integration is working correctly. The notice you’re seeing is a reporting mismatch following a recent update. Our new setup tool is currently optimized for all cases and because you are using the Stripe Connect method, the plugin is simply being over-cautious and triggering a warning even though your connection is perfectly healthy.

You can safely ignore the notice for now and apologize for the confusion. We are releasing an update after the weekend to refine this logic specifically for Stripe Connect users, which will clear the message.

I’ll be happy to ping you here once that update is live so you can grab it and clear the alert. Thanks for your patience and let me know if you have any questions. 🙂

Hi @cameronbq,

I am very sorry for the trouble here. Our team identified this specific issue involving a conflict in the Stripe integration logic shortly after the 1.8.10.1 release. We have just pushed version 1.8.10.2 which contains a fix.

Since you have the plugin deactivated currently, you should be able to update to 1.8.10.2 via your dashboard or CLI and then reactivate the plugin. Even if you are not using the Stripe connection, this update ensures the migration check no longer triggers that fatal error. Could you give that version a try and let us know if it resolves the issue for you?

Thank you for your patience and for providing the detailed error log.

@ebfuser thank you! you’ve been patient and kind as well. It’s great having you as Charitable users! Please continue to reach out if you need anything or want to share suggestions and feedback!

@thefredjacobs

Hello! Good to meet you.

Assuming you are referring to our official Charitable PayFast gateway add-on, the add-on has been consistently maintained and updated with various improvements and compatibility fixes since 2019. It is currently working well, and we have many customers successfully using it to process donations in South Africa today.

Questions about addons in the future should be directed toward our website since this ww.wp.xz.cn forum is primarily for questions and support for the free plugin.

Hope this helps! Thanks for reaching out!

@itapress Thank you! I will pass this along to the team. Likely will see a fix in the next maintenance release coming shortly. I’m going to mark this as resolved however if you wish to be nodified when the release is out or if there’s any further questions – please continue the conversation. 👍🏻