Plugin Support
Julian
(@juliangk)
Hello @twiginteractive,
I am not sure if I understand your issue completely. Can you please explain in more detail what is happening?
Thank you and best regards
Julian
Thread Starter
Twig
(@twiginteractive)
Hi –
There isn’t a ‘problem’ exactly, I just noticed that your HTML generation is missing one of the tokens getting replaced in the output. If you enable the plugin on a clean WP install, and send a test email – then View Source, you’ll see the first <table> tag has a class attribute ##plugin-class## – which obviously isn’t intentional. Presumably it should have replaced this token with some class like ‘wp-html-email’ or whatever.
I put up a sample text email code here you can verify.
https://www.twiginteractive.com/TEMP/example-html-test-email.html
Plugin Support
Julian
(@juliangk)
Hi @twiginteractive,
I see what you mean now. Thank you for bringing this to our attention, I will check it out.
Did you by any chance also test sending proper e-mails and see the same placeholder?
Best regards
Julian
Thread Starter
Twig
(@twiginteractive)
I did, and it also has the same placeholder in it (I tested with a Password Reset system email)
Plugin Support
Julian
(@juliangk)
Hi @twiginteractive,
thank you again for pointing this out. The ###plugin-class### placeholder is intended only for certain sender plugins that integrate with WP HTML Mail. If such a plugin is detected, the class gets replaced with the appropriate value. If not, the placeholder simply remains in place.
This doesn’t affect how your emails look or work — it’s only a CSS class marker — so it isn’t an error in functionality. We could replace it with an empty string, but since it has no impact beyond the source code, we don’t currently plan to adjust it.
We really appreciate your careful eye in spotting details like this!
Best regards,
Julian
