KJ

@tallsam Glad to hear that fixed the issue! If anything else pops up, don’t hesitate to reach back out to us. We appreciate you using the plugin.

If you’re happy with this integration, please consider leaving a 5-star review. Your feedback helps other WooCommerce customers find this integration and helps support future development.

Also, can you please check: https://github.com/mailchimp/mc-woocommerce/wiki/Custom-Merge-Tags#custom-merge-tags closer it’s not only about date. You can insert any merge tags based on the?WP_User?object, and push to?$merge_vars?which is associative array where keys are the merge tags taken from mailchimp.

function custom_user_merge_tags($merge_vars, $user) { $merge_vars['PHONE'] = $user->billing_phone; return $merge_vars; } add_filter('mailchimp_sync_user_mergetags', 'custom_user_merge_tags', 100, 2);

where PHONE is the name of the merge tag in mailchimp. and $user->billing_phone; whatever they want to use as phone.

Try this – and turn on the remote diagnostics – just in case.

I have a feeling it could be a theme conflict. Enable the?Remote Diagnostics?feature found in the plugin’s Settings tab. This allows the Mailchimp for WooCommerce development team to diagnose and fix the issue remotely. Drop your URL so that we could also check it out. In the meantime

• This reply was modified 1 month ago by KJ.

The block method might be the easiest way – But I am unsure what kind of theme you have. Also, do you have admin rights?

Enable the?Remote Diagnostics?feature found in the plugin’s Settings tab. This allows the Mailchimp for WooCommerce development team to diagnose and fix the issue remotely – and I will be able to see your theme type that way but you should be good to go!

If you’re using the WooCommerce Blocks for your checkout page and the “Mailchimp Newsletter!” block appears grayed out or unavailable, ensure that you have the following plugin versions installed:

• WooCommerce Blocks version 8.0.0 or higher.
• Mailchimp for WooCommerce version 2.7 or higher.

These versions are required for compatibility with the new Cart and Checkout block. If the checkbox still doesn’t appear on the checkout page, it may be due to a theme or plugin conflict. To troubleshoot:

• Theme Conflict: Temporarily switch to a default WordPress theme (like Twenty Twenty-One) to see if the checkbox appears. If it does, the issue lies with your theme.
• Plugin Conflict: Deactivate all plugins except WooCommerce and Mailchimp for WooCommerce. If the checkbox appears, reactivate your plugins one by one, testing each time, to identify the conflicting plugin.

Hi @tallsam You can set the newsletter box to be checked by default

On the checkout page you will need to click edit – Check for the ‘Mailchimp Newsletter!’ Block under the WooCommerce/Woo section. On the right hand side of the screen, you should see the option to have that box checked by default

Mailchimp Newsletter! Adds a newsletter subscription checkbox to the checkout.

Let us know how it turns out!

Sure thing – Sorry we couldn’t help you out on this. RE the workaround, you mentioned MC recommended, “to make non-variable products,” not ideal, but an option.

Hi @hastibe as much as we would like to accommodate your request, we do not make decisions RE the Mailchimp.com site. BUT, you can see all of the change logs in our Github

Hi @enfueggo

My apologies – You are right. I reached out to a contact at MC and it is a confirmed bug on the MC side. They have the issue documented and will hopefully deploy a fix soon, but I was not given a date. Perhaps a workaround for now (which you mentioned)?

Awesome!

Glad to hear that fixed the issue! If anything else pops up, don’t hesitate to reach back out to us. We appreciate you using the plugin.

If you’re happy with this integration, please consider leaving a 5-star review. Your feedback helps other WooCommerce customers find this integration and helps support future development

Yea – That is super inconvenient – I would try this method for bulk updates: bulk through the audience dashboard by selecting the contacts and choosing the action to update their status.

And yes to the update, I would of course back up your site first, but this newest version could help.

To translate the “Subscribe to our newsletter”, “Unsubscribe from our newsletter”, and “Receive Order Updates” options from WooCommerce/Account/EditAccount into French, you can follow these steps using the WPML plugin. This approach assumes you have WPML installed and set up on your WordPress site for multilingual support.

Identify the Strings for Translation:

• First, ensure that the strings “Subscribe to our newsletter”, “Unsubscribe from our newsletter”, and “Receive Order Updates” are correctly registered in WPML for translation. These strings might be part of the WooCommerce plugin or a custom addition, depending on your setup.

Use WPML String Translation:

• Navigate to the WPML > String Translation page in your WordPress admin area.
• Use the search function to find each of the strings you want to translate. You might need to select the domain related to WooCommerce or your custom strings to filter the search effectively.

Translate the Strings:

• Once you find the strings, click on translations next to each string.
• Enter the French translation for each string in the text area provided.
• Make sure to check the “Translation is complete” box (or similar confirmation) for each string after you enter the translation.
• Click on the ‘Save’ button to store your translations.

Verify the Translations:

• After saving the translations, visit the WooCommerce/Account/EditAccount page while your site is set to the French language. You should see the translated strings in place of the original English ones.
• If you’re using a cache plugin or service, clear your site’s cache to ensure the changes are reflected immediately.

If you don’t see the strings available for translation in WPML’s String Translation section, you might need to use the “WPML String Translation” plugin to manually add these strings to the database for translation. This can be done by navigating to WPML > Theme and plugins localization and ensuring that the texts from WooCommerce and any related plugins are fully scanned and available for translation.

Remember, the exact steps might slightly vary based on the versions of WooCommerce, WPML, and any other plugins you’re using. If you encounter any issues, I recommend consulting the official WPML documentation or contacting their support for more specific guidance.

Hi there! Sorry we couldn’t help you out – I would say it is safe, as long as you have deleted the plugin. I would back up your database first and then delete, just in case. We are here if you decide to ever give us another chance.

Hi! @diegogomez this link should help! https://github.com/mailchimp/mc-woocommerce/wiki/Custom-Merge-Tags#custom-merge-tags

You could also set them up on the Mailchimp side as well! https://mailchimp.com/help/merge-tags/ – Let us know if this helps!

Hi @marco1970! Thanks again for letting us know! This update is now in our v5.2! Let us know if you still experience the error.

If you’re happy with this integration, please consider leaving a?5-star review. Your feedback helps other WooCommerce customers find this integration and helps support future development.

Hi! @rayjohnson28 hmmm – My first thought is to check if you’re using caching plugins, Cloudflare, or server caching, clear your cache and refresh the checkout page.

Next I would verify your code – Ensure that your code is correctly placed in your theme’s functions.php file or a custom plugin. Then check for theme or plugin conflicts – Switch to a default theme (e.g., Storefront or Twenty Twenty-Three) and check if it appears. Disable all plugins except WooCommerce and test again. If the checkbox appears after disabling a specific plugin, that plugin might be overriding the checkout fields.

Last, you can enable remote diagnostics so that we can check on our end. Enable the?Remote Diagnostics?feature found in the plugin’s Settings tab. This allows the Mailchimp for WooCommerce development team to diagnose and fix the issue remotely. Once you have done that, drop your URL here and we can see what we can find.

Thanks!