Jump to content
Roope

Email Obfuscation (EMO)

Recommended Posts

I've doubled up on javascripts and apparently it's causing an issue.  I recently started working on an interactive map on my site, the problem is that since I'm rendering the HTML on an event (click of the state loads .html(<div>...john@email.com...) ), it's loading the replacement text instead of my email addresses.  Are there any steps I can take to make it work properly without blocking the template altogether?

Thanks for info! Unfortunetaly I don't think there is any other option at the moment and I'm currently very busy with my projects so I don't have any time to debug the module right now but when I do, I'll get back to this. If you have time, you could paste here simplefied test case how to reproduce the issue. Thanks!

Share this post


Link to post
Share on other sites

Thank you for the module, works great for simple mailto under PW 2.6 as well.

All the best!

Share this post


Link to post
Share on other sites

Hi,

great modul, it works for me under PW 2.7.1.

My problem is, I dont get it work when email contains german umlaute like ö or ä.

Can you help please?

Share this post


Link to post
Share on other sites

Hello guenter!

Umlautes are working fine here - what kind of problems are you facing?

Share this post


Link to post
Share on other sites

Hello guenter!

Umlautes are working fine here - what kind of problems are you facing?

Hi,

for example this is in source :

<!--Email: <span id="emo_email_1" class="emo_email">Enable JavaScript to view protected content.</span><br>-->
<!--Email: <span id="emo_email_2" class="emo_email">Enable JavaScript to view protected content.</span><br>-->
<!--Email: info@kübelgeräte.at<br>-->

happend nothing for info@kübelgeräte.at

Share this post


Link to post
Share on other sites

OK, thanks!

 
I've just pushed a fix to module repo. Please update and see if it works for you.
  • Like 1

Share this post


Link to post
Share on other sites

OK, thanks!

 
I've just pushed a fix to module repo. Please update and see if it works for you.

You are great!! Now it works fine!

thanks

  • Like 1

Share this post


Link to post
Share on other sites

Hello,

On a live development website, powered by ProcessWire 2.7.1, I've just updated Email Obfuscation (EMO) from 1.0.2 to 1.0.4. via the Upgrades module.

Now, on a directory page, the first two email addresses are ok, the third one is "replaced" by the � sign (Firebug -> �

<span id="emo_email_3" class="emo_email"></span>), and all the following ones are replaced by "Enable JavaScript to view protected content.".

(I've just upgraded to ProcessWire 2.7.2, it doesn't change anything.)

Source code

First two email addresses and all the other ones except the third one:

<span id="emo_email_[number]" class="emo_email">Enable JavaScript to view protected content.</span>

Third one:

<span id="emo_email_3" class="emo_email">Enable JavaScript to view protected content.</span>

Share this post


Link to post
Share on other sites

Hello Christophe!

 
Could you please tick debug mode on from module admin page and see what it outputs. Found email data is appended to page source after closing </html> tag. Do addresses look ok there?
  • Like 1

Share this post


Link to post
Share on other sites

I had enabled debug mode and checked a bit the source code. I've just done it again.

Apart from the third email that is prepended with �� the rest seems ok.

The following emails are perhaps not displayed correctly because of the third one.

Share this post


Link to post
Share on other sites

Hello PWaddict!

 
Haven't use AIOM but according to module readme you have to first enable Directory Traversal Filter:
 
Then choose Load manually as Script file loading method at EMO config page and load required emo.js (or emo.min.js) with AIOM:
<script src="<?php echo AIOM::JS('../modules/EmailObfuscation/emo.min.js'); ?>"></script>

Share this post


Link to post
Share on other sites

Hello PWaddict!

 
Haven't use AIOM but according to module readme you have to first enable Directory Traversal Filter:
 
Then choose Load manually as Script file loading method at EMO config page and load required emo.js (or emo.min.js) with AIOM:
<script src="<?php echo AIOM::JS('../modules/EmailObfuscation/emo.min.js'); ?>"></script>

Oh I didn't noticed Directory Traversal Filter at all. LOL

Thank you very much Roope and have a GREAT new year!

Share this post


Link to post
Share on other sites

Great module you built here Roope.

I just found one issue with it, it detects email addresses in some links. For example google maps links like this: https://www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667,7.2779266,18z/data=!4m2!3m1!1s0x0000000000000000:0xeaf2e4dfe02713bb?hl=en

Here's the debug data from that page:

<!-- 

 EMO DEBUG DATA

 Email crypting took 0,0014450550079346 seconds

 Found 3 matches:

 1[0] = <a href="mailto:info@gad.ch">info@gad.ch</a>
 1[1] = info@gad.ch
 1[2] = info@gad.ch

 Hash: "MaT6r2Kwq+INJ5LhlmNOlFYgljJ6UeiO0C9HlFYgledc45O805NP02YGX5zyJCAgl50cSa3w0jACUBfcro1P"
 Data: <a class="emo_email" href="mailto:info@gad.ch">info@gad.ch</a>

 2[0] = info@example.com
 2[1] = info@example.com
 2[2] = info@example.com

 Hash: "MaT6r2Kwq+INJ5LhlmNOlFYgljJ6UeiO0C9HlFYgledc45O805NP0vwwlv.70ZACl29HM5O805NP0vwwlv.70ZACl29DX2Tp"
 Data: <a class="emo_email" href="mailto:info@example.com">info@example.com</a>

 3[0] = //www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667
 3[1] = //www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667
 3[2] = //www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667

 Hash: "MaT6r2Kwq+INJ5LhlmNOlFYgljJ6UeiO0C9HlFYgledc4HDc3+3+X53cl2370ZACUjNhrv.xX+.7rFzOX90cl5dw3aOclHhQrFSkt+dg0Qdml5qcSBS+XCTuIot2zCqHMHDc3+3+X53cl2370ZACUjNhrv.xX+.7rFzOX90cl5dw3aOclHhQrFSkt+dg0Qdml5qcSBS+XCTuIot2zCqDX2Tp"
 Data: <a class="emo_email" href="mailto://www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667">//www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667</a>

-->

I couldn't really figure out a way to get it to work properly, but there's a workaround for now, we just use the short URLs provided by google maps.

Share this post


Link to post
Share on other sites

I just found one issue with it, it detects email addresses in some links. For example google maps links like this: https://www.google.ch/maps/place/Fondation+gad+Stiftung/@47.1215667,7.2779266,18z/data=!4m2!3m1!1s0x0000000000000000:0xeaf2e4dfe02713bb?hl=en

Thanks flo!

 
Just pushed a fix to github. Please update and see if it helps.

Share this post


Link to post
Share on other sites

Fantastic! That seems to work.

Thank you very much for the quick fix.

Share this post


Link to post
Share on other sites

Thank you Roope for the great module! :rolleyes:

But unfortunately I can't get to work ???

  • installed propper
  • placed the script in the head section manually:
    <?php echo '<script src="/site/modules/EmailObfuscation/emo.min.js"></script>'; ?>
  • script file loading method is set to "manually"
  • script loads propper in head
  • but, the e-mail addresses are not converted within span elements

It looks like the module does not interfere at all. Any suggestions???

Share this post


Link to post
Share on other sites

You should perhaps add this in document.ready (or document.DOMContentLoaded if not using jQuery):

if(emo_replace) {
    emo_replace();
}

 

Share this post


Link to post
Share on other sites

Hi tpr, thanks for your reply.
I added this as suggested to document ready.
Firebug gives me now a ReferenceError: emo_addr is not defined

Share this post


Link to post
Share on other sites

You should see a javascript section at the bottom where emo_addr array is present. Are you sure it's there?

Share this post


Link to post
Share on other sites

Nope, no emo_addr array is present :(

I guess you mean this part of the module:

		// create addresses script block
		$addrScript = "\n<!-- emo -->\n<script>\n var emo_addr = new Array();\n";
		$addrScript .= "{$this->addrScript} addLoadEvent(emo_replace());\n</script>\n"

It looks to me as if the module is not active. Either the emo_addr array nor the addLoadEvent are implemented. *weird* :huh:

Share this post


Link to post
Share on other sites

Do you have a closing body tag in your html output? The module uses that to add the script block.

The function addLoadEvent is in emo.min.js.

Also make sure you haven't applied any template exclusion in the module settings, just to make sure.

Share this post


Link to post
Share on other sites

Thank you tpr.
Closing body tag </body> is present in the html output.

Quote

Also make sure you haven't applied any template exclusion in the module settings, just to make sure.

-> this is empty / none template is applied to exclusion.

Share this post


Link to post
Share on other sites
8 hours ago, Bacelo said:

Thank you Roope for the great module! :rolleyes:

But unfortunately I can't get to work ???

  • installed propper
  • placed the script in the head section manually:
    <?php echo '<script src="/site/modules/EmailObfuscation/emo.min.js"></script>'; ?>
  • script file loading method is set to "manually"
  • script loads propper in head
  • but, the e-mail addresses are not converted within span elements

It looks like the module does not interfere at all. Any suggestions???

Hello @Barcelo!

So email addresses are replaced by text set in module config but conversion back to email doesn't kick in, right? Double check that emo.js is really present because it sounds like there's the issue here. Maybe consider adding modules config url to the file path:

<?php echo '<script src=" . $config->urls->modules . EmailObfuscation/emo.min.js"></script>'; ?>

 

Share this post


Link to post
Share on other sites

Feature request: one thing that would be cool is to be able to enable this only for some templates, instead of disable;
because i only need it on the contact page, so i'd need to disable like 30 templates, rather than enable 1, the way it is currently;

Is there any way of conditionally loading this module by the API?

One of the really critical issues here is that the module is still not able to skip stuff like twitter handle (e.g. @processwire)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...