Forum Replies Created
-
Posts
-
Were those users imported or manually created (as opposed to being created by the user following the special link after the payment?)
Every paid member account should have a value in the “Subscriber ID/Reference” field. If that is not there then something is not setup correctly somewhere.
I can’t don’t know how those transactions were done and how the user account was created but for us to be able to provide a definitive answer, we would need to see the problem being recreated with the debug logging feature enabled. Then we will get some clue as to what is happening on this site.
So first, enable the following feature:
https://simple-membership-plugin.com/enable-debug-logging/Then do a test transaction or wait for a user to do a transaction. Does the user account get created properly with the “Subscriber ID/Reference” field populated?
Also, you may want to explore the possibility of using the following registration process option (which is a good alternative for some setups):
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/Please empty your browser cache and cookies also. Try it again after that to see if that makes any difference.
Also, if this is a newly created PayPal account, please make sure to go through all the verification and other setups to get the paypal account fully approved.
Hi, Our partial protection shortcode is just a standard WordPress shortcode and it works fine on WordPress’s Guttenberg block/page editor. If you are using a different page builder on your site, you will need to ask them why the standard shortcode is not working with their editor (when it works fine with WordPress’s editor).
We can only make sure that our plugin works with the Standard WordPress install with standard WordPress editor. We certainly cannot make it work with all external plugins out there. Some of them will conflict unfortunately. You may need to look at using an alternative membership plugin since it is conflicting on your site:
https://simple-membership-plugin.com/message-from-the-simple-membership-team/We have released an update that should fix the issue. Please upgrade the plugin when you can and check it out.
Some of the most common messages can be customized using the following option:
https://simple-membership-plugin.com/simple-membership-custom-messages-addon/You can customize any messages that are output by this plugin by customizing the language translation file for your site:
https://simple-membership-plugin.com/translate-simple-membership-plugin/Hi Joni, Thank you for reporting this. This looks to be a conflict with the 2023 theme. It’s a new theme that we haven’t tested yet. There is a JavaScript error which is creating the unexpected output with the the theme. We will need to test and address this issue with the 2023 theme.
It will take a few days for us to address this.
We will have to continue to use the JS validation script that we use. There are some custom validation rules in there are we are not planning to change right now. You are welcome to try a different plugin so you can continue to build your project.
Please use the following contact form to get in touch regarding this paid addon related support:
https://simple-membership-plugin.com/premium-addon-support/Just to confirm, are you referring to the “attachment page” that WP creates for each of the media files that you upload? or a standard WordPress page that you have created and put some downloads on that page?
Does it happen on one particular page or all the pages on your site?
Yes, you can create a PayPal button and then a Stripe button (both for one membership level). Then offer both those buttons on your membership join us page as payment options.
You can create as many payment buttons as you want for any membership level.
There was a small bug in the new password reset feature. I have released an update just now that will fix it. Update the plugin when you can and then do another test.
The following free extension should override the password length to a minimum of 12 characters long:
https://simple-membership-plugin.com/simple-membership-minimum-password-length-override-addon/
Hi, The other registration option is to get the users to register for a free account and then direct them to pay afterwards. The following documentation explains how that works and how to set it up:
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/Our plugins works in a certain way (regarding the registration process) that we explain in the following documentation:
https://simple-membership-plugin.com/membership-registration-process-overview/I have added the filter hooks (required for this) in the core plugin. Next, I need to create a small addon that will allow the overriding to happen on sites that want to override it. It will be a few days before I can have that addon ready.
The mod security rule on this server seems to be giving a false positive for that action. You might be able to configure/customize the rule to remove this false positive. The hosting provider will probably be able to adjust/tweak the mod security configuration. The following file might have some additional insight into why the false positive is triggering:
usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.confI am not seeing this anywhere else so I don’t have enough data to guess where the conflict is coming from but it is some kind of conflict somewhere. Did you already try testing by switching the theme to a default WP theme?
What PHP version is being used on this server? Which hosting provider are you using? It is using the latest version of WP and the plugin?
Hi, The setup you are wanting to try will require a bit of manual intervention on an annual basis. So our plugin may not be the most suitable option. With that said, you could try the following:
#1) Every year when you create the membership level for the year, you will also create a temporary membership level (to assign users who pay for renewal before expiry for the following year). For this example, lets call this temporary membership level “Already renewed for next year”. Give this temporary level access to current year’s content.
#2) The renewal button can be connected to that following year’s temporary level that you create in step 1. So anyone renewing before expiry will get assigned to this “Already renewed for next year” level.
#3) At the start of the next year, when you create the new membership level for that year, you can do the following to switch all the members who already renewed to this new year’s membership.
Go to the “Members” menu then the “Bulk Operations” tab. Use the “Bulk Change Membership Level” feature to assign the “Already renewed for next year” members to the new year’s membership.
Let me know if that works.
