Forum Replies Created
-
AuthorPosts
-
admin
KeymasterHi, Your plan should work, but there are a few things to watch.
1. The 28 classes and access control
eMember controls content access by membership level, not by a custom field. If the 28 classes need to see different parts of the site, they need to be separate levels. Since price is set on the payment button, you only need buttons for the price and duration combinations you actually sell. You don’t need one for every class and duration pair.2. Use 1 July as the start date, not 30 June
The expiry date is calculated from the “Subscription Starts” date plus the level’s duration. If the start is 1 July, a 1-year membership runs to the following 1 July. If you use 30 June, everyone gets one day less. Your year rule is right otherwise:Paid 1 April to 31 December: start is 1 July of the current year
Paid 1 January to 31 March: start is 1 July of the previous year3. Make sure the script only picks the right accounts
Selecting accounts by “start date = yesterday” will also pick up any record whose start date changed yesterday for another reason, such as a manual edit by the secretary. Exclude those, or limit the script to accounts created or paid yesterday. Late renewals by lapsed members do get their start date reset to the payment date, so your script will correct those as intended.4. Early renewals
On-time and early renewals extend from the current expiry date, so they stay on the 1 July cycle and need no action.5. Test first
Updating the members table directly is a custom change, so please back up the database before you start. Test the script on a few test accounts before you schedule it. Run it at a fixed hour in your site’s timezone so that “yesterday” means the same thing to the script as it does to WordPress.admin
KeymasterWe have sent you an update via email.
admin
KeymasterHi John, You can do this with far fewer membership levels than you are expecting. A few points about how eMember works will help explain the approach:
1. A membership level controls content access and the membership duration. The price is set on the payment button, not on the level. If your 28 membership classes all get access to the same content and differ only in price, they don’t need to be separate membership levels. You only need one level per duration, so 5 levels in total (1 year, 2 years, 3 years, 4 years and 5 years). You can then create a payment button for each class and duration combination, pointing to the matching level. If you need to record which class a member belongs to, you can store it in a custom field.
2. We recommend using duration-based expiry (for example “1 Year”) rather than a fixed expiry date. A fixed expiry date applies to every member on that level, so it would need to be changed every year, and changing it would extend everyone on that level, including members who haven’t renewed.
3. With duration-based levels, the expiry is calculated from the member’s “Subscription Starts” date. When an active member renews, the new period is added from the end of their current expiry date rather than from the payment date. So once a member’s start date is lined up with 1st July, it stays lined up every time they renew on time.
4. For new members, the start date is set to the date they paid. To line them up with your membership year, edit the member’s profile in the admin area and change the “Subscription Starts” date to the 1st July that started the current membership year. For members joining after 1st April, set it to the upcoming 1st July instead, which gives them the free period up to 30th June automatically. You would do the same for a lapsed member who renews after their membership has expired.
This way nothing needs to be changed on 1st April each year. The only manual step is adjusting the start date for new members and late renewals.
You can find more details in the eMember documentation:
Thank you.
admin
KeymasterHi, Thanks for the suggestion. Editing the option at line 767 of eMember_registration_utils.php on its own won’t be enough, for two reasons:
1. The edit profile form has its own copy of the title list (in eMember_profile_utils.php), so the new option would not show up when a member edits their details.
2. The “title” column in the eMember members database table only accepts a fixed set of values (Mr, Mrs, Miss, Ms, Dr). Any other value, such as “Prof”, will not be saved correctly unless the table structure is updated as well.Because of this, we will add “Prof” (Professor) to the title options in the core plugin. The next eMember update will add it to the registration form and the edit profile form, and will also update the database table. That way you don’t need to modify any plugin files, and nothing is lost when you upgrade.
If your members need a fully custom set of titles (for example, a combined “Prof Dr”), you can use the Form Builder addon to create your own drop-down field with any options you want:
We will update this thread once the new version is released.
admin
KeymasterHi, The registration form loads a small CSS framework (Pure CSS) for its layout. Pure includes a standard reset stylesheet, and one of its rules adds a margin of 1em top and bottom and 40px left and right to every
figureelement on the page. WPBakery wraps its images in afigureelement, so they pick up that margin and appear smaller. That is why the spacing goes away when the form is removed.Add the following to your Custom CSS, along with your existing rules:
.vc_figure { margin: 0; }This resets the margin on WPBakery image elements only and won’t affect the registration form. Clear any caching plugin or server cache after saving, then reload the page.
Thank you.
admin
KeymasterYou can also create two versions of the category: one protected and one publicly accessible. Add the posts you want to restrict to the protected category, and add the publicly available posts to the unprotected category.
August 7, 2026 at 10:10 pm in reply to: Form Builder – Enable custom fields vs custom fields emember #85250admin
KeymasterThanks for checking on this before making changes.
On the custom fields checkbox: unticking the “Custom Field” checkbox won’t delete any of your existing configuration. The data stays in the database, so you can toggle those fields on or off without losing anything.
On the form builder: for the form builder to work, you’ll need to configure the fields within the form builder itself. It can’t pull from the simple custom fields that the core plugin provides.
The reason for that is structural. The simple custom field system was never built to scale, which is exactly why we created the Form Builder addon. It uses a more robust structure that lets us offer a much wider range of field types and configuration options.
If the form builder doesn’t turn out to be a good fit for your use case, please submit a request through the contact form on our site and we’ll be happy to issue a refund since the purchase was recent.
admin
KeymasterEmail is a required field for each row – if it’s empty, that record will fail to import, and the fields around it won’t get pulled in either.
The mismatch you’re seeing (203 rows counted vs. 197 lines, only 7 email errors vs. ~100 you’d expect) is usually a sign that some rows aren’t being split correctly, most often caused by a comma inside a field (like an address or company name) that isn’t wrapped in quotes. That will shift or merge rows, which throws off both the row count and which rows get flagged for errors.
To narrow it down: take just 5-10 rows from your file (including a couple you know are missing emails) and try importing that smaller batch. That’ll make it much easier to spot exactly which row is misaligned. Also open the CSV in a plain text editor rather than Excel, since Excel will hide quoting/comma issues that a text editor shows plainly.
April 10, 2026 at 6:10 pm in reply to: WP Affiliate : Remove field from the registration form #85236admin
KeymasterTry adding the following CSS tweak to target and hide the state field:
input[name="astate"] { display: none; }To customize the text message displayed at the top, you can use the technique described here:
How to customize various text/messages displayed by the plugin
admin
KeymasterPayment gateways (such as PayPal or Stripe) do not support $0 transactions. For this reason, it’s not recommended to set a product price to $0 if you intend to process it through a payment gateway. Instead, you can set a small minimum amount (for example, $1) and treat that as the minimum donation value.
If you want to offer the item for free, using a squeeze form is a good approach. The following post explains the available options in more detail:
A practical setup would be to include both options on the same page—use a squeeze form for users who prefer not to make a donation, and provide a donation-based product for those who are willing to contribute.
March 9, 2026 at 5:41 pm in reply to: How can I display a product with only Add To Cart Button and Price,? #85226admin
KeymasterThe [wp_eStore_add_to_cart id=1] shortcode is the way to go, but you will need to enter any details you want to display (for example, the price) directly in the editor.
For example, you can enter the following in your page editor to test it out:
Price: $16.00
[wp_eStore_add_to_cart id=1]You can format the price text using the standard WordPress block editor.
If you use a product display shortcode that automatically shows certain product details, it may not be suitable for cases where you want full control of the layout. The idea with this shortcode is that you add any text, images, or other content you want on the page to create the display layout, and the shortcode simply generates the “Add to Cart” button.
March 7, 2026 at 5:16 pm in reply to: How can I display a product with only Add To Cart Button and Price,? #85224admin
KeymasterThe following standard shortcode can be used to display only the Add to Cart button without any additional HTML. This allows you to place any content you like above or below the button and format the surrounding elements however you prefer:
[wp_eStore_add_to_cart id=1]
If you are using one of the fancy product display templates, the product name can be hidden with a small CSS tweak. If you can send me a link to the page where the product is displayed, I can inspect it in my browser and suggest the exact CSS needed to hide the product name.
You may want to try one of the existing stylish product display templates that is closer to what you are looking for, and then hide specific sections with CSS if needed:
September 22, 2025 at 6:58 pm in reply to: Payment Gateway Bundle Stripe Checkout SCA:Shipping Address For Just 4 Countries #85199admin
KeymasterJust adding the soluition to this forum post also.
Stripe requires that you specify a list of countries where shipping will be allowed at checkout:
Our plugin provides a filter hook that lets you override the default list and define the countries you want to allow.
You can add the following custom code to your theme’s functions.php file or to a custom plugin:
function my_allowed_countries_list( $allowed_countries ){ //TODO - Add two-letter ISO country codes separated by comma. $allowed_countries = array( 'US', 'CA', 'GB', 'AU' ); return $allowed_countries; } add_filter('wppg_stripe_shipping_allowed_countries', 'my_allowed_countries_list');This will replace the default allowed country list with the one you specify.
July 26, 2025 at 7:11 pm in reply to: Payment Gateway Bundle Stripe Checkout SCA post-payment error #85180admin
KeymasterPlease share a link to the page where the “Add to Cart” or “Buy Now” button is located. I need to inspect the page to check if any caching issue might be affecting it.
Also, please send a screenshot of the “Developers” menu from your Stripe account. I need to verify the API version currently set. You can reply to the email we sent and share the screenshot privately.
Next, reset the debug log files for both the WP eStore plugin and the Payment Gateway Bundle addon. After that, perform a test transaction and share the updated debug log files from both plugins. This will give me a complete overview of what’s happening. Feel free to send the logs via email as well.
July 22, 2025 at 7:37 pm in reply to: Payment Gateway Bundle Stripe Checkout SCA post-payment error #85177admin
KeymasterHi, I’ve replied to your email but just in case it ended up in your spam folder, I’m copying the message here as well.
——–
Looks like your server’s firewall or security rule is blocking the post payment redirection after Stripe checkout via our plugin.Please contact your hosting provider and ask them to temporarily disable ModSecurity for your domain, or whitelist the specific rule that is being triggered during the Stripe checkout.
You can send them this message:
“We are encountering a Not Acceptable! error from ModSecurity when attempting to complete a Stripe checkout using the WP Payment Gateway Bundle addon. Can you please review your ModSecurity logs and either disable ModSecurity for this domain or whitelist the rule being triggered? The request is being blocked incorrectly by ModSecurity.”
-
AuthorPosts