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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • 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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...