emiubaldi

Hello @muddasirhayat,
I’m very sorry for the confusion. Unfortunately, I haven’t received any email from you at emiuba***@******.com — I’ve checked thoroughly, including my spam/junk folder, and there’s nothing there.

Would you mind sending it instead to pilot29it [at] gmail [dot] com?

Thank you very much, and sorry again for the inconvenience.

• This reply was modified 1 month ago by emiubaldi.

Hi @muddasirhayat,
I’d like to follow up on this issue, especially after the release of the latest version, email-templates 1.5.7. As you advised three weeks ago, I opened a support ticket using the link you provided, but I never received any response. Even with the new update, the issue persists.

As before, I’ve replaced the public function send_email( $args ) in the class-mailtpl-mailer.php file with the fixed version below.

/**
		 * Send Email to All the SMTP Plugins
		 *
		 * @param array $args Expected args.
		 *
		 * @since 1.0.0
		 */
		public function send_email( $args ) {

			do_action( 'mailtpl_send_email', $args, $this );

				/* ============================================================
				PATCH — Prevent double HTML wrapper for Elementor emails
				============================================================ */

				// Detect messages that already contain full HTML structure
				$has_full_html = (
					strpos($args['message'], '<html') !== false &&
					strpos($args['message'], '<body') !== false
				);

				if ( $has_full_html ) {

					// Elementor already generated a complete HTML email.
					// DO NOT apply Email Templates wrapper.
					// But DO apply placeholder replacement for consistency.

					$user_email = isset($args['to']) ? $args['to'] : get_option('admin_email');

					$args['message'] = $this->replace_placeholders(
						$args['message'],
						$user_email
					);

					return $args;
				}

				/* ============================================================
				NORMAL BEHAVIOR — Email Templates wraps plain WP emails
				============================================================ */

				$temp_message = $this->add_template(
					apply_filters('mailtpl_email_content', $args['message'])
				);

				$user_email   = isset($args['to']) ? $args['to'] : get_option('admin_email');

				$args['message'] = $this->replace_placeholders(
					$temp_message,
					$user_email
				);

				return $args;
			}

Could you please follow up internally with your team and let me know the status?
I’m also wondering why no one has replied to the ticket I submitted.

Thank you in advance, and Happy New Year.

Hello @muddasirhayat,
Thank you for sharing the updated link.

Unfortunately, after testing, the issue is still not resolved on my end. I’ve attached the mailer I received after updating the pluign with the zip file you shared and submitting the contact form.

Click here to view the screen capture

Please let me know if you’d like me to run any additional tests.
Thanks,
Emiliano

• This reply was modified 2 months, 1 week ago by emiubaldi.

Hi @rafkwa,

Thank you for your message. I’ve already submitted an email through the online support form on the page you shared. The account may be registered under a different name—I’m not entirely sure—but I can provide any necessary details if needed.

Please let me know what information you require, and I’ll send it right away.

Best regards,
Emiliano

Thanks, @haseeb0001! It is not a must, but it is a plus! Have a great Holiday season everyone.

Hello, @haseeb0001!

I confirm that the newly released version 1.4.1 is working well now on multi-site and single-site WP installations.

Thank you and your team for resolving this glitch.

Just a small note if I can: I would have liked to see a link to the Email Editor directly on the WP left column, as I can see it only on the multi-site.

Click here to see a screen capture.

If I’m correct, the link to the Email Editor appears only on the plugin list page for a single-side WP installation. Can someone confirm this?

Click here to see a screen capture.

Thanks!

Hi @patrick_d1985!

The developer’s approach while updating the plugin could have been better engineered.

We cannot consider the v.1.4 version an update from v.1.3.2.1. It is a completely new dedicated plugin targeting WooCommerce users.

It would have been better to keep v.1.3.2.1 as it was while informing WooCommerce users to download the new version 1.4.

Merging the two engines was probably not the best decision for the developer.

Of course, this is my opinion without knowing the reason behind this release!

Thanks!