We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 12601
    • 9 Posts
    I am using the latest MODx version from SVN (0.9.5 RC3 rev 2051), and have inserted into my template the ProtectEmail snippet from Etomite (http://etomite.org/browsesnippets.html?int_snipid=43&lst_category=0).

    Until two days ago, ProtectEmail worked on all pages. However, now I have updated my local development server to the latest SVN release, ProtectEmail causes my homepage (page ID = 1) to return a 404 error. If I rename the ProtectEmail snippet (to stop it loading), my homepage displays. No other page seems to be affected by the ProtectEmail snippet.

    Can anyone help me resolve why the homepage should be "lost"? Does anyone else use ProtectEmail on their sites and find it now breaks?

    (Why do I use ProtectEmail? Because it doesn’t just encode an email address; it generates a random starting value for the encoding, thus making it even harder for any automated systems to decode the email address.)

    [Later ...]

    Just found ProtectEmail is breaking more pages than just the homepage. I fear the snippet has been rendered unusable by the latest SVN version. It would be a real shame to lose this snippet, as it is more advanced in some ways to others I have seen.
      • 22815
      • 1,097 Posts
      That Eto link leads to a smarmy message if you click on it directly from this site. Apparently you shouldn’t have linked to that page because you could make your own repository, and to save their bandwidth what you should presumably do is tell people to go and click through several pages to find the snippet on the Eto site. That doesn’t actually make any sense, but hey, that’s eto.

      (If you copy paste it, it works.)

      I would be interested to know why this breaks, because it may be an issue that needs resolving. Of course, the SVN is not guaranteed to be stable and there may be an issue with rev 2051.

      It is unclear what you updated from - if you could tell me what you were running two days ago that would make it easier to track down what is causing the issue.

      Other than that, all I can do is suggest you consult our own code repository and give:
      http://www.modxcms.com/Email-Link-Obfuscator-604.html
      a go.
        No, I don't know what OpenGeek's saying half the time either.
        MODx Documentation: The Wiki | My Wiki contributions | Main MODx Documentation
        Forum: Where to post threads about add-ons | Forum Rules
        Like MODx? donate (and/or share your resources)
        Like me? See my Amazon wishlist
        MODx "Most Promising CMS" - so appropriate!
        • 12601
        • 9 Posts
        Quote from: PaulGregory at Nov 24, 2006, 09:50 AM

        I would be interested to know why this breaks, because it may be an issue that needs resolving. Of course, the SVN is not guaranteed to be stable and there may be an issue with rev 2051.

        It is unclear what you updated from - if you could tell me what you were running two days ago that would make it easier to track down what is causing the issue.

        One site is using 0.9.5 RC3 rev 2004, another using rev 2032, and ProtectEmail works in both instances. The site using rev 2051 is the one highlighting the conflict with ProtectEmail. Hope this helps you resolve the conflict. It’s going to be something blindingly obvious, I hazard a guess, but I am not a programmer ... sadly. sad )

        Quote from: PaulGregory at Nov 24, 2006, 09:50 AM

        Other than that, all I can do is suggest you consult our own code repository and give: http://www.modxcms.com/Email-Link-Obfuscator-604.html a go.

        I’ve looked at the Email Link Obfuscator, and while it does accomplish its objective, I prefer ProtectEmail because of the latter’s element of introducing randomness into the obfuscation encoding.

        Quote from: PaulGregory at Nov 24, 2006, 09:50 AM

        That Eto link leads to a smarmy message if you click on it directly from this site. Apparently you shouldn’t have linked to that page because you could make your own repository, and to save their bandwidth what you should presumably do is tell people to go and click through several pages to find the snippet on the Eto site. That doesn’t actually make any sense, but hey, that’s eto.

        (If you copy paste it, it works.)

        ???

        Oops! Sorry. embarrassed Was trying to be helpful to any reader who was interested to know where to find ProtectEmail.