boca jo

Yes, thanks. Shortcode also works instead of the block because it employs cart.php, but the layout of the cart is quite different with the shortcode.

Bummer. I’m surprised it’s not possible to customize the blocks. It seems like they’re not quite ready for release, yet here they are and they’re the default configuration for new installs like mine.

Thanks @serafinnyc.

I’ve confirmed that the latest release of the plugin resolves my issue. Thank you.

Old question, but I’m adding my answer in case someone searches for it. In the free version of the plugin, try adding this to your CSS to remove “From: $0” in your product lists:
li.cpw-product .price {
visibility: hidden;
}

Hi again. I updated my site a bit since my reply 5 days ago. The issue still exists as described above, however the main shop page which does not have a problem has moved to
https://worldleadgifts.com/gifts/

The page exhibiting the problem is still
https://worldleadgifts.com/all/

Thank you for looking into this issue, @dominikl65. The problem does not occur when the plugin is disabled. It only occurs for products that have custom prices.

My site is under development, but I disabled basic authentication site protection temporarily so you can view the pages in question. On the following pages, please look at the first product, Where Needed Most.

Page where the where the problem occurs – it’s a regular WordPress page that includes the WooCommerce All Products block to display the product grid:
https://worldleadgifts.com/all/

Main shop page, which does not have the problem:
https://worldleadgifts.com

Once you’ve had a chance to look at these pages and/or replicate the issue on your own site, kindly let me know so I may re-enable authentication for my site.

• This reply was modified 5 months, 3 weeks ago by boca jo.

Thank you, kc1024. Updating to WordPress 6.2.2 indeed fixed the problem.

@treibalen I just submitted the contact. Thank you.

@treibalen I apologize for missing the notification for @damielinhou’s reply. Yes, I have already tried the steps suggested in the tutorial at https://kb.mailpoet.com/article/233-error-could-not-instantiate-mail-function-on-1and1-servers (except using for SiteGround’s maximum sending rate, which is our host).

This issue remains unresolved. Thank you for any suggested next steps.

I want to do this too. It’s so frustrating that MailPoet doesn’t support it.

@sudiptomahmud That is item (1) in my list that I have already tried. Result was “Could not instantiate mail function.”

Thanks, Steven! That worked well. I also needed to scrub the last name from the page source, in particular the alt and title attributes of the img tags as well as the folder name for the individual’s images. The filters cn_photo_alt, cn_photo_title, and cn_entry_slug did the trick. Thank you for providing them!

Jo

• This reply was modified 3 years, 5 months ago by boca jo.

By looking at my site backups, I can see that 70 old .json files that had previously been in wp-content/uploads/smtp-mailing-queue/invalid were for some reason moved to wp-content/uploads/smtp-mailing-queue at exactly midnight GMT on July 8. I have no idea why SMTP Mailing Queue may have done this, nor what steps to take to prevent it in the future.

Thanks, Jake. I wouldn’t mind showing the submission time, but unfortunately {entry:date_created} is in UTC. In the end, I made a clumsy workaround by adding a hidden date field to the form that defaults to {date_mdy}.

By the way, I really love this plugin.

It has never been addressed. I recently had 2.7.11.3 on a site and it was worse than ugly: some recipents’ providers like Outlook online were flagging the malformed mail as spam. As soon as I reverted to 2.7.6, the spam problem resolved.

I hated to revert because a back-level MailPoet plugin got me in trouble a few years ago when they had a security hole. One of my sites got hacked because it was back level.

Seriously considering MailChimp.