muddasirhayat

Hi @joprestonom4,

We’re pleased to inform you that the official release containing the reported fix has now been published on the WordPress repository.

Please update the plugin to the latest version directly from your WordPress dashboard and test it in your environment. Once you have had a chance to verify the update, please let us know whether the issue has been resolved.

Your feedback is greatly appreciated and helps us ensure the fix is working as expected for all users.

Thank you for your patience and support.

Thanks & regards,
WPExperts Support Team

Hi @egocefalo,

We’re pleased to inform you that the official release containing the reported fix has now been published on the WordPress repository.

Please update the plugin to the latest version directly from your WordPress dashboard and test it in your environment. Once you have had a chance to verify the update, please let us know whether the issue has been resolved.

Your feedback is greatly appreciated and helps us ensure the fix is working as expected for all users.

Thank you for your patience and support.

Thanks & regards,
WPExperts Support Team

Hi @tomangell,

Thank you for your patience throughout this process.

We’re pleased to let you know that the official release containing the fix has now been published through the WordPress repository.

Please update the plugin to the latest version directly from your WordPress dashboard and test it in your environment. We would appreciate it if you could let us know whether the issue has been resolved on your site after updating.

Your feedback will help us confirm that the fix is working as expected across all affected environments.

Thank you again for your cooperation and support.

Thanks & regards,
WPExperts Support Team

Hi @tomangell,

Thank you for your feedback and for sharing your concerns.

We completely understand your preference to install updates through the official WordPress repository rather than testing a separately provided build.

The reason we shared the build was to validate the fix in the environments where the issue was originally reported before proceeding with a public release. However, we respect your decision and appreciate your perspective.

Our development team is continuing to review the fix and the reported behavior. Once the validation process is completed, we will proceed accordingly and provide updates here on the forum.

Thank you for your patience and feedback throughout the investigation.

Thanks & regards,
WPExperts Support Team

Hi @egocefalo,

Thank you for your time and patience.

We’re pleased to let you know that the reported issue has been fixed. Our team has prepared an updated build for your testing. This is not a beta version; it is a production-ready build. Once you have tested it and confirmed that everything is working correctly, we will proceed with releasing it to all users.

We have also prepared a guide that explains the required steps. The instructions are provided both in the video and in a text format.

To permanently resolve the issue, please update the plugin using the latest build provided below. After updating the plugin, open the Classic Editor block and update the snippet by removing the old rendering and then re-entering it, as demonstrated in our guide.

Updated plugin:
https://drive.google.com/file/d/1Bj9A1D7oMysu_rgXDsuf70DxO6VbAHQB/view?usp=sharing

Guide video:
https://www.awesomescreenshot.com/video/53284457?key=72e7cbd5098c978b79ef606644b7d6c7

We look forward to hearing your feedback.

Thank you.

Hi @guenni,

Thank you for your time and patience.

We’re pleased to let you know that the reported issue has been fixed. Our team has prepared an updated build for your testing. This is not a beta version; it is a production-ready build. Once you have tested it and confirmed that everything is working correctly, we will proceed with releasing it to all users.

We have also prepared a guide that explains the required steps. The instructions are provided both in the video and in a text format.

To permanently resolve the issue, please update the plugin using the latest build provided below. After updating the plugin, open the Classic Editor block and update the snippet by removing the old rendering and then re-entering it, as demonstrated in our guide.

Updated plugin:
https://drive.google.com/file/d/1Bj9A1D7oMysu_rgXDsuf70DxO6VbAHQB/view?usp=sharing

Guide video:
https://www.awesomescreenshot.com/video/53284457?key=72e7cbd5098c978b79ef606644b7d6c7

We look forward to hearing your feedback.

Thank you.

Hi @sflwa,

Thank you for your feedback.

We have prepared a reference screencast using the same plugin build that was shared with you. In our testing environment, we installed the exact plugin version provided in the ZIP file and were unable to reproduce either of the issues you mentioned.

From our testing:

1. The logo image is displaying with the correct width and appearance.
2. The “Send Test Email” option is available and functioning as expected.
3. Since this is a temporary test WordPress site, we are also able to verify the email delivery through the email logs, and the test emails are being generated successfully.

Please review the screencast here:
https://www.awesomescreenshot.com/video/53283906?key=d668d901e9d2ccb09a5f8ba6f3360b43

Could you please confirm whether the plugin version installed on your site is the same build we provided? If possible, please share a screenshot or a short screencast showing the missing “Send Test Email” option and the logo width issue on your setup. This will help us investigate the difference between your environment and our test environment.

We look forward to your update.

Thanks & regards,
WPExperts Support Team

Hi Jory,

Thanks for the detailed investigation — it helped us pinpoint the exact issue.

Root Cause: In class-mailtpl-woomail-composer.php, the on_init() method was calling WC()->mailer() early (hooked on after_setup_theme at priority 80) to remove WooCommerce’s default email header. This forced WooCommerce to instantiate its mailer and lock in all registered email classes before Tribe had a chance to register its ticket email — effectively excluding it from the WooCommerce email flow permanently.

Fix (line ~107, class-mailtpl-woomail-composer.php): We’ve moved that remove_action call to fire lazily at send time (priority 0 on woocommerce_email_header), so it only runs when an email is actually being sent — by which point all plugins including Tribe have fully registered their email classes. This means your custom workaround snippet is no longer needed and can be removed from functions.php.

You can download the updated plugin from this URL: https://drive.google.com/file/d/1dwXMMY4tkPac5QuTnXAte-TsrAjASekl/view?usp=sharing

Please test and let us know.

Thank you