Title: Seeing
Last modified: April 20, 2026

---

# Seeing

 *  Resolved [jayti](https://wordpress.org/support/users/jayti/)
 * (@jayti)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/)
 * ![](https://wordpress.org/c2af6562-d544-4e99-85a0-f7eba52ce14a)
 * Running the latest version as of today (2.4.6). I snipped a piece of the “worst”
   page. It’s showing the code instead of the email address. I don’t believe anything
   else changed on other plug-ins, themes, etc. I see the plug-in updated three 
   weeks ago–I haven’t checked the page so it’s likely this happened with the latest
   update.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fseeing-2%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Thread Starter [jayti](https://wordpress.org/support/users/jayti/)
 * (@jayti)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/#post-18886020)
 * Apologies for no snippet, and for a poor topic title. Should be: “Seeing Code
   not email addresses”.
 *  Plugin Author [Josh](https://wordpress.org/support/users/oojosh/)
 * (@oojosh)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/#post-18886235)
 * Hi jayti,
 * Thanks for reporting this, I can see the issue on your contact page. The email
   addresses are
   showing as JavaScript code instead of being decoded.
 * What’s happening is something on your site is stripping the tags that the plugin
   uses to
   decode emails, which leaves the raw code visible as text. This is usually
   caused by a cachingplugin, security plugin, or your hosting provider’s firewall
   rules.
 * To help me narrow it down, could you go to Settings > Email Encoder in your WordPress
   admin,
   and in the sidebar on the right you’ll see a “Copy Support Info” link 
   with a clipboard icon.Click that, then paste the result into your reply here –
   it’ll give me your settings andactive plugins so I can pinpoint the conflict.
 * In the meantime, a quick workaround: on the same settings page, try changing “
   Protect emails
   using” to “automatically the best method (excluding javascript)”
   and save. That’ll switch toa CSS-based method that doesn’t rely on script tags.
 *  Thread Starter [jayti](https://wordpress.org/support/users/jayti/)
 * (@jayti)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/#post-18887218)
 * Thanks Josh. Been a busy day, but I have done as you suggested. Changing the 
   setting to other than javascript has returned it to working order. Thanks for
   your help. Support info is:
 *     ```wp-block-code
       === Email Encoder Support Info ===Plugin Version: 2.4.6PHP Version: 8.4.20WordPress Version: 6.9.4Theme: EmpowerWP (1.0.34, classic theme)Multisite: NoGD Library: YesMemory Limit: 512M=== Settings ===Protection: Full-page scanMethod: With JavaScript (auto best)RSS Protection: OnAJAX Protection: OffAdmin Protection: OffConvert to mailto: OnConvert to images: OffInput field protection: OffProtection Text: protected emailCustom Classes: mailto-linkCustom Href Attrs: (none)Skip Posts: (none)Skip Query Params: (none)Footer Scripts: OffSecurity Check: On=== Active Plugins (47) ===ManageWP - Worker (4.9.33)SW Copyright Year Updater (1.0.0)Advanced Custom Fields (6.8.0)Akismet Anti-spam: Spam Protection (5.6)AutomateWoo (6.2.3)Broken Link Checker (2.4.8)Classic Editor (1.6.7)Classic Widgets (0.3)ConvertBox Auto Embed WordPress plugin (1.1.2)Custom Sidebars (3.38)Donation For Woocommerce (3.9.8)Email Encoder - Protect Email Addresses (2.4.6)Email Verification for WooCommerce Pro (2.3.7)MonsterInsights - eCommerce Addon (8.6.2)MonsterInsights Pro (10.1.2)Gravity SMTP (2.1.6)Heinleinsociety Custom Plugin (1.0.0)Export CSV (0.1)Import CSV (0.1)Jetpack Protect (5.0.0)Jetpack (15.8-a.5)Login Security Captcha (1.8.7)Mesmerize Companion (1.6.168)Meta Tag Manager (3.3)MonsterInsights - User Journey Addon (1.1.8)NextGEN Download Gallery (1.6.2)Order Export & Order Import for WooCommerce (2.7.2)Poll Maker (6.3.2)Redirection (5.7.5)Simple History (5.26.0)SSL Insecure Content Fixer (2.7.2)Strategic Websites Management (1.3.15)User Switching (1.11.2)WooCommerce.com Update Manager (1.0.3)WooCommerce PayPal Payments (3.4.1)WooCommerce Tax (3.6.1)WooCommerce Subscription Downloads (1.4.1)WooCommerce Subscriptions (8.6.0)WooCommerce (10.6.1)Wordfence Security (8.1.4)WP Crontrol (1.21.0)SEOPress (9.7.4)WPForms Lite (1.10.0.4)WPMU DEV Dashboard (4.11.30)WPS Hide Login (1.9.18)PayPal Zettle POS (1.6.1)NextGEN Gallery (4.1.3)
       ```
   
 *  Plugin Author [Josh](https://wordpress.org/support/users/oojosh/)
 * (@oojosh)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/#post-18887330)
 * Thanks for sending the support info, that helped a lot.
 * Based on your plugin list, this looks like a case where another plugin on your
   site is stripping out the `<script>` tags that the JavaScript encoding method
   relies on, which would explain why you’re seeing the raw code instead of the 
   decoded email. The plugin itself is working correctly, something else is interfering
   with its output.
 * Likely candidates in your stack are SSL Insecure Content Fixer, Jetpack, or Wordfence–
   all of them do output buffering or HTML rewriting that can strip inline scripts.
   If you want to narrow it down, try deactivating them one at a time and check 
   the contact page after each.
 * Either way, the workaround I suggested should sidestep the conflict entirely.
   It uses CSS-based encoding instead of JavaScript, so even if another plugin is
   stripping scripts, your emails should still display correctly. I’d suggest leaving
   it on that setting unless you specifically need the JS method back.
 *  Thread Starter [jayti](https://wordpress.org/support/users/jayti/)
 * (@jayti)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/#post-18888273)
 * Thank you for the info and help!

Viewing 5 replies - 1 through 5 (of 5 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fseeing-2%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/email-encoder-bundle/assets/icon-256x256.png?rev=2056506)
 * [Email Encoder - Protect Email Addresses and Phone Numbers](https://wordpress.org/plugins/email-encoder-bundle/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/email-encoder-bundle/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/email-encoder-bundle/)
 * [Active Topics](https://wordpress.org/support/plugin/email-encoder-bundle/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/email-encoder-bundle/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/email-encoder-bundle/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [jayti](https://wordpress.org/support/users/jayti/)
 * Last activity: [1 month, 2 weeks ago](https://wordpress.org/support/topic/seeing-2/#post-18888273)
 * Status: resolved