Amy said:I have a great spam blocker, but yeah not a bad suggestion. Not sure how much text vs having a link at all matters these days? thought most spambots would see the "mailto" in the link and email anyway.
or a serverside include via a little pearl script? :halo: that aside, nice set of picsMike Hopley said:Amy, your photos are fantastic! :bow:
Amy said:I have a great spam blocker, but yeah not a bad suggestion. Not sure how much text vs having a link at all matters these days? thought most spambots would see the "mailto" in the link and email anyway.
You're right. Spambots will scan for links with href="mailto: ...", as well as scanning all text for @ symbols.
You can defeat them by using javascript to insert the link into the page. Spambots will only parse the HTML, so they never see the email link. To make the site accessible you would then need a contact form as a fallback for users who do not have javascript.
In principle spambots could also parse and execute javascript, but that's too resource-intensive to be worthwhile. It's simpler and more efficient to harvest the vast numbers of unprotected emails, and ignore the few emails that are cloaked.
Antwan said:or a serverside include via a little pearl script? :halo:
I think people like email better.
Amy said:If it becomes a problem I'll use one of the many ways of making it harder for spambots.
I do have a question though: some photog sites list print pricing. Others just say to contact them. Should I add a pricing sheet for prints? Trying to think of pros/cons of that. I offer lustre, metallic, and canvas wraps.
langcliffe said:I suggest that you should ensure that your HTML and CSS validates. Whilst one cannot guarantee browsers interpreting mark-up correctly, there is more chance if it validates.
Validate HTML of home page
Amy said:Working on fixing validation errors...I did a check but my tools are perhaps old...I coded websites years (re: decade) ago often and usually am stuck confused between old and new ways of doing thing.
I "hid" my email (couldn't get the one ya messaged me working right but I figured out a workaround similar).
Amy said:Got it working...a facepalm moment (as is usual when it's me with coding). I had to change the navigator.useragent to allow it to load on mobiles. :-[