Hey @alextegelid – thanks a lot for your message and the details to your issue!
I created a pre-beta version for you that fixes this issue as well. Feel free to download it here: https://www.dropbox.com/s/e1arfkcxjzpqy28/email-encoder-bundle-alextegelid.zip?dl=1
After the next update comes available, you can simply update again and the fix continues to work. 🙂
Please let me know in case you face further issues.
Thank you for the fast response and the pre-beta version. Unfortunately it didn’t solve the problem. I’ve been debugging a little and if my guess is correct the method filter_soft_attributes inside Email_Encoder_Validate should filter some emails with a lighter encryption (inside the placeholder attribute for example) before the heavy javascript based encryption is applied?
I had a look at the $content variable inside that method and it never contains the source code where my placeholder attribute appears. It seems to only contain a chunk of the source code.
Bear in mind that I might be completely wrong in my assumption.
Hey @alextegelid – Thanks for the further debugging!
It’s very much possible that you are right with that. The filter_soft_attributes method takes exactly care of that and it is also pretty accurate.
The only reason I can think of that there is currently no encoding happening:
The code is not loaded at that point. Is it possible that this piece of code is maybe loaded via Ajax or another third party plugin?
You can try that by including the input field directly within the content (There it should work as expected).
If it does work there, you might want to use the [eeb_protect_content] shortcode.
If this also doesn’t help, feel free to reach out again – We will definitely find a solution for that. 🙂
I’ve been busy the last couple of weeks and haven’t had a chance to try out your tips. You seem to have solved it nicely in release 2.0.3. Thanks for that!
