M. Ballou

Thanks for your reply @ironikus! I appreciate the explanation.

Follow up question to your suggest on further obfuscating displayed email: How do you insert a SUBJECT line into MAILTO shortcode?

For instance, following your instructions to replace my old MAILTO link, I’m now using something like, [eeb_mailto email=”jondoe@example.com” display=”jondoe(AT)example(DOT)com”]

I tried a variety of ways for the manually protected MAILTO link to insert the SUBJECT line but couldn’t figure it out. I also used the brackets in your example “jondoe [AT] example.com” and that seemed to break things, so I went with parentheses and that appears to work.

Thanks for the reply @ironikus!

Unless I am misunderstanding something, it seems like the way I was Safari searching Source data, it maybe combines Inspector and Source data, thus yielding my results. So that may be why that’s happening. As I mentioned in the other post that led me to this conclusion, I’m still not sure why I got spam to an obfuscated email associated with a button on my page… I know there are many ways to have email compromised, but this is a very new email address, and not a logical one. So either someone manually harvested it, or is using some other scraping method?

Thanks to this thread and @alexanderbailey, I think I’m getting a better understanding of why I’m seeing my obfuscated data when searching Page Source results for Safari in the Developer tools. Here’s a link to my post about it. It seems that the source search feature in Safari combines the source and the inspector data? Because when you actually just read through the source code, without searching, the data I’m concerned is exposed is nowhere to be found. I also copied and pasted the source into a text doc and searched that to be sure, and it also wasn’t found. So that’s good news.

I’m still not sure why I got spam to an obfuscated email associated with a button on my page… I know there are many ways to have email compromised, but this is a very new email address, and not a logical one. So either someone manually harvested it, or is using some other scraping method?

I just got pushed an update today for WP Email Encoder, so it appears to be actively maintained. I am a little bummed about the lack of responses from the developer and concerned about the vulnerabilities that @aztopdavid points out. I’d buy the guy/gal(?) a coffee or even pay, if there appeared to be a developer presence. The site seems nice enough, but no way of contacting them is a drag. Even following that Wordfence report and searching @ironikus didn’t yield any results.

As a follow up, I also looked at the source code for the page in 3 browsers and was surprised to see the only viewable email address on my site was NOT obfuscated in Safari v17.2.1, but WAS in the latest versions of Firefox and Brave (chrome browser). I thought that was the whole point of this plugin? By default shouldn’t it at minimum protect a visible MAILTO link? Alternately, I tried to manually protect the email with [eeb_protect_emails], and got the same results.

In addition the manually protected phone number that shows on my site doesn’t appear to be protected in Safari when viewing the source code, but does not show in search results of the source code in Firefox and Brave. I used the [eeb_protect_content] for that. For what it’s worth, I cleared the cache for my domain on each browser with each test.

Again, I know enough to get myself in trouble, so maybe I’m misunderstanding how this tool works, or how to check it looking at source code. In Safari I went to Develop>Show Page Source, in Firefox I use Tools>Broswer Tools>Page Source, and in Brave View>Developer>View Source. Assuming I’m using it correctly, as it stands, I can’t recommend it and am going to have start looking for other options. ??

I see an update for the tool was JUST released today, so it seems like it’s actively being developed. Hope you can shed some light!

Resolved for me too! Thanks.

I too have this issue. Started after latest updates to your plugin. I have one Custom icon in addition to 3 of the “Strongly Recommended” icons. My custom icon which was a Tumblr link that I created (which has worked for years w/ this plugin) no longer shows up. Though it is selected and set in the settings of you plugin.

Site: blog.markballou.com

Tried multiple browsers and cleared cache. No joy.

Of note, I was also having the PHP errors in Admin, but that appears resolved with the last update.

Will the new version enable error reporting by default, or do we need to turn that back on once the update goes through?

Me too. Anxious for a fix ASAP. Thank you!

The instructions from Jetpack resolved the issue.

I’ve reached out to Jetpack. Will let you know how they respond.

I also have this question. Hope it’s not rude to jump in, but figure it might be helpful for folks to consolidate similar questions. Don’t mean to hijack, but think this relevant.

When managing multiple sites on the same domain (root and subs), is it better to do separate installs of WP, or go Multisite?

I have a root domain (www.mydomain.com) with an old flash site hosted there. I also have a subdomain (blog.mydomain.com), where I’ve been experimenting using WP building a blog. Now that I’m getting more comfortable with WP (enough to really get myself in trouble!), I’m thinking of switching the root domain’s design over to WP. Is Multisite the answer for me?

From what I understand, I could install WP on my root domain and build the root domain’s site independently (giving me 2 installs of WP, one for the root and another for the subdomain), or I could do a Multisite install on my root and handle however many sites (based on the root name) I have in one place with one install. Is this correct? Pros? Cons?

As you say, DennisBarkerCV, I just want “to keep things simple.” In this particular case, with the two sites I’m thinking of, each would have a different theme/design.

If I were to go with a multisite, would it be difficult to migrate my blog.mydomain.com over to the root (mydomain.com) multisite install?

As a side question, while keeping my root domain’s current site running, would it be prudent to build the replacement WP site in another subdomain? Or is there a better way to build a site before replacing it, allowing the transition to be more seamless?

Appreciate the insight!