FusionGrokker

Easily Cache the Return Value of Any Function

Tue, 14 Oct 2008 12:00:00 GMT

Work in web development long enough, and you'll run into caching. When done appropriately, it can be a real life saver. In CFML, we have several caching tools at our disposal.

The built in cfcache function will cache an entire page, and there are a bunch of projects on RIA Forge (search for "cache") that deal with caching of whole pages, partial pages, and specific data; and use various methods from memcached to underlying java caching. And of course, you can always roll your own cache using a persistent scope (application, session, client, or cookie) and some date comparison.

After about the 100th time of rolling my own custom caching, I decided it was time to wrap it up in a nice little UDF.

Before I show you the code, here's an example of how to use it:

<cffunction name="currentTime" output="false"> <cfreturn "The current time is #timeformat(now())#<br />"/> </cffunction> #cacheCallback("myApp.CurrentTime", CreateTimeSpan(0,0,2,0), variables.currentTime)#

Pretty simple, right? The first argument is a unique string that's used as the cache key, to identify which bit of data we're caching. The second is how long the cache is good for, and the third argument is a reference to a simple function that displays the current time.

Notice that the 3rd argument is not a string containing the name of the function to be executed, but actually a reference to the function itself. My cacheCallback function will check to see if the cache is expired, and either return the cached value or re-run the function being passed in and return the result, as appropriate.

A fourth and optional (boolean) parameter will force a cache refresh if true.

This has already proven useful, as a fellow Mango Blog plugin developer is using it to cache API results from services like Twitter and Flickr in some plugins he'll be releasing soon.

Here's the code for the cacheCallback function:

<cfscript> function cacheCallback(cacheKey, duration, callback){ var data = ""; //optional argument: forceRefresh if (arrayLen(arguments) eq 4){ arguments.forceRefresh=arguments[4]; }else{ arguments.forceRefresh=false; } //clean cachekey of periods that will cause errors arguments.cacheKey = replace(arguments.cacheKey, '.', '_', 'ALL'); //ensure cache structure is setup if (not structKeyExists(application, "CCBCache")){ application.CCBCache = StructNew(); } if (not structKeyExists(application.CCBCache, arguments.cacheKey)){ application.CCBCache[arguments.cacheKey] = StructNew(); } if (not structKeyExists(application.CCBCache[arguments.cacheKey], "timeout")){ application.CCBCache[arguments.cacheKey].timeout = dateAdd('yyyy',-10,now()); } if (not structKeyExists(application.CCBCache[arguments.cacheKey], "data")){ application.CCBCache[arguments.cacheKey].data = ''; } //update cache if expired if (arguments.forceRefresh or dateCompare(now(), application.CCBCache[arguments.cacheKey].timeout) eq 1){ data = arguments.callback(); application.CCBCache[arguments.cacheKey].data = data; application.CCBCache[arguments.cacheKey].timeout = arguments.duration; } return application.CCBCache[arguments.cacheKey].data; } </cfscript>

I've submitted this to CFLib, so hopefully it will be approved soon.

Disadvantages:

I tried for a while to figure out a way to pass arguments into the callback function, but never came up with anything. When I added a callbackArgs argument and passed that in as an argumentCollection to the callback function, CF threw an error telling me that I couldn't use named arguments in this case. I also tried to use CFInvoke, but that required passing in a string containing the name of the function instead of a reference to it, which while it would actually work with some massaging, wouldn't work as well in an Object Oriented architecture where passing objects (like function references) as arguments is common practice.

So for now, your callback functions must run without any arguments. If anyone has any other ideas for how to pass in arguments, I'm all ears.

New Themes for Mango Blogs

Mon, 13 Oct 2008 13:13:44 GMT

Mango Blog comes with some great themes, and with Mango's awesome custom tag access to data, it's super simple to create your own or modify an existing one to suit your tastes. But not everyone is a designer or has time to give it a shot. My buddy Mark has created a new site devoted to Mango themes called MangoWear.

There are both free and "premium" (paid) themes, but judging by his portfolio and free themes, I would say that they are definitely worth the cost if you don't want to do the work yourself.

So far there are only a couple of themes available, but it should be growing all the time. Go check it out!

HTML/CSS Tip: Specifying Multiple Classes

Mon, 06 Oct 2008 13:14:12 GMT

Since CFML developers are essentially very specialized web developers, I feel that it's important to continually learn and improve my skills not only with CFML, but also with HTML and CSS. Here's a trick I picked up earlier this year that I think could benefit a lot of people.

The beauty of CSS is that you can write simple, reusable rules that can be applied throughout your site to provide a consistent look and feel without setting individual display properties on every object on the page. You already knew that.

But let's say that you want all of your site's button elements to have the same overall style: a specific font, a background and border color, and maybe a set of color changes for hover (not displayed in IE). But on certain pages, you want all buttons to have a fixed width so that their edges line up when stacked vertically, and on other pages you want widths to be automatic so that you can fit more in a single horizontal row. This is a great case for multiple classes.

Take these two HTML samples (from different pages) for example. We'll start with our set of vertically stacked buttons:

<div id="buttons">
    <button class="standard" onclick="doStuff1();">1</button><br />
    <button class="standard" onclick="doStuff2();">2</button><br />
    <button class="standard" onclick="doStuff3();">3</button>
</div>

And now our single row of horizontal buttons:

<div id="buttons">
    <button class="standard" onclick="doFoo();">Foo</button>
    <button class="standard" onclick="doBar();">Bar</button>
    <button class="standard" onclick="doFooBar();">Foo & Bar</button>
</div>

Let's make them flat, with a light shade of gray for their background, and a darker shade of gray for their border. Add some font styling and a hover style, and they start to look pretty decent:

button.standard{ background-color: #eee; border: 1px solid #bbb; text-align: center; color: #666; font-family: Tahoma, Verdana, Helvetica; font-weight: bold; } button.standard:hover{ background-color: #935232; color: #fff; }

Now, here are the two classes that we'll use to specify widths:

button.autoW{ width: auto; } button.fixedW{ width: 200px; }

To apply these size style classes without losing our other styles, we can add them to the class attribute, as if it were a space-delimited list, like so:

<button class="standard fixedW">...</button>

Now, we can have consistent color & hover styles for our site, and be able to specify either a fixed or automatic width for it. Using this method, if you decide later that you want your button hover color to be something different, you only have to change it in one place.

I've tested this with IE6 and 7, Safari, and Firefox 1-3. I presume Opera and other modern browsers also support this functionality.

Announcing my Twitter Bot: TwitMeBack

Sun, 28 Sep 2008 21:05:25 GMT

Over a few evenings last week and over the weekend I wrote a twitter bot. It's not a client or a mashup. It simply looks for you to say certain things and replies later. It's basically a glorified alarm clock — one that you can set and receive via text message (if you have twitter setup for mobile updates).

The syntax is pretty simple:

@twitmeback in 15 time to make the donuts

@twitmeback in 1:45 check parking meter

You can specify the duration until you're reminded in either [hours]:[minutes] or just in a count of minutes.

Where I think this really gets useful is that it can do direct messages, too. Personally I prefer to keep mobile updates to directs only, so if I want a text message reminder, it needs to be in the form of a direct message. The bot will automatically follow you back if you follow it (it checks every half hour). Then, you can set reminders via direct message, like so:

d twitmeback in 30 don't forget to submit your time sheet

d twitmeback in 4:00 lunch time!

If your reminder is received via DM, it will remind you via DM. This way, your reminders can be totally private (if that's what you want), or work totally from text message.

Lastly, you can also specify a DM reminder by starting your message with "d", like so:

@twitmeback d in 90 is the pizza here yet?

Now go forth, and be reminded.

Windows Tip: No to All

Sat, 20 Sep 2008 12:15:00 GMT

Everyone agrees that Microsoft is not the really best when it comes to usability, right?

We've probably all looked at this dialogue at some point during our lives and said, "How about a No to All button, Microsoft?"

But did you know it's possible? Hold the shift key while you click the "No" button, and Windows will act as if there were a "No to All" button and you clicked it.

You're welcome.

Ask a Grokker: Why can't I activate an inactive Plugin in Mango?

Mon, 15 Sep 2008 13:00:00 GMT

Hey, everyone else is doing it. Why not me?

Mark asks,

I have been getting a lot of comment spam on one of my mango installs. I took a look and the captcha is not showing up anymore. The plug in's page says it's deactivated, however trying to activate it says it's already active? Have you see this before?

In fact, I have seen this before. I'm not sure what causes it, but what happens is somehow one of Mango's preferences files gets out of sync. Luckily, it's fairly easy to fix.

Open up the file pluginprefs.cfm, which should be in the root of your Mango install. Look (or search) for:

<entry key="userPlugins" ...

…and take a look at the value. There, you'll find the plugin listed that you're having difficulty activating. Remove it from the list, save the file, and try again to activate the plugin. In this case, the value to remove is "LylaCaptcha", as this is the plugin that can't be activated.

ColdSpring 1.2 released, website updated

Fri, 12 Sep 2008 14:19:43 GMT

Along with the long awaited 1.2 release of ColdSpring, the worlds best CFC IoC/AOP framework has a brand spanking new website, which looks great; and includes a total overhaul of the online documentation.

Congratulations to Chris Scott — manager of the Philadelphia CFUG, and project lead for ColdSpring — and the rest of the ColdSpring team. Looks like a job well done!

Related Entries plugin for Mango Blog

Wed, 10 Sep 2008 12:00:00 GMT

This plugin has been a long time in the making. It's something I knew from the outset that I would want in Mango, but after getting my feet wet by writing a few other small plugins, I knew I could do it. I made it as simple as I could, but there are still a couple of things you will need to know; one of which is that you might need to modify your theme to broadcast a new event in a couple of places. This new event is going to be a part of future versions of Mango, so there isn't any worry about future-compatability and worries when upgrading.

First of all, though you need a small update to the core of Mango. Even if you've got the latest version of Mango (1.1)! Laura posted a comment on the plugin ideas page with a link to the update zip file, and an explanation that it included a new plugin (home page chooser), some core modifications that were needed to support that plugin, and most importantly, some bug fixes — one of which is necessary for back-linking of related entries to work correctly. So before you do anything else, make sure you grab and install that update!

Once you've got the Mango update installed, go ahead and download my Related Entries plugin.

Now about that event. It's really simple to add. Open up your theme's index.cfm and post.cfm files (and archives, and other places you may want to show related entries…). The code to broadcast the event is really simple:

<mango:Event name="beforePostContentEnd" />

Simple, right? And where do you put it? Anywhere, really… within reason. It uses contextual information to look up related entries data for the current post, so you must broadcast it inside of a (custom tag) block. So for example, here's the relevant information from my theme's index.cfm template:

<mango:Posts count="5"> <mango:Post> ... <mango:Event name="beforePostContentEnd" /> <p class="date">Posted in ...</p> ... </mango:Post> </mango:Posts>

That's almost it! After you install the plugin, and add the event broadcast to your theme, there's just 2 more things.

First, relate a couple of entries. Edit a post, and look at the bottom of the form.

This new section should be displayed at or toward the bottom of the form. As it explains, you select a category from the left column to see its entries from the selected categories (use control to select multiple). Then click on any entries from the center column that you want to relate to the current entry; they will be displayed in the right column. (This is all done with jQuery ajax!) To remove an entry from the right column, double click it. When you submit the form, the posts in the right column will be marked as related to the current entry; and in addition to that, the current entry will be related to those posts.

When you submit the form, if you get an error that looks like this, then you didn't install the update!:

If you don't get the above error, then your data should be good to go. Now, you just need to style it.

When you've got related entries data, the event you're broadcasting is going to be replaced with some code along this line:

<div class="related"> <h2 id="RelatedEntries">Related Entries:</h2> <ul> <li><a href="http://server/post/your-post">Post Title</a></li> <li><a href="http://server/post/your-post">Post Title</a></li> <li><a href="http://server/post/your-post">Post Title</a></li> </ul> </div>

So, you can define some css rules for .related, #RelatedEntries (or .related h2), and .related ul, .related ul li, .related ul li a.

That's it. Enjoy!

One note for the future: The update I talk about above should be included in Mango 1.2, so if you've got 1.2 (or later) installed, don't worry about the update.

In case you missed the link before, you can Download my Related Entries Mango Blog Plugin right here.

Tracking the storm… Redux

Sat, 06 Sep 2008 18:19:58 GMT

A couple of days ago I used Rays code for tracking hurricane distance from your local zip code to add tracking of Hurricane Hanna to my family blog. Then my father in law was kind enough to point out that it was wrong. Way wrong! It was reporting distances of over 3,000 miles, when we're really less than 300 miles from it.

Closer inspection of the code showed that Ray accidentally swapped the order of latitude and longitude assignments from the NHC feed; and wasn't accounting for Southern and Western hemispheres being represented as a negative number. Ray posted about some changes he made in a comment on his post to fix these problems (if only I had seen those before now!).

Ray is going to post his updated script soon, but mine is below.

In addition to the same fixes, I've added a touch of encapsulation (though I did remove the zip lookup stuff once I knew the lat/long for my zip — because this was easily the slowest part of the whole script) and setup caching with a forced refresh, and refreshing if the previous attempt had any problems. Here's my entire script:

<cfif structKeyExists(application, "hannaData") and findNoCase("check back later", application.hannaData)> <cfset application.hannaData = getHannaData() /> <cfset application.hannaDataUpdated = now() /> </cfif>  <cfif structKeyExists(url, "updateHanna")> <cfset application.hannaData = getHannaData() /> <cfset application.hannaDataUpdated = now() /> </cfif>  <cfif not structKeyExists(application, "hannaData") or not structKeyExists(application, "hannaData")> <cfset application.hannaData = getHannaData() /> <cfset application.hannaDataUpdated = now() /> </cfif>  <cfif structKeyExists(application, "hannaDataUpdated") and dateCompare(now(), application.hannaDataUpdated, "n") gt 10> <cfset application.hannaData = getHannaData() /> <cfset application.hannaDataUpdated = now() /> </cfif> <cfoutput> #application.hannaData#<br/> <small><em>Updated: #timeFormat(application.hannaDataUpdated, "h:MM tt")#</em></small> </cfoutput> <cfscript> /** * Calculates the distance between two latitudes and longitudes. * This funciton uses forumlae from Ed Williams Aviation Foundry website at http://williams.best.vwh.net/avform.htm. * * @param lat1 Latitude of the first point in degrees. (Required) * @param lon1 Longitude of the first point in degrees. (Required) * @param lat2 Latitude of the second point in degrees. (Required) * @param lon2 Longitude of the second point in degrees. (Required) * @param units Unit to return distance in. Options are: km (kilometers), sm (statute miles), nm (nautical miles), or radians. (Required) * @return Returns a number or an error string. * @author Tom Nunamaker (tom@toshop.com) * @version 1, May 14, 2002 */ function LatLonDist(lat1,lon1,lat2,lon2,units) { // Check to make sure latitutdes and longitudes are valid if(lat1 GT 90 OR lat1 LT -90 OR lon1 GT 180 OR lon1 LT -180 OR lat2 GT 90 OR lat2 LT -90 OR lon2 GT 280 OR lon2 LT -280) { Return ("Incorrect parameters"); } lat1 = lat1 * pi()/180; lon1 = lon1 * pi()/180; lat2 = lat2 * pi()/180; lon2 = lon2 * pi()/180; UnitConverter = 1.150779448; //standard is statute miles if(units eq 'nm') { UnitConverter = 1.0; } if(units eq 'km') { UnitConverter = 1.852; } distance = 2*asin(sqr((sin((lat1-lat2)/2))^2 + cos(lat1)*cos(lat2)*(sin((lon1-lon2)/2))^2)); //radians if(units neq 'radians'){ distance = UnitConverter * 60 * distance * 180/pi(); } Return (distance); } </cfscript> <cffunction name="logit" output="false" returnType="void"> <cfargument name="str" type="string" required="true"> <cflog file="hurricane_hanna" text="#arguments.str#"> </cffunction> <cffunction name="getHannaData" returntype="string" output="false"> <cfset var dst = 0/> <cfset var long = 0/> <cfset var longdir = "" /> <cfset var lat = 0/> <cfset var latdir = "" /> <cfset var hannaXML = "http://www.nhc.noaa.gov/nhc_at3.xml"> <cfset var results = "" /> <cfset var match = "" /> <cfset var regex = "" /> <cfset var text = ""/> <cffeed source="#hannaXML#" query="results"> <cfif not results.recordCount> <cfset logit("Error - no feed entries")> <cfreturn "Unable to track hurricane Hanna (no data provided), check back later." /> </cfif>  <cfquery name="pa" dbtype="query" maxrows="1"> select rsslink, content, title from results where title like '%HANNA Public Advisory Number%' </cfquery> <cfif not pa.recordCount> <cfset logit("Error - cound't find a matching entry")> <cfreturn "Couldn't find information on hurricane Hanna, check back later." /> </cfif> <cfhttp url="#pa.rsslink#" result="results"> <cfset text = results.fileContent>  <cfset text = reReplace(text, "[\r\n]+", " ", "all")> <cfset regex = "CENTER OF TROPICAL STORM HANNA WAS LOCATED NEAR LATITUDE ([[:digit:]\.]+)[[:space:]]*([NORTH|SOUTH|EAST|WEST]+)...LONGITUDE ([[:digit:]\.]+)[[:space:]]*([NORTH|SOUTH|EAST|WEST]+)">  <cfset match = reFind(regex, text, 1, true)> <cfif arrayLen(match.pos) is 5> <cfset lat = mid(text, match.pos[2], match.len[2])> <cfset latdir = mid(text, match.pos[3], match.len[3])> <cfset long = mid(text, match.pos[4], match.len[4])> <cfset longdir = mid(text, match.pos[5], match.len[5])> <cfif longdir eq "WEST"><cfset long = -1 * long /></cfif> <cfif latdir eq "SOUTH"><cfset lat = -1 * lat /></cfif> <cfelse> <cfset logit("Error - couldn't find my matches in the string")> <cfreturn "Couldn't find lat/long location info for hurricane Hanna, check back later." /> </cfif> <cfset dst = latLonDist(lat,long,39.98,-75.82,"sm")> <cfset logit("distance:" & dst)> <cfset rtn = "" /> <cfset rtn &= "<strong>Distance:</strong> " & numberFormat(dst,',9.99') & " miles<br /><small>As of: <a " /> <cfset rtn &= "href='" /> <cfset rtn &= pa.rsslink /> <cfset rtn &= "'><strong>#replaceNoCase(pa.title, 'Tropical Storm HANNA Public ', '')#</strong></a><br />" /> <cfset rtn &= "Hanna Lat: #lat# #latdir#<br />Hanna Long: #long# #longdir#</small>" /> <cfreturn rtn /> </cffunction>

Introducing SmartType Mango Blog Plugin

Thu, 21 Aug 2008 12:00:00 GMT

Last night I quickly threw together a Mango Blog plugin for something I've wanted ever since leaving WordPress: Smart Dashes. Since it was possible with the component I was implementing, I also added conversion of elipses.

I can't take any credit for any of the difficult parts of this; all I did was wrap Seb's Code in a Mango plugin.

From the project page:

SmartType Mango Blog Plugin is a simple implementation of Seb Duggan's SmartType ColdFusion Component to prettify post and page content and titles. It implements his replacement for elipses (... as …) and en and em dashes (- as – and -- or --- as —). Folks who have used WordPress in the past should be familiar with this behavior, except that I'm not changing single or double quotes. That was one of the things I hated about WordPress, because it always messed up my code samples.

If you want to include in an elipses, single dash, or set of dashes, without it being replaced, preceed it with a back-slash: \

Download it here: SmartType Mango Blog Plugin 0.1

Install Instructions:

Unzip to the components/plugins/user/ folder

Activate in the Add-ons section of your Mango Blog Admin

There is no step 3.

CF8 Certification, Here I Come!

Mon, 18 Aug 2008 13:43:38 GMT

Last year I got my first ColdFusion certification, just in time for a new version of CF to come out and make me feel like I was behind again. Since the test is only $150, I figure I might as well upgrade to a CF8 certification.

I've heard rumors that thanks to Ray, the CF8 exam is much tougher than the CF7 exam. And since it's going to be harder, and I really don't want to lose the "Advanced" level, I'm going to prepare pretty hard. Last year I did self-study, and it was pretty overwhelming — there's just so much material and you don't get a great idea for what to study. This year, I'm going to prepare with the recently released CF8 Exam Buster training software.

I've already got it installed and gone through the first test, and I'm confident it's going to help me be prepared for the exam. I'll post again after I get my exam results and let you know what I think of CF8 Exam Buster, and whether or not I maintained my "advanced" level certification.

Protect your websites, logs, and inbox from SQL Injection

Fri, 08 Aug 2008 15:26:03 GMT

If you're like me you leave error reporting emails on for most of the sites that you build, so that wherever possible you are alerted to potential problems — like the recent wave of SQL Injection attacks — before the website owner (your client) knows they're being attacked, and hopefully, before an attack is successful. Of course, you're a responsible coder and you're logging and reporting errors, and then hunting down and eradicating the buggy code… right?

But as was pointed out this moring on twitter by Adam Lehman, if you log and subsequently email yourself or anyone else for every single error your website throws, you could end up flooding your own inbox (or worse, the inboxes of your clients and coworkers!) with error reports; essentially causing a Denial Of Service attack on yourself. And you may overly tax your server's resources in the process. It doesn't get much more lose-lose than that.

As ColdFusion Muse points out, a majority of recent attacks have been an attempt to append some javascript to every text field in a database, and they are using a very specific method: Declaring a text variable that contains some TSQL instructions, and then evaluating it. And like something out of a bad comedey, a few hours after reading Mark's post, it started happening to two of the websites my group manages. And boy, did the emails start coming.

Luckily, because the attack is so specific, it's easy to head off.

If you're using Application.cfm, just add this somewhere near the top:

<cfif findNoCase("DECLARE%20@S", cgi.query_string)><cfabort/></cfif>

And of course, if you're using Application.cfc, you can just put it in the onRequestStart function. Either way, you should position this code so that it is run before any significant work is done on the web server. There's really no generic reason it can't be line 1.

By doing this, you'll protect yourself from this specific attack (but not all SQL Injection) and stop all of those nagging error emails and log entries. Then you can focus on important things like making sure all of your queries use CFQueryParam.

Even prettier SES URLs in Mango

Thu, 31 Jul 2008 04:20:20 GMT

Tonight I installed Ionic's ISAPI Rewrite filter on my server and set it up for this domain. I've always been a fan of the www-less URL, so now you don't have a choice — I'm redirecting you here. In addition to that, I'm making urls like /page.cfm/projects/burnt-mango accessable as /page/projects/burnt-mango. I even took it a step further and redirect you to the new pretty format from the old ugly format, in case there are any errant URL's going around.

The first thing I had to do, once I got the ISAPI filter installed and running, was to define my rewrite rules:

# force removal of www. prefix on all requests RewriteCond %{HTTP_HOST} ^www\.fusiongrokker\.com [I,U] RewriteRule ^/(.*) http://fusiongrokker.com/$1 [I,R=301,U]

This takes care of getting rid of "www." from the URL.

###### Mango Blog stuff #redirect old url's to their new fancy url's RewriteRule ^/post.cfm/(.*)$ /post/$1 [R=301,I,U] RewriteRule ^/page.cfm/(.*)$ /page/$1 [R=301,I,U] RewriteRule ^/archives.cfm/(.*)$ /archives/$1 [R=301,I,U] RewriteRule ^/author.cfm/(.*)$ /author/$1 [R=301,I,U]

These will redirect you from the old page.cfm/page-name format to the new page/page-name format.

#standard mango rewrites RewriteRule ^/post/(.*)$ /post.cfm/$1 [I,U,L] RewriteRule ^/page/(.*)$ /page.cfm/$1 [I,U,L] RewriteRule ^/archives/(.*)$ /archives.cfm/$1 [I,U,L] RewriteRule ^/author/(.*)$ /author.cfm/$1 [I,U,L]

And lastly, these rewrite the new page/page-name format as page.cfm/page-name so that Mango can still interpret them correctly.

Notice that for all of my redirects ([R] flag) I'm using R=301. 301 is the status code for Moved Permantently, rathern than the default of 302, Moved Temporarily. This will tell search engine spiders and other smart things to update themselves; as well as preserve any PageRank that the old URL might have had. The L flag stands for "Last" and indicates that no further rules should be processed after this one is matched. In this case, I'm using it to prevent circular references, where going to page/page-name rewrites as page.cfm/page-name, which redirects to page/page-name which rewrites as… yeah.

Update: As suggested by Seb Duggan in the comments, I've combined the above rules into these two simple lines:

After the rules are in place, we have to tell Mango how to output URLs in the new format. It uses a special file called config.cfm which contains your blog settings.

<entry key="searchUrl" value="archives/search/"/> <entry key="postUrl" value="post/{postName}"/> <entry key="authorUrl" value="author/{authorAlias}"/> <entry key="archivesUrl" value="archives/"/> <entry key="categoryUrl" value="archives/category/{categoryName}"/> <entry key="pageUrl" value="page/{pageHierarchyNames}{pageName}"/>

These are just the relevant settings, of course. They should use the format that you want the user to see the URL as, because this is what Mango uses to format its links.

I keep finding more and more reasons to love Mango. This is just another one of them.

The Survey For People Who Make Websites

Tue, 29 Jul 2008 12:21:45 GMT

This year is A List Apart's second year running their Survey For People Who Make Websites. I just completed it (18 pages, average 2-3 questions per page) in about 8 minutes, so what are you waiting for?