Rules in FarCry are cool. Rules let you easily add dynamic content to a page, such as News or Events, simply by placing rules into a Container when you are viewing the site in Design Mode.

This example is very simple and makes use of FarCry 4's "Form Tools". The two cfproperty tags are all we need for FarCry to be able to deploy the appropriate table and fields to the database and to display and save the form when the user is editing the rule. Nice :) The only other required pieces of code are for the component to extend farcry.core.packages.rules.rules (or another rule that has already extended that component), and to implement a public function called execute() so that we can display something.

My ruleRecentlyUpdated.cfc rule simply does a query for dmHTML records whose status match the allowed options in request.mode.lValidStatus - i.e. if you are logged in and are in Draft Mode then Drafts will be included, otherwise it defaults to Approved page only - and sorts them in descending order using the datetimelastupdated field. It also makes use of a display method so that you can choose which display teaser you would like to use for output. See the sample code below...

ruleRecentlyUpdated.cfc (in /farcry/projectname/packages/rules)

<!--- $Developer: Justin Carter $ ---> <cfcomponent displayname="HTML Pages: Recently Updated" extends="farcry.core.packages.rules.rules" hint="Display the most recently updated HTML Pages"> <cfproperty ftseq="1" ftfieldset="General Details" name="displayMethod" type="string" hint="Display method to render." required="yes" default="displayTeaser" fttype="webskin" fttypename="dmHTML" ftprefix="displayTeaser" ftlabel="Display Method" /> <cfproperty ftSeq="2" ftFieldSet="General Details" name="numItems" type="numeric" hint="" ftLabel="Number of items" /> <cffunction access="public" name="execute" output="true"> <cfargument name="objectID" required="Yes" type="uuid" default=""> <cfargument name="dsn" required="false" type="string" default="#application.dsn#"> <cfparam name="request.mode.lValidStatus" default="approved"> <cfset stObj = this.getData(arguments.objectid)> <cfquery datasource="#arguments.dsn#" name="qGetPages" maxrows="#stObj.numItems#"> SELECT * FROM #application.dbowner#dmHTML WHERE status IN ('#ListChangeDelims(request.mode.lValidStatus,"','",",")#') ORDER BY datetimelastupdated DESC </cfquery> <cfif qGetPages.recordcount> <cfset arrayAppend(request.aInvocations,"<ul>")> <!--- loop over display methods ---> <cfloop query="qGetPages"> <cfscript> stInvoke = structNew(); stInvoke.objectID = qGetPages.objectID; stInvoke.typename = application.types.dmHTML.typePath; stInvoke.method = stObj.displayMethod; arrayAppend(request.aInvocations,stInvoke); </cfscript> </cfloop> <cfset arrayAppend(request.aInvocations,"</ul>")> </cfif> </cffunction> </cfcomponent>

displayTeaserRecentlyUpdated.cfm (in /farcry/projectname/webskin/dmHTML)

<cfsetting enablecfoutputonly="yes"> <!--- @@displayname: Recently Updated Pages (list) ---> <!--- @@author: Justin Carter ---> <cfimport taglib="/farcry/core/tags/webskin" prefix="skin"> <cfoutput> <li> </cfoutput> <skin:buildLink objectid="#stObj.objectid#"><cfoutput>#stObj.title#</cfoutput></skin:buildLink> <cfoutput> <span>#LSDateFormat(stObj.datetimelastupdated, "long")#</span> </li> </cfoutput> <cfsetting enablecfoutputonly="no">

* Note that I have only tested this with MS SQL, though I assume it will work with most other DB servers. Use this code at your own risk ;)

For my use case this was simply all I needed, however you could make a number of improvements to the functionality of this rule, such as:

• add a property to make the unordered list HTML tag optional
• select or exclude pages that are children of a particular navigation node
• select pages that belong to particular categories
• check pages that may be part of a members area that requires a login and include/exclude them as appropriate

If you want to look at rules, form tools and other stuff in more depth check out the FarCry 4 Developers Guide.

I've been a really hopeless blogger lately so I thought I'd kick things back into gear with some FarCry 4 goodness. FarCry 4 now uses TinyMCE for it's rich text editor and any customisations or editor replacements are done by extending richtext.cfc. This quick example just shows you how to change the configuration options of TinyMCE.

I wanted to specifically make changes to the HTML formatting output, HTML editor window, and default table attributes, but there is a whole lot more you can do with TinyMCE too - check out the TinyMCE Wiki for a full reference of configuration, button and plugin options.

In your project you will need to create a formtools folder inside /farcry/yourproject/packages, and create a file called richtext.cfc. This new component will extend farcry.core.packages.formtools.richtext and will override the getConfig() function - pretty straight forward really :)

Below is my sample richtext.cfc (use at your own peril, comments are welcome!)

<cfcomponent extends="farcry.core.packages.formtools.richtext" name="richtext" displayname="Rich Text Editor" hint="Used to liase with longchar type fields"> <cffunction name="getConfig" access="public" output="false" returntype="string" hint="This will return the configuration that will be used by the richtext field"> <cfset var configJS = "" /> <cfsavecontent variable="configJS"> <cfoutput> theme : "advanced", plugins : "table,advhr,farcrycontenttemplates,advimage,advlink,preview,zoom,searchreplace,print,contextmenu,paste,directionality,fullscreen,spellchecker", theme_advanced_buttons1_add : "pasteword,pastetext,separator,search,replace,spellchecker,separator,fullscreen", theme_advanced_buttons2_add : "separator,farcrycontenttemplates", theme_advanced_buttons3_add_before : "tablecontrols,separator", theme_advanced_toolbar_location : "top", theme_advanced_toolbar_align : "left", theme_advanced_path_location : "bottom", theme_advanced_resize_horizontal : true, theme_advanced_resizing : true, extended_valid_elements: "code,colgroup,col,thead,tfoot,tbody,abbr,blockquote,cite,button,textarea[name|class|cols|rows],script[type],img[style|class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name]", remove_linebreaks : false, relative_urls : false, <!--- customisations ---> content_css : "/css/tinymce-content.css", apply_source_formatting : true, fix_table_elements : true, remove_trailing_nbsp : true, theme_advanced_source_editor_width : "900", theme_advanced_source_editor_height : "700", <!--- customisations: table plugin ---> table_default_border: 0, table_default_cellpadding: 0, table_default_cellspacing: 1, verify_html : false </cfoutput> </cfsavecontent> <cfreturn configJS /> </cffunction> </cfcomponent>

After your new file is in place and has been saved you'll need to do an ?updateapp=1 for the new configuration to take effect. That should be all there is to it!