Forum Replies Created
-
Posts
-
Our plugin has no reference to a function call that is being shown on the error message. So this is likely coming from a customized code or some kind of plugin conflict on your site.
Please do the following to isolate the source:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/MailChimp keeps changing these things around and the addon is outdated now unfortunately. List name is definitely the same as Audience. I think the tags is what they used to call it groups before. So you will specify tags in there. You will need to do a test to see if that works. I no longer use MailChimp so I can’t test this one right now.
The main issue is that you have some customization requirements which our simple plugin does not support. Also, some of your issues are coming from some kind of conflict on this site. There is weird behavior happening on this site which is an indication of conflict that we don’t understand. There is some explanation of why conflicts can happen here:
https://simple-membership-plugin.com/message-from-the-simple-membership-team/We have offered you a full refund already since our addon is not a 100% good fit for your project. We will send you another email now.
Thank you. I will add a reference to this on our following page:
https://simple-membership-plugin.com/user-submitted-tweaks-simple-membership/Recently I saw this on another user’s site where it was happening due to a plugin conflict on that site. So it is worth doing the following test:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/Then try creating a new stripe subscription button on a test page using the following method. Check if that new one works (to get an indication if the old button has an issue or a stripe configuration is incorrect):
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/No. The passwords are kept using a ONE WAY hash. So you can’t look at the database and get passwords (this is the best security practice for storing passwords).
The following documentation of WordPress has an explanation on how passwords are hashed in the WP system. We use that same functionality in our Simple Membership plugin also:
https://codex.wordpress.org/Function_Reference/wp_hash_passwordThe best practice is to request your users to reset their password after you import their details. You (the site admin) can also go to the admin interface and set a new password for the member.
I understand what you are saying but our plugin’s simple architecture is not going to allow what you need to do with your current project.
It does give an error if a required field is not filled out. The issue will be related to some kind of conflict on this particular site that is preventing the error from showing. When there is some kind of conflict, things can behave very weirdly and everything seems weird. Please read the following post which will explain why it can be an issue with conflict:
https://simple-membership-plugin.com/message-from-the-simple-membership-team/It’s not counter intuitive in the context of a WordPress plugin. A customer can accidentally, delete the plugin. It is not a good idea to delete all member’s data and settings data on that site because then the user can lose all those membership setup that he/she has done over a period of time.
You may need to use a different plugin that will align better with what your particular project needs and doesn’t have any conflict with the server and any other combination of plugins that you are using on your site.
#1) Make sure all the following fields have values when you are trying to manually add a member entry:
– Username
– E-mail
– Password
– Membership Level#2) When you delete the plugin and re-install it, you don’t lose any data (for example: member’s data, membership level, settings values etc).
#3) If you made any customization to our plugin files, it can break functionality (if there is some kind of mistake in the customization). Any kind of customization is beyond the scope of standard support.
Let me explain how it works with woocomemrce so you understand where our plugin fits into this process.
When coupons are being applied via WooCommerce, our plugin has nothing to do with. It doesn’t know about any coupons nor does it care about it. Your woocommerce transaction (with the discount) is handled completely by woocomemrce. After the transaction, our plugin receives a notification from WooComemrce and then applies the membership level to the user’s profile (if the user purchased a membership level).
With that said, what you explained above with the discount is really not something that has any relation with the content project. Content protection is something that is controlled by our plugin. The protection will be there even if the wocommerce plugin is deactivated. The content protection saving works independently. There maybe some kind of conflict or other issue that is preventing the content protection saving functionality. You can do the following test to isolate things:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/It’s important to understand that the expiry is not something set in the user’s account. In our plugin, the concept of membership level is used to control the content permission and account expiry. This offers greater flexibility for a membership type setup. Read the following page to understand how our plugin works with membership level and the expiry is set in there:
https://simple-membership-plugin.com/adding-membership-access-levels-site/If you need to manually edit the expiry of a member’s account then you can edit a few parameter’s of the account to control this. The following page explains how to do this:
https://simple-membership-plugin.com/manually-activating-expired-members-account/The webhooks are most likely not setup correctly. So our plugin is never receiving the notification from Stripe after the renewal. Please go through the following documentation one more time and make sure the webhooks are setup with what it says:
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/
Also, do the debug log option as suggested by @mbrsolution.
This could be a mailchimp API version mismatch related issue. Which version of MailChimp API is being used for your account?
Also, check the following just to see if we can narrow it down some:
#1) Make sure to remove any requirement of fields for the list in question. Our plugin will only do the signup using name and email address. If your list has requirement for other fields, then the API request to add the user to that list will bounce. This is usually what triggers that 400 error.
#3) What value did you enter in the list name field?
#2) Remove any groups or any advanced setup. Only do a test with the standard signup to a list (without any other stuff). Does that simple signup work?
