Ivan

Hi @asaconover

Thank you for bringing this to our attention.

We’ve been doing internal work to improve the codebase and strengthen validation and type handling, and a release candidate is now available that should address the issue you reported.

It’s great that you’re testing this on a development environment first 🙂 Could you please visit the following link, download email-encoder-bundle-2.4.3-rc1.zip, and install it manually to verify whether the issue is resolved?

https://github.com/Online-Optimisation/email-encoder-bundle/releases/tag/v2.4.3

If this works as expected, we’ll proceed with preparing the official update after completing a few additional checks.

Hi @tkendrickweb and @stephenturner

Thanks for bringing this up. I wasn’t able to reproduce the exact issue you’re experiencing, but I did spot a bug that could occur under certain circumstances. I’ve addressed it in the latest update (version 2.4.2), and I’m hoping this resolves the problem for you.

If the issue persists, it would be really helpful if you could share a screenshot or any additional details that might give me more insight into what’s happening.

@tkendrickweb – I’m unable to view the page you linked to; it appears to be a DNS resolution issue on my end. Could you please double-check the link or provide the details another way?

Hi @bogdanguenther

Thanks for posting this, but the analysis doesn’t really help me diagnose the issue.

The error is coming from a legacy part of the code where a lot of things were initialised in the constructor. That was fine at the time, but it’s not how the plugin is meant to be used in its current, more modern structure, mainly for reliability, performance and security reasons.

What this error is actually doing is exposing a bug that occurs when something is used in a way I didn’t anticipate. To fix it properly, I need to understand the context in which it happens. The real problem is most likely somewhere else, not at the point where the error shows up.

Can you tell me how you’re using the plugin? For example, are you using shortcodes, calling its functions directly from template files, or something else?

If you can also share your plugin settings, I should be able to reproduce the issue and implement a proper fix.

Hi @leanderbraunschweig

That’s a totally fair point, and I agree with you!
I was (perhaps a bit too much) following the “best practice” you often see from big players, where changes get bundled under vague labels like “bug fixes”, “security update”, or “various improvements”.

What we’ve been doing recently is modernising the codebase while keeping all existing functionality intact. The plugin has been around for quite a while, and over the years it’s lived through multiple PHP and WordPress versions, along with coding standards and best practices that made sense at the time. Untangling that isn’t trivial.

A lot of the recent “bug fixes” are actually part of this cleanup work: improving structure, testability, reliability, removing dead code, and addressing issues we uncovered along the way – some of which were genuine bugs. It’s very much a work in progress, but the goal is to move away from just carrying legacy code forward and instead properly clean things up before building further.

I’ll definitely be more explicit in the changelog going forward. Thanks for calling it out 🙂

• This reply was modified 3 months, 2 weeks ago by Ivan.

Hi @imrelaszlo

Thank you for bringing this up, it’s much appreciated.

It’s fixed in latest 2.3.9 update.

Hi @solserpiente

Thank you for bringing this to my attention.

The plugin recently went through a major structural overhaul, and unfortunately a few bugs slipped in as a result. The RSS issue has now been fixed, and an update is available in version 2.3.8.

Sorry for the inconvenience, and thank you for your patience and for helping improve the plugin. It’s much appreciated.

Hi @kev58699

Thanks for reporting this, and sorry for the fatal error you ran into.

I’ve been cleaning up some internal structure in the plugin, and one of those changes caused the issue. It’s fixed now and included in the latest release.

Appreciate you flagging it, and sorry for the inconvenience.

If you notice anything else odd, or if something still doesn’t behave as expected in your setup, please don’t hesitate to let me know – your feedback genuinely helps make the plugin more robust for everyone.