With this plugin you can let users of FarCry add custom forms to their websites. Each form submission will be emailed to an address that is defined for each form, as well as being logged and available from the FarCry administration.

This is the full version of the plugin that was started in my FarCry plugin tutorial.

A pdf file with documentation is enclosed in the download.

This plugin is open-source under the Apache License, Version 2.0

If you have questions or would like to contribute in further enhancing the plugin, please contact me.

Also if you use the plugin in your FarCry projects I'd love to hear about it.

DOWNLOAD

This plugin is released by IDLmedia AS

I just wrote a tutorial on making plugins in FarCry 4 making use of the FarCry Form Tools technology. I think it really shows some of the awesome powers of FarCry. Scaffolding, ORM, code- and application generation in a very smooth package is what this is about.

While FarCry is known to be an amazing CMS - it has developed into a full blown application framework - where CMS is just one of the plugins that you can make use of. In this tutorial I show you how to build another application/plugin - even though this plugin is mainly ment to be used together with the CMS.

Enough said - click the download link below to download the tutorial in pdf format.

DOWNLOAD

In a comment to yesterdays post about the skin:buildLink tag Jack is asking;

What about parameters?

If we have parameters on link such as &pagename=123&language=en_us

Now that is a good question, and David makes a good answer to that in a follow up coment.

The buildLink tags also takes a few nice args that let you manage other params etc.

* The stParameters arg will allow you to supply a struct that will be used to create the extra URL params * Also the xCode arg will let you add other attributes to the (a) link tag (good for titles etc).

But how do you learn about this? Where do you go to find out what parameters a tag can take? I find that the easiest is to go straight to the code in the core. For example, if you open the file core/tags/webskin/buildLink.cfm file you'll see the following (abreviated):

Some of the attributes the tag can take are explained in the comments to the tag, but not all. But looking at the cfparams you get a pretty good overview over what attributes you can use. Ok - it's not totally intuitive what they all do, but getting to know the attributes you can use and what they do plays a big part in using the tag libraries succesfully.

Happy FarCry'ing

One of the tag library tags I use the most is skin:buildLink

This one you use to build links to any of the objects (articles, news, images etc.) within your application. All you need is the objectID. Let's say that you are showing a teaser, and want to link to the full article from a read more link.

You'd do this (abreviated):

Notice that you escape cfoutput before calling the tag - this as part of limiting white space.

Very handy to know - especially if your site uses FUs

Happy Farcry'ing

When developing applications in Farcry a lot of time and head scratching can be saved by knowing the available tag libraries and how to use them.

Tag libraries are usually included at the top of the page like this:

(The paths above are for Farcry 4. In Farcry 3 you would write "farcry_core" instead of "core")

Typically you only include the tag libraries that you need.

I will now and then post examples on how to work with the available tag libraries.

Stay tuned.

A client wanted a site that should have content in Norwegian, English and French. In the design file there was separate choises for the three different languages, and then a navigation area, where the navigation should be in the currently selected language.

This could be solved in different ways. One could make three different page templates calling the three different language navigations - or one could make categories for each of the languages and make pages belong to one of these.

However we wanted to have only one template, and not to have categories. We wanted to sort it with three different top nodes in the site tree. Looking like this:

Then we gave aliases to these three navigation nodes.

We then made a new method in a utilities cfc we use in our company, and call it like this from out header template (before the navigation section):

The method then checks if the current page, or any of it's ancestors have an alias of one of those provided with the cfinvokeargument. It then returns the alias, and we can make the navigation like so:

Here's the code for the method (first version - it still needs some work):

By doing it this way we have a reusable way of handling this, without the hassle of managing several very similar templates, and with a very intuitive grouping of the different articles in the site tree.

If you display teasers you might want to display teaser images as well. However the default teaser templates do not include this option. So we need to tweak them a bit.

You find the teaser templates in the folders for the different datatypes in the webskin folder. They all have file names starting with displayTeaser.

As an example lets look at one of the teaser templates for news (slightly abreviated code to save space and focus on the topic): webskin/dmNews/displayTeaserFeature.cfm

Now let us say that we want to display teaser images as well. And we'll have the teaser images float to the right of the teaser text.

First you might want to do a cfdump of the stObj. Here you'll find that there is a value called stObj.teaserimage, but however this is not the name of a image file as you might expect. It holds a UUID for the image object that is the teaser image.

What we will do is use the q4 library that is a part of FarCry to get the necasary information from the image object.

Here's the code:

At the top we import the q4 library. Then within the paragraph holding the teaser text, we check if there is a UUID value for a teaser image. If so we pass the UUID to a q4 method called contentobjectget. We then get all the needed properties of the image object back. Here we use imagefile and alt, but you can try to cfdump getObject to see all properties available.

Now you have no excuse for not getting some more pictures into your FarCry solutions ;)

Happy FarCry'ing

In the last FarCry post I linked to another post about configuring TinyMCE in FarCry. However most of the time I find that I use TinyMCE like it works right out of the box. It will use the same stylesheet that is configured for the site itself, so the formating you see in TinyMCE will pretty much be the same as on the site.

The only little problem with this is if you in your css have specified a background color or image for body. For example you have a black background for the site, but the content is black text in a div with a white background.

Now what happens is that TinyMCE will use the black background from the body as a background in the editor window.

The solution is quick and easy. In your css include the follwing code:

Happy FarCry'ing