authentictech

Hi @hchouhan

Thanks for testing it.

The other email addresses I tried yesterday were actually added after a while.

The first one which I tried to add last week never was added even though I have never used it before on this list or even on Mailchimp.

Although the plugin works with the 3 other addresses I tried, do you have any idea from your experience why one email address – never used before with Mailchimp – isn’t added to Mailchimp via the plugin even though the plugin says it was added successfully? I am still concerned that some subscribers might find their addresses are not also added.

I noted this in your FAQ:

If you use the same email to test one or multiple forms in a short amount of time Mailchimp might temporarily block your email from signing up to any Mailchimp list.
Trying another (fresh) email address often solves this issue

…but the first email address is still not being added now a week later.

Thanks for your help.

@xootix Thanks for the reply.

I’m using Elementor Pro page builder with the Cart widget on the same page as the product rather than a separate page so there’s a slightly different flow to the default WooCommerce flow but the same thing happens if I am on the actual Woocommerce cart page.

SideCart picks up when items are added to the cart but not when they are removed. The cart item is removed from SideCart after reloading the page.

There are no console errors.

Here’s a screen recording showing the process: https://youtu.be/3Qzj7U8lEoE

Thanks again.

Thanks so much for that @xootix it’s really appreciated.

Hi @abidhasan112

I really appreciate you taking the time to show me how this can be done.

Thanks. ??

Thanks @algolplus

Thank you. And from my perspective a quick response for which I am extra grateful.

@crazycharlie I’m using Make theme and Site Origin plugin but had a similar problem today.

I had a similar problem today with a white screen of death after updating my plugins. I did not update Wordfence which was already up-to-date but disabling Wordfence did stop the problem of the white screen of death.

I restored my site and DB from a pre-update backup and updated each plugin individually to see if one of them was causing the problem. This time there were no problems after all the plugins were updated.

The only other things I did differently before updating were I went to the Wordfence settings screen and accepted the new terms and conditions (didn’t do that before) and I purged all caches using W3 Total Cache.

@jricketts4 Thanks.

The use case is for a take away store where products are collected or delivered. There is no delivery/shipping charge as delivery is handled by shop employees, not a shipping service, and delivery is free.

Thanks Bernhard.

BTW I appreciate the dedication you have to supporting your plugin. Thanks for that. I’ll definitely come back to use it when the requirements match up.

@amandasjackson Thanks for investigating it.

I still experience this issue when I have disabled all plugins except WooCommerce and switch to Storefront – as seen in this video:

If you have any ideas, please let me know. Thanks.

I know, but that wasn’t my point.

@stefaniehoedlmoser

Here is my temporary fix in CSS if you need it:

div.eael-table-align-left div.td-content,
div.eael-dt-th-align-left div.td-content,
div.eael-dt-td-align-left div.td-content
{
	justify-content: start;
}

div.eael-table-align-right div.td-content,
div.eael-dt-th-align-right div.td-content,
div.eael-dt-td-align-right div.td-content
{
	justify-content: end;
}

div.eael-table-align-center div.td-content,
div.eael-dt-th-align-center div.td-content,
div.eael-dt-td-align-center div.td-content
{
	justify-content: center;
}

There isn’t a problem now without doing anything to fix it. I can see the success message after a couple of seconds. So I’ll leave things as they are for now.

We use the WP Mail SMTP plugin but that has always worked well. I got the emails fairly quickly even though there was no success message.

Thanks for your help.

Hello @shamser_suzon

My website is not on a public URL but it’s exactly the same issue as described in my original post with screenshots of the broken code. It was fixed as noted by @rafinkhan but lately this part of the code was reverted to the old state. Perhaps @rafinkhan can point out what was done before to fix it.

Thanks.