Not encode en events from The Events Calendar

Hi @wp-henne – thank you for your message!
Can you please tell me how I can reproduce the issue?
I will then check more detailed on the issue and update you accordingly.

Regarding the other thread: We completely refactored the plugin with version 2.0.0, so I’m certain the issue might be a different one this time.
Can you also tell me the version that you currently use?
Thank you already a lot.

Hello Ironikus,

I’m using Version 2.0.6.
The issue may be exist because the email-field at The Events Calendar is formated by html:

	<?php if ( ! empty( $email ) ) : ?>
		<p class="tribe-block__organizer__email"><?php echo esc_html( $email ); ?></p>
	<?php endif; ?>

I’m not very familiar with php, but tif checked the code and now its more clear:

They use own script to encode, in create-organizer-fields.php
‘The e-mail address will be obfuscated on this site to avoid it getting harvested by spammers.’

This gives something like ` <dd class=”tribe-organizer-email”>
hola@7okpno.es </dd>` at source of the page.
May You will look at the code there. I’ve asked the Author of The Events Calendar, so may be there will be a solution to provide using different options to encode outside of The Events Calendar while using plugins like Yours!

THX
Henry

Hey @wp-henne – thank you for the details.
Unfortunately, I couldn’t reproduce the issue from my end, but I was able to check on their encoding methods within the plugin.
I created an integration for the plugin to deactivate their simple protection so that our plugin can recognize the email as an email again.

I created a beta-version for you, which you can download with the following link: https://www.dropbox.com/s/0tfuu7whpbie6mu/email-encoder-bundle-wp-henne.zip?dl=1

Please try this one and let me know if it solves your issue.
If it does, I’m happy to push this fix for the next version.

Thank you already a lot for your feedback.

Hello Ironikus,

WOW!

I am happy about Your quick answer and the beta version. I gladly confirm that the coding works as expected:

In the source code now I can see the encoding of Your script.

Because the mail address is not clickable by the plugin, I have enabled this in the settings of EMail Encoder and it works, great!

For the new release You should consider if the default setting “convert plan mail address” to clickable address has two option details:
– one valid only for the plugins predefined in the loader.php (list them if necessary, so that anybody can assign them)
– the previous “global” setting without those plugins.

Background of the idea of splitting:
For instance in the imprint it’s not necessarily to have the address clickable, but in the calendar detail this would be fine. A touch of luxury, but again “only” some code, maybe.

Thanks a lot for your amazing support!
Henry

Hey @wp-henne – thank you for your feedback, happy to hear it solved your issue.
This said, you can continue using the beta version – as soon as the next version is launched, you can simply update and it will continue to work.

Regarding your suggestion: I like the idea behind it, but I assume the use-case is too specific to make a separate setting for it.
However, it can be accomplished by creating a simple plugin file with which you can filter against the custom integration and validate it only based on your needs.

Here is some code you could use to achieve that:

add_filter( 'eeb/integrations/the_events_calendar', 'deactivete_email_encoder_the_advent_calendar', 10, 1 );
function deactivete_email_encoder_the_advent_calendar( $load ){

    //Include all of the post id's you want to filter with the advent calendar plugin instead of email encoder
    $deactivate_sub_validation = array(
        123,
        6234,
        1234
    );

    $post_id = get_the_ID();
    if( in_array( $deactivate_sub_validation, $post_id ) ){
        $load = false;
    }

    return $load;
}

Please note that it is important to use this filter as a separate plugin and not within the functions.php file of your theme since otherwise, it doesn’t trigger the filter itself.
If you have further questions, feel free to let me know. ??