ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Comment preferences and charcter entities

September 03, 2010 4:59am

Subscribe [6]
  • #1 / Sep 03, 2010 4:59am

    danieljohnbarnes

    151 posts

    Running 1.6.9 20100430 standard lamp setup.

    In comment preferences for a weblog I have:

    Comment Text Formatting : XHTML
    Comment HTML Formatting : Convert…char entities
    Automatic Email addresses : No (not that this setting should matter)

    However, if someone puts the following comment:

    In this case, we are looking at a situation where you, the buyer, stops paying the premiums. This is a contractual breach. Instead of creating a situation where there are thousands of lawsuits in which a life insurance company is suing policy holders,<a href="http://www.badpspamdomain.com/">Insurance reviews</a>

    Then that link is presented and rendered by the browser as is - no char ents.

    I have enough on my plate dealing with bio field link stuffers so am I missing something obvious? Not using anything fancy on the template side, just a simple

    {comment}
  • #2 / Sep 03, 2010 9:42am

    Ingmar

    29245 posts

    Can you show us a link to one such entry? Are you running any extensions? You might also consider upgrading to the latest build (although that’s probably not at the heart of this issue).

  • #3 / Sep 07, 2010 6:56am

    danieljohnbarnes

    151 posts

    I can’t post a live link right now, but I have verified this behaviour not happening on a clean install.

    No 3rd party extensions, no modules other than the forum module is installed, but it still happens if it’s removed.

    It’s an odd one.

  • #4 / Sep 07, 2010 3:44pm

    Ingmar

    29245 posts

    What happens when you use some other Comment Text and Comment HTML Formatting options?

  • #5 / Sep 08, 2010 8:06am

    danieljohnbarnes

    151 posts

    Okay, I have managed to get it working in my testing, although unsure of what I did to make it happen (nothing major, just going away and coming back a hour or 2 later), going to push it back live and see if any real world spammers generate different results.

    Thanks

  • #6 / Sep 08, 2010 9:07am

    Sue Crocker

    26054 posts

    We can keep this thread open a bit longer.. let us know when you’re ready to close it.

  • #7 / Sep 17, 2010 7:31am

    danieljohnbarnes

    151 posts

    Thanks Sue.

    Think I have found the issue though.

    Now, html is converted to character entities.

    However, if you post a URL in this form (logged in or not):

    [url="http://www.spammersite.com"]Spam Anchor Text[/url]

    the following happens:

    1. The listed email contacts for comment notification get an email with the link code shown as:

    <a href="http://www.spammersite.com">Spam Anchor Text</a>

    For this reason I assumed the spammer had entered the link like that when it appears they are using BB code and EE is post processing for the notification emails.

    2. The link is converted and displayed as a clickable link on the entry page by EE.

    I found this - http://ellislab.com/expressionengine/user-guide/general/bbcode.html

    So it seems that there is some intended behaviour, but I am hoping there is an option to turn the BB support off, otherwise it’s a Welcome doormat for would be EE spammers and the ability in the CP to prevent URLs being automatically being turned into links is a bit useless if it can be bypassed so easily 😊

  • #8 / Sep 17, 2010 8:25am

    danieljohnbarnes

    151 posts

    Okay, so I have done some more digging:

    The following spammer site was placed into the blacklist module - easigo.co.uk

    Typing:

    easigo.co.uk

    Yields no error.

    <a href="http://www.easigo.co.uk">http://www.easigo.co.uk</a>

    Yields an error.

    [url="http://www.easigo.co.uk"]Easigo[/url]

    Yields NO error and of course creates a link too.

    So I guess it’s subjective whether the non http://www. version on it’s own should yield an error when the version with it does, but certainly going down the BB route bypasses it altogether.

  • #9 / Sep 18, 2010 3:10pm

    Greg Salt

    3988 posts

    Hi Daniel,

    Let me investigate this a bit further. I’ll update this thread as soon as I can.

    Cheers

    Greg

  • #10 / Sep 19, 2010 5:21pm

    Greg Salt

    3988 posts

    Hi Daniel,

    I can’t replicate the issue with Blacklist - if I add a root domain then all subdomains of that domain are blocked as well. I am discussing the BB code question with the rest of the team. Thank you for your patience.

    Cheers

    Greg

  • #11 / Sep 23, 2010 6:27am

    danieljohnbarnes

    151 posts

    Hey Greg,

    Thanks for the update.

    I am still seeing the root domain issue. To clarify, I am simply pasting the URL as is in the comment field, exactly the same as the entry in the blacklist.

    Can you confirm your test used a co.uk domain name, rather than a single extension like .com or .net?

    On the BB code issues (ability to turn off and blacklist not affecting BB entries) - thanks, waiting patiently 😊

  • #12 / Sep 24, 2010 2:38am

    John Henry Donovan

    12339 posts

    danieljohnbarnes,

    We are still awaiting to hear back on the BBcode question but regarding your Blacklist can you tell us if you are writing it to a htaccess file ?

  • #13 / Sep 24, 2010 7:12am

    danieljohnbarnes

    151 posts

    regarding your Blacklist can you tell us if you are writing it to a htaccess file ?

    No I am not.

    Thanks.

  • #14 / Sep 24, 2010 1:42pm

    Sue Crocker

    26054 posts

    Is there a reason why you aren’t writing it to an .htaccess file?

  • #15 / Sep 27, 2010 5:43am

    danieljohnbarnes

    151 posts

    As I understand it’s an option, it’s not mandatory, and not part of the setup so it’s never been enabled.

    Simply preventing spam input is good enough for me, so long as it works, and given the size of the URL blacklists I’d rather not have all those in my htaccess file.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases