TIP RenderPlugin is not installed on Foswiki.org.


Render WikiApplications asynchronously


This plugin implements three simple REST handlers to get content from Foswiki. For example, these can be used to easily replace a server-side INCLUDE with a functional equivalent using an ajax call to one of these REST handlers.

This comes in handy to asynchronously load content in a tabbed interface, loading subsequent content for a treeview, a menu widget, or tooltips.

You may also use it to just render a snippet of TopicMarkup on the server and return a HTML preview back to the browser.

The REST handlers of this plugin have been designed to be rather generic. So, besides some very basic parameter checking, most error handling is up to the callback analysing the return value of the REST handler. The main purpose is best described as being an intermediate transport device.

Compare this to other plugins that implement more specific REST handlers. As such, they are rather tailored to one specific service and thus will be dealing with error cases on the server side in much more detail.

The advantage of using this plugin's REST handler is that you don't have to implement service backends using perl. Instead, you can write TopicFunctions that contain the WikiApplication to be executed when it is called by an appropriate ajax request. This basically is the client side equivalent of a parametrized INCLUDE, as it is used on server side WikiApplications (see examples below).


The available REST handlers are:

Handler Parameters Description
expand text expands common variables in the submitted text fragment
render text same as expand but also renders TopicMarkup converting it to HTML
tag name,
this is a convenience function to expand one specific variable instead of having to build up a snippet of code that you want to expand or render; The param parameter specifies the default parameters to this tag; the named-params are additional named parameters; the render flag indicates if the result is to be expanded only or if it should be renderd into HTML; default is off, that is only expand common tags but don't interpret TopicMarkup
template name,
this handler loads the template name and expands the macro given in expand; the render flag indicates whether the result is to be rendered in addition to common tags being interpreted
jsonTemplate name,
, expand,
same as template handler, but returns a json object holding css and js zones required to properly format the template; used via foswiki.loadTemplate()


The REST handlers are called like this:
%SCRIPTURLPATH{"rest"}%/RenderPlugin/render?text=%ENCODE{"This is _very_ cool."}%

(equivalent to a %INCLUDE{"Applications.RenderWebTagCloud" search="screenshot"}%)

This can be schedule using jQuery like this:
<div id="container"></div>

jQuery(function($) {


Fetching a message

*Hello World!* :)

Previewing TML

Okay, your turn to create an example calling SEARCH.

Installation Instructions

You do not need to install anything in the browser to use this extension. The following instructions are for the administrator who installs the extension on the server.

Open configure, and open the "Extensions" section. Use "Find More Extensions" to get a list of available extensions. Select "Install".

If you have any problems, or if the extension isn't available in configure, then you can still install manually from the command-line. See http://foswiki.org/Support/ManuallyInstallingExtensions for more help.

Plugin Info

Change History:  
31 Aug 2015: implemeted JSON-Template REST handler
04 Apr 2014: flag rest handlers that don't require authentication
18 Mar 2014: removed duplicate http header from render rest handler
01 Nov 2013: added support for contenttype url parameter
10 Jan 2012: some docu fixes
12 May 2009: added template handler
24 Apr 2009: converted to foswiki plugin
07 Jan 2009: added upload rest handler; fixes for foswiki and FastCGIContrib
11 Jul 2008: initial version
Topic revision: r14 - 31 Aug 2015, MichaelDaum - This page was cached on 09 Oct 2015 - 03:12. Get a fresh version here.
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License