protect phone number with shortcode

Hello @stonecutter,

Can you use a plan text widget from Elementor for testing? And then do you see the mail address in the source code?

Hello @stonecutter

in inspector you will see what the browser shows. To check the encoding, use “view source code”:

<h2 class="title"><span class="lead">VOICEMAIL</span> <span>TXT MSG</span></h2>
	   <span class="subtext"><h1><span id="eeb-575172-400693"></span><script type="text/javascript">(function(){var ml="05-28",mi="414240020434",o="";for(var j=0,l=mi.length;j<l;j++){o+=ml.charAt(mi.charCodeAt(j)-48);}document.getElementById("eeb-575172-400693").innerHTML = decodeURIComponent(o);}());</script><noscript>*protected email*</noscript></h1></span>

This is the encoded Headline, works fine!

<div class="elementor-element elementor-element-8761a13 elementor-widget elementor-widget-text-editor" data-id="8761a13" data-element_type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
							<h1><span id="eeb-81562-752026"></span><script type="text/javascript">(function(){var ml="2-085",mi="343132212303",o="";for(var j=0,l=mi.length;j<l;j++){o+=ml.charAt(mi.charCodeAt(j)-48);}document.getElementById("eeb-81562-752026").innerHTML = decodeURIComponent(o);}());</script><noscript>*protected email*</noscript><i class="eeb-encoded dashicons-before dashicons-lock" title="Email encoded successfully!"></i></h1>						</div>
				</div>
					</div>

And this is in the footer while is also shown the green lock.

All works like expected 🙂

If you like to make the phone number encoded and clickable, please look at the other newest treads in the support forum were I’ve just reposted to others.

Cheers!

Hello @stonecutter !

I can see that the encoder is working correctly.
In the source code (view source) everything looks coded as it should:

And of course you can see the phone number in plain text in the ‘Inspect’ developer view, as this is what the browser provides – which is also correct, as this is the ‘human mode’. You can also see that the encoder is working correctly here, because the fall-back (script is blocked) ‘protected email’ is displayed.

I am a bit perplexed by your message, google has captured the phone number and ‘protected email’!
Are you sure that this is from the current release or was it possibly entered at a time when you had the phone number in plain text by trial and error and the encoder was also running?

I have never encountered such a situation (with >30 websites). I also have blog posts where the encoder is used manually. There may be a risk in the excerpt that the shortcode gets into the feed or the excerpt and is not resolved there – i.e. the instruction ‘[eeb_protect_content] …’ would be visible in the excerpt!
However, this cannot be the case with your footer integration.

Try to acquire a new indexing by google, whether the mentioned circumstance remains or is ‘overwritten’, which I consider to be plausible.