Forum Replies Created
-
Posts
-
We will need to add a filter hook for this so for your site you can override this behavior.
I have added a filter hook to the core code which will go out with the next release.
You can download a zip file from the github repository now if you want to go ahead and use it right now:
https://github.com/wp-insider/simple-membership/archive/master.zipBelow is an example snippet of code showing how to use this new filter hook. You can add this code to your theme’s functions.php file to apply the override for your site.
add_filter('swpm_account_status_for_subscription_start_date_update', 'swpm_override_account_status_for_sub_renew'); function swpm_override_account_status_for_sub_renew($account_status){ $account_status = 'active'; return $account_status; }Hi, This won’t work unfortunately with the 2FA from the other plugin. So yes you need to look for an alternative membership plugin.
The following page has some explanation of why conflicts can happen:
https://simple-membership-plugin.com/message-from-the-simple-membership-team/The custom message addon doesn’t handle the partial content protection addon yet.
That “This content is for members only” message needs to be translated in the main plugin:
https://simple-membership-plugin.com/translate-simple-membership-plugin/What you are doing is going to cause unexpected behavior so I don’t recommend doing that. If are worried and want to delete a user account, simply delete the user from the Simple Membership plugin (it will delete the corresponding WP user entry also). Then the user can register again in the future (if he wants to come back and be a member).
The wp user entries are going to have a role of “subscriber” so that should not be any security concern (unless you are doing something on this site to give some membership levels a higher permission). You can review each of your membership level configuration and make sure you are setting the role to what you really want/need (normally it should be a “contributor” or “subscriber” role).
Alternatively, use a different plugin where it has the structure/architecture to do what you are trying to do in terms of deleting the WP user entry but not the SWPM entry. Otherwise, you won’t have a smooth operating plugin and that will simply cause more issues.
Regarding your original question, Just translate the language file of the core plugin (the main simple membership plugin’s language file). Those strings come from the core/main simple membership plugin.
So if you just translate the main plugin’s language file to your language, you should see them translated:
https://simple-membership-plugin.com/translate-simple-membership-plugin/We have sent 2 replies to your emails in the last 24 hours. Looks like our email maybe going to your spam box. Please check the spam box of your inbox and let me know if you see our reply.
There is no such thing as “Rejected registration” action. The admin simply uses the following feature to send an email telling the user whatever he wants to say when he changes the account status to “inactive” for example:
https://simple-membership-plugin.com/send-a-quick-notification-email-to-your-members/
That one “quick notification email” feature allows you to send an email to the user when you edit that user’s profile and change the account status for example. The email is sent when you save/update the profile.
Looks like your browser has the auto-unzip option enabled. So the zip file is getting unzipped automatically on download. Please temporary disable the auto-unzip feature then re-download the addon. If you submit the form that @mbrsolution posted in the previous reply, we will try to provide more help.
Looks like there maybe some kind of caching issue happening on this site. Cached page is being served to different users so you are seeing this weird behavior. This is a site specific issue that will require a lot of investigation. That will require a paid support ticket so time can be allocated for this.
Please read the following page so you understand:
https://simple-membership-plugin.com/message-from-the-simple-membership-team/Sorry, What you are looking for is not available in this plugin. What you can potentially do is the following:
Use your own databases table to store the value and keep a reference of the member ID in that table. So it will be like a relational table that can cross reference additional custom data. Alternatively, you can create custom post type and use that to store additional custom data and use the member’s ID as a reference (so you know which data is for which member’s profile).
If you are offering a fully free option then you can’t really stop a determined user from signing up again (as mentioned by @The Assurer already).
The way to stop this is to offer a paid trial option. You charge an small amount for the trial. That should deter users from doing this. This is one of the main reasons why some businesses offer paid trials.
Please upgrade to the newly released version (v4.0.3). This was a jQuery script related issue from WP5.6 update. It should be solved now.
That feature is really for developers since they will know what to do. If non-developers try to use that feature, it won’t work out. You will just get even more confused and we won’t be able to provide support for coding related work in this free support forum. That is beyond the scope of free support.
The better option is likely for you to use the contact form on our site to get in touch and maybe we can do a custom job for you to create an integration for constant contact.
Please fully read the following page slowly (there is a lot of info packed in there that will be helpful in understanding how the registration process works):
https://simple-membership-plugin.com/membership-registration-process-overview/If you don’t fully read the above mentioned documentation and try to understand how this particular plugin works, you may feel a little bit confused. So I want to make sure that you have read it and have that general understanding of our plugin’s registration process.
Now, given the kind of setup you are wanting to have, I would recommend that you try the following setup (as far as I understand it):
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/So the idea is that a user will create a basic free account on your site first. Then they will go the payment page and make a payment using the Stripe payment button. Upon successful payment, their account will be updated to the paid membership level (that they paid for). This way, they don’t have to come back to your site to complete anything (since the user account was already created before the payment). Only the account’s permission (membership level) gets updated in the background after the payment.
