Ironikus
Forum Replies Created
-
Hey @knodderdachs – Thanks for bringing this to our attention. I will make sure we fix that within our next release. 🙂
Hey @wp-henne – Thank you for reaching out.
With our latest release. we’ve introduced further security measurements to limit the possibility of harmful code via shortcodes through the contributor roles. Because of that, we started filtering the HTML within shortcodes to only allow certain HTML tags.
After looking through the code, the validation is applied after the shortcodes have been resolved to its actual content.
However, after looking further into it, I believe that we can start applying the validation before the shortcodes have been rendered, as we should expect each plugin to sanitize it’s own shortcodes respectively.
I will make sure that within our next release, we will apply our HTML sanitizations before the shortcodes ran to avoid checking HTML that doesn’t need to be validated by us.
Hey! This will be fixed in version 2.2.1 🙂
Forum: Plugins
In reply to: [Email Encoder - Protect Email Addresses and Phone Numbers] PHP 8.2 error?Hey! This will be fixed in version 2.2.1 🙂
Hey @kiway, Thanks for reaching out.
You probably face this error as you haven’t enabled the GD Library on your server.
I suggest installing it if you want to use this feature.
Furthermore, I will make sure we do an additional availability check within our upcoming version.Hey @ngvtech, Thanks for reaching out.
Can you please share some further details on the configuration of our plugin on your site?
Hey @ballou – good point – the shortcode currently only supports the direct email for validation purposes.
If you want to add additional parameters to an email, you can use the
[eeb_protect_content]
shortcode instead.Hey @michalzwierz – Thanks for reaching out!
I’ve just released a new version that offers a WordPress filter that you can use to prevent certain pages from being protected:
apply_filters( 'eeb/frontend/apply_protection', $apply_protection )
Here’s a callback as an example:
function eeb_frontend_apply_protection_callback($apply_protection) { if (is_checkout() && is_woocommerce()) { // Add your custom logic here to apply protection on the WooCommerce checkout page // Example: $apply_protection = true; // Enable protection // Example: $apply_protection = false; // Disable protection } return $apply_protection; } add_filter('eeb/frontend/apply_protection', 'eeb_frontend_apply_protection_callback');
Hey @shorrog99 – Thanks for reaching out! The website error has been fixed. As for the 6.4.2 support: Yes, our latest version (2.2.0) supports 6.4.2 as well.
Thanks, and feel free to let me know in case you have any questions.
Hey @robwent, I’ve just added a new advanced setting called “Exclude URL parameters from protection” – You can use it to exclude pages with certain query parameters from being encoded.
In your specific case, you can simply add
wpml-app
to the input field.If you want to add multiple ones, you can do so by comma-separating them.
This feature is available in version 2.2.0
Hey @tbauerdigital – I’ve implemented additional logic to optimize the enqueue of our scripts and styles. It’s going to be available with version 2.2.0
Forum: Plugins
In reply to: [Email Encoder - Protect Email Addresses and Phone Numbers] Deprecated PHPHey @dav74 – I can’t bother if I never read it. 🙂
Do those errors still occur? I’ve tried it with different 8.1+ versions but couldn’t reproduce many issues. I’ll ship some improvements soon for PHP 8.x.
Feel free to share some further details about it.
Hey @xtiborius – Thanks for reaching out!
The eeb_protect_content returns an obfuscated HTML snippet containing the hidden phone number. By default, it uses the rot13 (Javascript) obfuscation method. To display it within an actual ahref link as an entity, you need to parse it using a method that doesn’t add any HTML tags. You can use the following:
eeb_protect_content( ‘+12 345 678’, ‘encode’ )
Hope that helps!
Hey @ffwebdesigner – Thanks for sharing this. Did you manage to look into the debug.log file of your WordPress website? There you should find more details about the error, which helps me to look into it further.
Thanks!
Hey @sunrises, Thanks for reaching out! You can execute shortcodes by setting the do_shortcode argument within the shortcode itself: Here’s a full example:
[eeb_protect_content protection_text=”I am a noscript text” method=”rot13″ do_shortcode=”yes”]My Email[/eeb_protect_content