This project has moved and is read-only. For the latest updates, please go here.

Widgets / Plugins in the content area

Aug 22, 2010 at 11:44 PM

Hello All,

1. Is it possible to bring widgets / plugins (eg., popular posts / related post) near the actual post in the content area?

2. Is it possible to create widgets like what i have in the home page of, how should i go about it?

3. The current post URL is like, we have references in other websites, how to make sure the links are not broken after moving to graffiti? as graffiti's url is different, I'm very new to URL rewrite.

If all these are workable, i'm planning to move the site to graffiti. Would be great if I could get solution for these questions.





Aug 24, 2010 at 5:30 AM

Hey, hopefully this will help you get started:

1) See this post on how to pull widgets into page content. The functionality isn't perfect, but it works quite well.

2) You can create widgets or extend chalk to add just about anything you want to add. For these things, I would say that custom chalk extensions are the way to go. If you can program it in .Net to display the content that you want, then you can do it with Graffiti.

Here's links with info on how to get started:

Extending Chalk

Creating Widgets

3) This one's a bit tougher. There are definitely ways to do it, but the solution is going to depend on your setup. If you are running IIS7 somewhere where you can access IIS directly, you can set up rules using the rewrite module to handle the redirects. If there are a ton of URL's though, that might get cumbersome because I don't know that you can come up with a generic rule to use across the board.

Another option is to create a custom HTTP handler to handle any .aspx URLs and in your .Net code figure out where to send it. For example (using your example url), you could have a category called Stocks, and the post could have the same title as it does now, meaning the URL for it would be You could then have your HTTP handler strip out the "/post/", the date "folders" and the ".aspx" and redirect the users (with a permanent 301 redirect) to the newly formed URL, which matches the Graffiti URL. Not sure if that makes sense, but I can try to explain in more detail if you need.

You could also modify the Graffiti code to keep the same URL structure, but I've never done that and not sure that I would recommend it either.

I'm sure that there are other ways to do the URL rewriting as well, and I may be missing something very easy to do, but that should get you started.

Aug 24, 2010 at 5:35 AM

3) Purchasing might save you a lot of trouble in this regard.


Aug 24, 2010 at 5:47 AM

Okay, I'm going to get a little salesman-y here for a second now, but hey, a guy's got to make a living. I'm not sure what your development experience is, but if any/all of this is over your head, or even if you just don't have the time to get this conversion done on your own, I do offer consulting services for customization of Graffiti along with standard .Net development. If you're interested, just send me a message.



Aug 24, 2010 at 5:49 AM
brianzalk wrote:

3) Purchasing might save you a lot of trouble in this regard.


Not sure that that honestly makes things much easier than just writing a handler in C# or using the IIS plugin from Microsoft. Configuring mod_rewrite isn't the easiest thing in the world to set up unless you've had some decent experience with it.

Aug 24, 2010 at 6:02 AM


"Easier" is certainly relative to experience.  I know plenty of non-developer folks who can setup/configure IIS tools and look on the forums for regex rules to piece together a solution.  If you aren't a developer and don't know how to write a custom HTTP handler in C#, I would consider that to be an "easier" solution.  

Speaking of the IIS plugin, you said, "If there are a ton of URL's though, that might get cumbersome because I don't know that you can come up with a generic rule to use across the board."  

It would be very easy to write a regex for isapirewrite based upon the URL provided in the original post regardless of the IIS version.

Hope that helps clarify.


Aug 24, 2010 at 3:11 PM

Thanks Charles & Brian... I need to dig on this... I'll come back if i have any more Q.


Thanks for your time!