showaction in the
blogcontroller, for example, Wheels will include the
.cfmfile named after the action.
.cfmfile in the controller's view folder).
templateargument, there are specific rules that Wheels will follow in order to locate the file you want to include:
/character, Wheels will start searching from the root of the
renderView(template="/common/page")will include the
/character elsewhere in the string, the search will start from the controller's view folder. Example:
renderView(template="misc/page")will include the
views/blog/misc/page.cfmfile if we're currently in the
/character at all), Wheels will just assume the file is in the controller's view folder and try to include it. Example:
renderView(template="something")will include the
views/blog/something.cfmfile if we're currently in the
renderView(template="thepage.cfm")work fine. But most of the time, Wheels developers will tend to leave out the
variablesscope if you prefer to set it explicitly) in the controller so that they are available to the view template.
paramsstruct. This contains anything passed in through the URL or with a form. If you want to follow MVC rules more closely though, we recommend only accessing the
paramsstruct in the controller and then setting new variables for the information you need access to in the view.
titlecolumn from a query object called
posts, it should encode HTML special characters:
EncodeForHtmlAttributeinternally as needed.
encodeargument (can be set to
attributes) that overrides the global setting. Setting it to
attributeswill only encode HTML attribute values but leave tag content as is. Note that the
attributesoption is not available on functions that don't produce any tag content (such as imageTag for example), in those cases it's enough to pass in either