Now that the new release of jQuery 1.4 is settling down, it’s time to update my jQuery Mango plugin.
It doesn’t do much – just includes the jQuery library (version 1.4.2) into the head of your blog page.
Update: Plugin release 2 now includes the latest version of the BasePlugin cfc, to avoid error messages on upgrading.
Wow – it’s been a while since I last posted…
This is just a quickie – a reminder for my own reference, but could also be useful to others.
I’m building a shop, and the email confirmations include the line:
Your credit card statement will show a payment to "MYDOMAIN.COM".Which is fine, except that many mail clients (e.g. Apple Mail) will take MYDOMAIN.COM and link it as a URL – which I don’t want.
To avoid this, simply add a zero width space into the “URL” – for instance:
Your credit card statement will show a payment to "MYDOMAIN​.COM".(That’s the HTML version. If you’re generating a plain text alternative (using CFML, of course), you’ll want to use #Chr(8203)#).
The text will now look identical – except it will not be linked by the mail client.
When building a jQuery-enhanced site (or using any other JavaScript library, for that matter) I find one of the tasks I use jQuery for is to set the initial display states of various elements on the page.
For instance, you may have some elements that should only be displayed if JavaScript is enabled; and some which should be hidden. But what do you do to avoid the flash of unwanted content which may appear before various libraries load? Here's my solution...
My latest web project has just launched - a mobile-optimised version of the successful LoveHoney website, where I've been doing web and ColdFusion work on and off for the last couple of years.
LoveHoney have been selling sex toys and lingerie in the UK and around the world for 6 years - so be warned, the sites may not be safe for work! (So all the more reason to browse on your mobile phone...)
Every now and again, I come across something in ColdFusion that really bugs me. This is today’s annoyance.
When using <cfoutput> to loop over a query, the query attribute cannot be a function name. For example, I have a CFC with a method getRoles(), which returns a query.
I would have expected that the following would work:
<cfoutput query="getRoles()">
...
</cfoutput>…but this throws an error. So I am forced to add extra code to work around it:
<cfset qRoles = getRoles() />
<cfoutput query="qRoles">
...
</cfoutput>I’m sure there’s a logical reason why this should be the case, and that someone will tell me what it is, but I just find it irritating.
Powered by 