Forum Replies Created
-
Posts
-
We did send an email to your address at the xxxx@koeln-weekend.de domain yesterday. That looks to be an address on a domain. It may have gone to the spam box. Glad to hear that you got it sorted out anyway.
There seems to be a conflict on this site. Please do the following test:
https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/Hi, Let me explain this a bit more so you understand that the issue is in the language file of the language you are using (not the actual plugin’s code).
#1) The double quote or single quote in the code doesn’t matter. Both syntax is fine. If that was the issue then this transaction would not work for any other language translations where the end-user has done a correct full translation. I just verified that the language translation is working for that particular string so the code for it is fine. I am happy to change the double quotes into single quote but I know that is not really the main issue.
We ONLY provide the main language POT file with the plugin (simple-membership.pot). All the other language files that you see in the “languages” folder of the plugin has been submitted by a community user (someone just like you). So it is possible for a particular language file to have some formatting issues or incorrect strings or wrong translation. We don’t have an expert for all these different languages in our small team. So can’t verify all the translations unfortunately.
#2) In most cases, you will need to re-generate your language files from the main POT file to make sure everything is correct and you are not using a language file that a user submitted which has some formatting issues. You can do a quick test by deleting the German language translation files then re-create it for just a few strings to test and see how that works. The following page has info on how you can do a fresh new translation:
https://simple-membership-plugin.com/translate-simple-membership-plugin/#3) Any line that starts with a hash # character is a comment in the language translation file. It doesn’t matter if you keep that line or not.
I hope the above explanation helps.
To my understanding, it won’t work that way with the partial protection addon. The partial protection shortcode doesn’t control anything for an email.
Also, free members don’t need to pay anything. They don’t need to go through the woocommerce checkout to make a payment. So I am not sure how the setup you explained will work.
Looks like you are trying to protect a static file (which is not handled by our plugin). The following explanation will be helpful.
There are two parts to a media item/file:
1) The attachment page that WordPress will create when you upload the media file via the media uploader.
2) The actual static file (example: yourdomain.com/testfile.jpg) that you can access by going directly to that static file’s URL (this doesn’t go via the WordPress system). The above mentioned attachment page will link to this static file.The attachment page and the static file are two separate items. The 2nd item won’t be handled by our plugin at the moment. Different people will handle the storage of static files differently (for example: some people will prefer to put their files on amazon S3). So we don’t have a universal way of handling this at the moment. We usually recommend using a download manager type plugin to handle the static files. A download manager type plugin will have some features and options for hiding/protecting the static files. You can configure the file as a download item and then embed it on a protected post or page so only a member can download it.
A plugin like the following could be useful to manage the static files and handling the direct download of the static files:
https://wordpress.org/plugins/simple-download-monitor/I think you are referring to the following feature. This feature will ACTIVATE the account upon email verification (as the feature says “email activation”):
https://simple-membership-plugin.com/email-activation-for-members/The default behavior is explained in the above mentioned documentation. The following feature doesn’t apply for the above setup:
https://simple-membership-plugin.com/manually-approve-members-membership-site/If you want to manually approve members, you just activate the user manually so you don’t really need to use that email activation option.
If you want to allow space or other characters in the field where you will collect phone number, use a standard text field (instead of a phone number type field). A text field will accept any characters. You can call this text field “Phone Number”.
Also, please note the following when you are manually adding a member record from the admin interface while using the form builder addon:
With the Form Builder, the custom form and the fields of a member depend on the membership level. So when you want to manually add a record via the admin interface, you need to add the user with some minimal info and set a membership level and then save the profile. When you edit that profile again, it will show the custom fields option this time (since it will be able to load the fields based on the membership level).
When you want to edit a member’s profile, if you change the membership level, then you have to remember that the custom fields will change based on the new membership level that you are giving that profile. So if you want to manually change the membership level, you need to change the membership level first and save the profile. Then edit the profile again so the custom fields template is loaded according to the new level that you have assigned to that profile. Now, you can make changes to the custom field values of that profile and save it.There are CSS classes in the HTML output so you can target those to make some appearance related changes (for example: change the color, font, size etc). There is also a filter hook that can be used to override the code completely and customize it from a custom plugin for example.
If you tell me what and where you need CSS classes or if you need an additional hook, I can look into adding that.
Customization is subjective since different users will want different looks. So sometimes you may need a developer to customize it according to how you want it to look like on you particular site.
This usually happens when you have requirements for certain fields for your MailChimp list. Edit the list and make sure there is no special custom fields or other requirements to subscribe to the list.
The mailchimp addon will only add the user to the list using the email address and the name value. If your mailchimp list has additional field requirements, the API call to add user to the list will fail.
Ask your hosting provider if they are using database cache and somehow the database is reverting to an older cached version or there was a restore of the DB to an older restore point. Only your hosting provider will be able to look at the server’s internal logs and be able to offer insight in terms of what happened with those records that you manually inserted into the database.
If you want to import some members, we recommend using the following option which will import the members in a way that will be ready to be used with our plugin:
https://simple-membership-plugin.com/simple-membership-bulk-import-member-data-csv-file/Please check the following page and make sure the registration page and all the other required pages are in place with the expected shortcode.
https://simple-membership-plugin.com/recreating-required-pages-simple-membership-plugin/If you have modified the registration page and/or the shortcode in that page, it can have an unexpected behavior. So at least make sure the required pages are in place.
Then tell us if you are using free membership or paid membership on your site? If paid membership is being used, which type of payment buttons are you using for the paid memberships? Are the members getting an email after the payment? The following page has information that explains what you can expect step by step from the registration process. Tell us which step is not working for your site (so we can get an idea of where things are getting stuck on your setup):
https://simple-membership-plugin.com/membership-registration-process-overview/Please make sure that you didn’t delete your registration page that our plugin needs to function correctly. If the registration page is missing or it has gotten messed up from an edit you may have done to the page, it can cause an unexpected behavior like the one you described.
Check the following page and make sure all those required pages are in place with the correct shortcode in them:
https://simple-membership-plugin.com/recreating-required-pages-simple-membership-plugin/Also, have you edited the plugin’s code in any way? The debug logging information seem to be missing some lines that a normal install of the plugin is supposed to have. So either there is a conflict happening on this site or the plugin’s code may have been modified. If you edited the plugin’s code, it can have some unexpected behaviors. Best to delete the plugin and re-install a fresh un-edited copy of the plugin. You won’t lose any member or other settings data that you already configured in the plugin. So you can delete the plugin and re-add it from the wp.org repository. At least that will ensure that the issue is not arising from a code edit that has gone wrong in some way.
As soon as a user completes the checkout process (by entering the credit card details), the payment will be processed. The subscription will start if it is for a subscription type payment button. So you can’t tell the user to go through the payment/checkout process but not bill that user (meaning you want the user to only be billed after he activates the profile). That’s not how it works.
Let me tell you another way that you might be able to use to get close to what you want.
Modify the registration process using the following method. This way the user is not asked to pay or do a checkout until he/she has completed a profile on the site. You ask them to create a free user account first. After their account creation is complete. Then you ask them to pay. The payment will simply connect to the existing profile that they have already created (it will also upgrade the member’s membership level to the one they are going to pay for).
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/Let me know if that helps.
