[admin]

Since you already have a dedicated thread for this question, I’ll continue the discussion and provide my response there:
https://simple-membership-plugin.com/forums/topic/how-to-enable-search-of-country/

[admin]

I’ll take another look at this over the next few days and get back to you with an update.

Since this issue relates to a premium add-on, please submit a support request via the following page so I can follow up with you by email:
https://simple-membership-plugin.com/premium-addon-support/

[admin]

Let me add some more context.

This thread is referring to the Member Directory Listing Addon:
https://simple-membership-plugin.com/simple-membership-member-directory-listing-addon/

The search feature in the Directory Listing Addon can search the following fields:

Username
First Name
Last Name
Email
Company Name
Custom Fields (text-based fields work best)

Is your question related to the Directory Listing Addon?

[admin]

Hi, No you don’t need form builder addon for that.

Translation strings missing mean it hasn’t been translated in that specific language yet. The following translation documentation should be helpful:
https://simple-membership-plugin.com/translate-simple-membership-plugin/

[admin]

We don’t have a built-in feature for post allowance.

[admin]

Thank you for submitting the ticket. We have responded to your inquiry.

[admin]

Thank you for reporting this. Looks like Stripe has updated their UI. I have just updated the documentation to so it matches closely with the current Stripe UI:

https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/#create-a-webhook-in-your-stripe-account

Here is the documentation for creating a Stripe webhook:
https://simple-membership-plugin.com/create-a-webhook-in-your-stripe-account/

Here is the documentation for configuring webhook signing secret:
https://simple-membership-plugin.com/configuring-the-stripe-webhook-signing-secret/

Let me know if this is helpful.

[admin]

@Naovaczid, It will be an issue with the site’s setup. Do you have debug log data similar to what the previous poster shared?

[admin]

If you only created this button a couple of months ago, there’s no need to create a new one. Just update the Stripe webhook API version to the latest from the Developers menu in your Stripe account. After that, reset the debug log file and monitor new transactions for a few days to see if any issues come up.

[admin]

That looks fine to me. Everything executed as expected, and the recurring payment was processed correctly (membership level retained, account remained active).

One thing worth noting: the Stripe webhook events in your log are coming through with api version: 2018-05-21, which is quite old. This indicates the subscription button was likely created some time ago. You can upgrade the API version from the Developers menu in your Stripe account.

Since the button has been around for a while, it’s a good idea to review the current Stripe subscription button documentation and make sure all the steps are still valid for your setup:
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/

You can also follow the documentation to create a new Stripe subscription button and replace the old one on your site. Existing subscriptions will continue running without interruption. Only new subscribers will use the new button. This is a good way to ensure that going forward, all new subscriptions are using the latest API version and the most up-to-date setup.

[admin]

Every site is different, and the original poster’s situation may include background details that don’t apply to yours.

The feature being discussed in this thread is documented here:
https://simple-membership-plugin.com/giving-wordpress-admin-user-access-protected-content/

There is no known bug with this feature. If it’s not working on your site, it’s most likely due to a conflict with another plugin/theme or a configuration issue.

If you’d like help troubleshooting, please describe your specific setup — what you’ve configured so far, what you expected to happen, and what’s actually happening. With that context, we can provide useful guidance.

[admin]

Thank you for sharing the log data. Unfortunately, this particular log doesn’t contain any recurring payment-related entries, so I’m unable to identify the issue from it. For us to troubleshoot effectively, the log file needs to cover the exact time when the issue occurs. I’d recommend resetting the debug log just before a recurring payment is due, so it captures only the relevant data from that event without unrelated noise.

A couple of clarifying questions to help us narrow this down:

1) When you mention “first invoice”, do you mean the very first checkout (when the user clicks the subscription button to create the subscription agreement), or the first recurring payment that occurs after the initial checkout?

2) From the timeframe covered by the current log, can you confirm whether the account was created correctly with the right membership level during the user’s registration/checkout attempt?

Also, since you’re using the WooCommerce addon as well, please go to that addon’s settings and make sure a value is set in the “Default Membership Level” field under the auto-create member account option. Missing this configuration can sometimes cause unexpected level assignments.

Once you’re able to share a fresh log covering a recurring payment event, we’ll take another look.

[admin]

The swpm_account_status_for_subscription_start_date_update filter hook is only used if some custom code on your site explicitly hooks into it. It is not something that runs by default. So unless you (or a developer) have added custom code for it, your site is most likely not using this filter.

You can check by doing a quick search for the filter name in the following places:

– Your active theme’s functions.php file.
– Any custom snippets added via a code snippets plugin (e.g., Code Snippets, WPCode).
– Any custom plugins you may have installed on the site.

In the meantime, please go ahead and capture the debug log when the next recurring payment comes in for one of the affected members, then share the relevant portion of the log file with us. The log will show exactly what status value is being applied to the account when the recurring payment is processed, which will help us pinpoint the cause.

[admin]

Please enable the debug logging feature and capture the event so you can share the log file with us:
https://simple-membership-plugin.com/enable-debug-logging/

This will let us see what account status value is being used when the payment is received.

Usually, this issue can be caused by one of the two things outlined below, so please check them as well:

1) “Default Account Status After Payment” setting

The value of this settings field may be set incorrectly. Our plugin sets it to “active” by default, so it’s a good idea to make sure it is set to active and then save the settings.

2) swpm_account_status_for_subscription_start_date_update filter hook

The plugin has this filter hook, which can be used to customize the account status after a recurring payment. If your site is using this filter to apply custom logic that returns an incorrect account status value, it can cause this issue.

[admin]

This one is a duplicate of this other post on WordPress.org forum so I will close this one here:
https://wordpress.org/support/topic/passkey-support-3/

[Author]

Posts