Comments on: Features and Limitations http://www.somethinkodd.com/oddthinking A blog for odd things and odd thoughts. Fri, 21 Nov 2008 11:33:41 +0000 http://wordpress.org/?v=2.6.2 By: Julian http://www.somethinkodd.com/oddthinking/emailshroud-wordpress-plugin/emailshroud-features-and-limitations/#comment-46223 Julian Sun, 24 Jun 2007 12:08:00 +0000 http://www.somethinkodd.com/oddthinking/emailshroud-20/emailshroud-features-and-limitations/#comment-46223 Jonathan S. contacted me through private communication to highlight the impact of a known limitation in EmailShroud. A page had an INPUT form. One of the fields had a VALUE attribute, and the value contained an email address. As was warned about in the limitations, EmailShroud saw the email address and tried to protect it, breaking the HTML. This is a very specialised situation that won't affect most bloggers, but it is legitimate, and EmailShroud will break the page in this situation. I apologise, but I cannot yet see a solution here. It will be hard to detect this situation, and even harder to work out what to do about it - the email address cannot be safely protected, which leaves it open to the spammers to harvest. Jonathan S. contacted me through private communication to highlight the impact of a known limitation in EmailShroud.

A page had an INPUT form. One of the fields had a VALUE attribute, and the value contained an email address. As was warned about in the limitations, EmailShroud saw the email address and tried to protect it, breaking the HTML.

This is a very specialised situation that won’t affect most bloggers, but it is legitimate, and EmailShroud will break the page in this situation.

I apologise, but I cannot yet see a solution here. It will be hard to detect this situation, and even harder to work out what to do about it - the email address cannot be safely protected, which leaves it open to the spammers to harvest.

]]> By: Julian http://www.somethinkodd.com/oddthinking/emailshroud-wordpress-plugin/emailshroud-features-and-limitations/#comment-23341 Julian Mon, 01 Jan 2007 03:11:27 +0000 http://www.somethinkodd.com/oddthinking/emailshroud-20/emailshroud-features-and-limitations/#comment-23341 Mark L contacted me through private communication to identify a bug in EmailShroud. I have broken the WordPress coding standard by relying on the "<?" abbreviation for the "<?php" tag. If your web-server is not configured to support PHP markup using short tags, EmailShroud will not work. I will correct this egregious error in the next version, and apologise for the inconvenience. [Update: This was fixed in Version 2.1] Mark L contacted me through private communication to identify a bug in EmailShroud.

I have broken the WordPress coding standard by relying on the “<?”
abbreviation for the “<?php” tag.

If your web-server is not configured to support PHP markup using short tags, EmailShroud will not work.

I will correct this egregious error in the next version, and apologise for the inconvenience.

[Update: This was fixed in Version 2.1]

]]>