Configuration

Last modified by Vincent Massol on 2016/02/04 16:18

Once you have XWiki installed you'll want to configure it. Configuration can be done in 2 ways:

  • by stopping the XWiki instance and editing either the xwiki/WEB-INF/xwiki.cfg file or the xwiki/WEB-INF/xwiki.properties one, and then restarting XWiki. Note that xwiki.cfg was the historical file containing the configuration option but we're moving away from it and in due time all the XWiki configuration options will be found in xwiki.properties
  • by logging in as a user with admin rights and going to the administration page using the top level menu. You can also go directly to http://localhost:8080/xwiki/bin/admin/XWiki/XWikiPreferences. This allows to keep the server running while making the changes.
    • Some configurations are only accessible from the xwiki.cfg and xwiki.properties files and have no equivalent on the administration page.
    • If you're a developer and need to understand how Configuration works in XWiki, check the Configuration Module Documentation.
    You can verify some basic settings of your XWiki installation (on Tomcat, MySQL) using the Check Config and Indexes application.

There are various things you can configure:

Enable superadmin account

Edit the xwiki.cfg file and enable the xwiki.superadminpassword property. For example:

# Enable to allow superadmin. It is disabled by default as this could be a security breach if
# it were set and you forgot about it.
xwiki.superadminpassword=system

When logging in, the username will be "superadmin" and the password will be the one you set in the xwiki.superadminpassword property.

Language settings

To define the default language for your wiki go to the administration page, click on "Localization", locate the "Default Language" field and enter the language code for the language you wish to use. For example: "en" for English, "fr" for French, "de" for German, etc.

In addition you can configure your wiki to be multilingual. See the I18 user page for more information.

Last, you can also force your wiki to display only in one of the languages specified in the settings, by editing your WEB-INF/xwiki.cfg file. Search for the "Internationalization" section, and you should see two commented settings that you can uncomment and set to 1:

#-# By default, XWiki chooses the language specified by the client (browser) in the Accept-Language HTTP header. This
#-# allows to use the default language of the wiki when the user didn't manually choose a language.
# xwiki.language.preferDefault=0

#-# Force only one of the supported languages to be accepted.
# xwiki.language.forceSupported=0

Date format

To define the date format used in the interfaces, go to Wiki -> Administer Wiki -> Localization, locate the "Date format" field and enter the date format you wish to use. Examples:

FormatResult
MMMM dd, HH:mmJanuary 27, 12:27
yyyy/MM/dd, HH:mm2009/01/27, 12:27
dd/MM/yyyy, HH:mm27/01/2009, 12:27

More information about date formatting.

Enabling/Disabling Statistics

To disable the Statistics feature edit your xwiki.cfg file and replace the following properties as shown here (to enable statistics, change 0 to 1):

xwiki.stats=0
xwiki.stats.default=0

where:

  • xwiki.stats controls whether statistics are on or off
  • xwiki.stats.default controls whether statistics are on or off by default for the current Wiki. This is useful in Virtual Wiki mode. A wiki can decide whether statistics are on or off by setting the "statistics" field in XWiki.XWikiPreferences. If no such field is defined then the default value xwiki.stats.default is used.

    There's currently no UI to set the statistics on or off for a given subwiki. Thus at the moment you'll need to do 2 things:

    • Edit XWiki.XWikiPreferences to add a new boolean property to the class, by going to http://localhost:8080/xwiki/bin/edit/XWiki/XWikiPreferences?editor=class
    • Set the statistics property to true by going to http://localhost:8080/xwiki/bin/edit/XWiki/XWikiPreferences?editor=object and setting the statistics property to true

Optional Store Features

Document versioning

One of the key features of a wiki engine is the ability to keep all the history of a document, giving users the ability to see the evolution of a document, but also to revert changes. However, the history of an active wiki continuously grows and is usually much larger than the current version of the data. It is possible to disable the versioning feature in XWiki, which means that less storage space will be used, although it will not be possible to revert the document in case of vandalism.

To disable versioning edit xwiki.cfg and add xwiki.store.versioning=0.

Attachment versioning is also available and turned on by default.

Document recycle bin

By default deleted documents are not permanently removed, but are placed in a recycle bin, from which they can later be removed or restored. To disable it, edit xwiki.cfg and add xwiki.recyclebin=0.

Disabling the recycle bin will make it impossible to restore a deleted document, unless a database backup is available.

By default, a deleted document can be permanently deleted right away by administrators, and after 7 days by regular users. To change these limits, edit xwiki.cfg and add:

# Admins must wait 3 days before being allowed to permanently delete
xwiki.store.recyclebin.adminWaitDays=3
# Normal users must also wait 3 days
xwiki.store.recyclebin.waitDays=3

Attachment recycle bin is similar.

Customizing the Skin

See the Skin Guide.

Security configuration

See the Security Guide.

If the users will be accessing XWiki using SSL (https) then you will have to change the way links are created so that external links do not redirect users back to the http page. This is accomplished by setting the xwiki.url.protocol property in xwiki.cfg.

Customizing Menus

The first thing to understand is that menus depend on the skin you're using. If you're using the 1.0 skin it's likely you're using the Panels Application to provide the different menu panels you see on the left or right of your wikis. Check the Panels Application to know more on how to configure/modify them.

Encoding

See the Encoding Guide.

User Authentication

See the Authentication Guide.

Customizing the Verified Registration Page (Since 2.2M2)

The Verified Registration Page is part of the Administration Application and allows you to require users to fill in a captcha and validates user input on both the server side and the client side using Javascript. The configuration allows you to add fields and validation constraints to the fields which are there.

Since version 2.3M1 in order to turn on captcha you simply go to the administration page, click "Registration" and you will find a checkbox for turning on captcha along with other registation page related settings.

For more information about configuring the registration page you can visit the page on the Administration Application.

Initial Groups

You can set the default groups which new users will automatically be added to by changing the xwiki.users.initialGroups parameter in your xwiki.cfg file. To make all new users be added to the groups XWiki.CoolPeople and XWiki.CommunityMembers you will have to set the initialGroups parameter like this:

xwiki.users.initialGroups=XWiki.CoolPeople, XWiki.CommunityMembers
  • Current members will not be automatically be added to these groups, only new members.
  • The groups have to be created before being specified as initial groups.

Logging

See the Logging page.

Configuring Interwiki links

Interwiki linking is a short hand syntax for linking to pages on other websites. For example, you could link to http://en.wikipedia.org/wiki/InterWiki just by typing [[InterWiki@WikiPedia]].

Note that different lists have to be maintained to support this function in XWiki Syntax 1.0 and 2.x.
The link notation for Interwiki links has changed in XWiki Syntax 2.1. Links should look like this in XWiki Syntax 2.1: [[interwiki:WikiPedia:InterWiki]].

Interwiki links (XWiki Syntax 1.0)

Since XWiki renders wiki syntax using the Radeox engine, it supports Interwiki links in much the same way as SnipSnap

To configure Interwiki links on your wiki:

  • Create a file named [location from where you start your container]/conf/intermap.txt
  • Fill intermap.txt with content like:
    IMDB http://us.imdb.com/Title?
    OpenWiki http://openwiki.com/?
    SourceForge http://sourceforge.net/
    TWiki http://twiki.org/cgi-bin/view/
    Why http://clublet.com/c/c/why?
    Wiki http://c2.com/cgi/wiki?
    WikiPedia http://www.wikipedia.com/wiki/
    You can of course add your own entries.
Radeox's parser for intermap.txt is very fragile. A blank line at the bottom of the file is enough to make it fall over.

Restart XWiki (you'll need to restart XWiki every time you change intermap.txt) and try out an Interwiki link. If it does not work, check your xwiki.log file. You'll see if conf/intermap.txt could not be found, or if there was an error parsing it.

Interwiki links (XWiki Syntax 2.x)

In order to use Interwiki links in the XWiki Syntax 2.x it is necessary to configure the appropriate list in your xwiki.properties file. Look for the following section:

#-# [Since 2.5M2]
#-# InterWiki definitions in the format alias=URL
#-# See http://en.wikipedia.org/wiki/Interwiki_links for a definition of an InterWiki link
# Some examples:
# rendering.interWikiDefinitions = wikipedia = http://en.wikipedia.org/wiki/
# rendering.interWikiDefinitions = definition = http://www.yourdictionary.com/

Setting the default editor to use (Wiki or WYSIWYG)

Starting with XWiki Enterprise 3.0, which introduced a revamp of the Administration, you can choose the default editor from "Configuration > Edit Mode Settings" (see below):

DefaultEditorStarting30.png

Configure the WYSIWYG editor

See WYSIWYG Editor Configuration page to find out how you can enable or disable editing features.

Link URLs

With parameters, you can specify what type of links will be made by XWiki.

Reverse proxy setup

XWiki can and does run behind reverse proxies such as Apache mod_proxy. Usually the only thing needed is to have the x-forwarded-host http header set to the external URL and XWiki will write links correctly.

Some reverse proxy software does not set this header and with XWiki Enterprise 3.0M3 or newer, you can use the xwiki.home parameter in single wiki instances (non farm) to achieve the same result.

  • xwiki.home - parameter in xwiki.cfg will be used to make all links pointing to the main wiki on the server. If your main wiki is called "xwiki" but you want your users to access it by going to www.yoursite.tld instead of xwiki.yoursite.tld, you may set the xwiki.home parameter to http://www.yoursite.tld/
    Since XWiki Enterprise 3.0M3, this parameter will also work for single wiki instances and will be the final authority if the x-forwarded-host parameter is not set.
  • xwiki.url.protocol - with the xwiki.url.protocol parameter in xwiki.cfg you can explicitly specify the protocol as https. This is useful if you are running xwiki behind a reverse proxy which converts https into plain http so xwiki only sees http.

Short URLs

It's possible to configure XWiki to use shorter URLs.

Configure the names of database schemas

Since 1.6M1 Sometimes, especially in enterprise environment, we need to control the names of database schemes, other than default.

  • xwiki.db: name of database schema for the main wiki (including the name of the wiki in a non-virtual environment, otherwise the database name comes from the hibernate configuration file).
  • xwiki.db.prefix: useful mainly for virtual wikis, where we have a separate database schema for each virtual wiki. This prefix is added to the database schema name after usual mapping between wiki names and schemas. Note that this is also applied to the main wiki database name.

Turning off comments or attachments

You need to change the XWiki.XWikiPreferences class like this:

  • Go to <server>/xwiki/bin/edit/XWiki/XWikiPreferences?editor=class
  • Add a new property called showcomments (or showattachments for turning off attachments) of type String Class 
  • Go to <server>/xwiki/bin/edit/XWiki/XWikiPreferences?editor=object&classname=XWiki.XWikiPreferences and write no in the showcomments (or showattachments) field

That's it, the comments (or attachments) are gone. If you want to re-enable them, replace the "no" value with "yes".

If you wish to turn off comments/attachments/history/information tabs only for a single page you just need to define some properties in a script in the page.

Last, if you wish to turn them off based on some programmatic rule (such as display them only for Administrators), you should define the properties in the layoutExtraVars.vm template file from your XWiki installation. For example:

#if (!$hasAdmin)
  #set($docextras = [])
#end

Configure "Version Summary" behavior

When you're editing a page you can add a brief description of your changes in the "Version Summary" field by default (look at PageEditing). You can disable this feature by setting xwiki.editcomment=0 in xwiki.cfg.

When the "Version Summary" feature is enabled, you can also set "Version Summary" to be mandatory by setting xwiki.editcomment.mandatory=1 in xwiki.cfg. This will show a popup window with the request to write a short comment if there is no comment entered. It doesn't allow you to enter an empty comment. If you want a popup, but you also want to be able to enter an empty comment, set xwiki.editcomment.suggested=1 in xwiki.cfg

If you set "Version Summary" as mandatory or suggested, you can also remove the "Version Summary" field and use only a popup window for writing a comment. Set xwiki.editcomment.hidden=0 in xwiki.cfg to do this.

You can use the special fields in the XWikiPreferences object instead of editing xwiki.cfg. These fields are: editcomment, editcomment_mandatory, editcomment_suggested and editcomment_hidden.

Configuring Directories

XWiki uses a temporary directory to cache images after re-sizing them or store attachments after loading them out of the database. It also uses a permanent directory for storing data such as filesystem attachments which must not be deleted and search indexes which are replaceable but laborious to create.

If there is no configured persistent directory, XWiki will use the temporary directory and log a warning on startup.

Since XWiki Enterprise 4.1M2 the temporary files will be placed in a special sub-directory of the temporary directory called xwiki-temp. This directory is periodically cleaned and all its content deleted so it is critical that it is not used for anything else.

To set the permanent directory, you have 2 options:

  • Set the xwiki.data.dir system property when starting the JVM (ie. the Servlet Container's JVM, specifically: -Dxwiki.data.dir=...)
  • Set the environment.permanentDirectory property in your xwiki.properties file

If the location points to a file or a directory to which XWiki does not have access, a warning will be printed in the log and the temporary directory will be used as a default.

The temporary directory is taken from the Servlet Container's javax.servlet.context.tempdir Servlet Context property and thus must be configured at that level. If it is pointed to a file or directory where XWiki cannot write, it will print a warning in the log and attempt to use java.io.tmpdir. If this is not a writable directory, an exception will be thrown.

Configuring WebDAV (since 1.7)

WebDAV support has been added to XWiki beginning with XWiki Enterprise 1.7. It is very important to note that WebDAV is enabled by default.

Securing WebDAV Server

XWiki's WebDAV implementation only supports the Basic Access Authentication scheme for authenticating WebDAV clients. Because of this reason it is highly recommended that you employ a transport level security mechanism like SSL to protect your clients. You may consult your web application container's documentation to see how this can be achieved.

Disabling WebDAV

To disable WebDAV support in your XWiki server, simply edit your web.xml file and remove the url-mapping element for mapping webdav requests. The url-mapping element for WebDAV looks like this:

<servlet-mapping>
<servlet-name>webdav</servlet-name>
<url-pattern>/webdav/*</url-pattern>
</servlet-mapping>

Redirections

XWiki supports defining redirections for incoming requests. To activate this feature modify your xwiki.cfg file and set the following property: xwiki.preferences.redirect=1.
Then for each redirection you want to add, add a XWiki.GlobalRedirect object to your main wiki's XWiki.XWikiPreferences document. The XWiki.GlobalRedirect object has 2 fields: pattern and destination. The URL received is matched on pattern and if there's a match it's replaced with the value from destination. XWiki then redirects to the new URL.

Customizing the PDF export Look & Feel

In the future we'll want to rewrite the PDF/RTF exports as renderers in the new Rendering Module architecture. When this happens this section will be upgraded.

Here's how the PDF and RTF exports currently work:
XWikiExport201010290119.png

As shown in the diagram you can customize 4 parts:

  • The templates, pdf.vm and the referenced subparts, pdfhtmlheader.vm, pdfheader.vm, pdffooter.vm, pdftoc.vm, pdfcover.vm, which can be overridden by a copy located in a custom skin
  • The CSS used to render the content as PDF/RTF. There is no pdf.css by default. It could be created in /templates or in a skin; a copy in a skin, override the one located in /templates
  • The XHTML2FO XSL transformation. The default one, xhtml2fo.xsl, is packed in core jar.
  • The FOP XSL transformation. The default one, fop.xsl, is also packed in core jar.

After the export request triggers XWiki ExportAction, the content of your document is parsed by Velocity to get the initial XHTML content. JTidy, a HTML/XHTML syntax checker and pretty printer, will clean the initial XHTML to make it XHTML compliant. No customization is possible in this step.

In order to provide your own customization you need to start by tweaking the default templates (they can also be copied to a new skin) and/or by creating a new XWiki Class. To do that simply create a new page called XWiki.PDFClass and edit it in class mode (for ex. http://yourserver.com/xwiki/bin/edit/XWiki/PDFClass?editor=class). Add the following "Text Area" properties as needed (they are all optional so you only need to define the ones you need to use):

  • style: contains the CSS information that will overwrite or complement the default pdf.css values if they exist. css4j, a CSS API implementation for the Java&trade platform, will take care of this
  • xhtmlxsl: contains the XHTML to FO XSL overriding the default one. It is processed by Apache Xalan, a XSLT processor for transforming XML documents into HTML, text, or other XML document types. Since version 3.0M2 (see issue XWIKI-5918) this field needs to be the actual content of the customized xhtml2fo.xsl. Note that you can also use velocity in this field (useful to get the content of an attached .xsl file, which comes in very handy when you need to fill in a big file, since the limit of textarea properties is of 60 000 characters)
  • fopxsl: contains the FOP to PDF/RTF XSL overriding the default one. It is processed by Apache FOP.
The name of the class must be XWiki.PDFClass.

The good thing about fop/xsl-fo is that the xsl-fo document is independent of the final result. So we can export the wiki documents into many formats.

Then create a new page (say XWiki.PDFTemplate) and add the XWiki.PDFClass object to it.

Last use that page when calling the PDF/RTF export using the pdftemplate parameter as in http://yourserver/xwiki/bin/export/Space/Page?format=pdf&language=en&pdftemplate=XWiki.PDFTemplate.

No template is used by default.

As mentioned the style property stores CSS code. The field is parsed by the Velocity engine, so you can use the current color theme to style your PDF. For example:

#template('colorThemeInit.vm')
h2 {
  color: $theme.titleColor;
}

td {
  border-color: $theme.borderColor;
}

Override the PDF Templates

Customize the PDF Footer

By default, the PDF footer will display the page number, the last author and the date on which the last modification was performed. In order to also display a customized message, the template pdffooter.vm must be overridden. To do that, edit the skin class (e.g. http://yourserver/xwiki/bin/edit/XWiki/XWikiSkins?editor=class) and add a "TextArea" object named pdffooter.vm:

OverridePDFFooter.png

After adding the pdffooter.vm you might want to edit it (clicking on it opens a detailed editor) and e.g. give it a "Pretty name". In this editor, also set the "Editor" property to "pure text" as otherwise the WYSIWYG-Editor will be used:

OverridePDFFooterEdit1.png

Next, edit the skin page (e.g. http://yourserver/xwiki/bin/edit/XWiki/DefaultSkin?editor=object) and add the following code to the pdffooter.vm property:

$msg.Page <span class="page-number"></span> - $msg.get('lastmodifiedby')
$xwiki.getUserName($tdoc.author, false)
$msg.get('lastmodifiedon')
$!xwiki.formatDate($tdoc.date)
<div>
<p>CustomName SAS. All rights reserved. Confidential and proprietary document. Printed Copies are not controlled.</p>
</div>

To see the changes, just export any wiki page:

OverridePDFFooterFinal.png

Customize the PDF Cover

This could be useful when you want for instance to add the company's logo to the PDF cover. In order to do this, the template pdfcover.vm must be overridden. Just like for the PDF header, a "TextArea" property named pdfcover.vm must be added to the XWiki.XWikiSkins class (e.g. http://yourserver/xwiki/bin/view/XWiki/XWikiSkins?editor=class).

OverridePDFCover.png

Next, edit the skin page (e.g. http://yourserver/xwiki/bin/edit/XWiki/DefaultSkin?editor=object) and add the following code to the pdfcover.vm property:

<img src="$xwiki.getSkinFile("logo.png")"/>

<div style="text-align: center; width: 100%;">
<h1>
#set($title = "$!pdfdoc.display('title', 'rendered')")
#if($title == '')
  $escapetool.xml($!doc.displayTitle)
#else
  $escapetool.xml($title)
#end
</h1>
<br />
<br />
$!xwiki.getUserName($tdoc.author, false)
<br />
$!xwiki.formatDate($tdoc.date)
</div>

The last step consists of attaching the image "logo.png" to the skin:

OverridePDFCoverFinal.png

Override the CSS rules

In order to use your own template when exporting a page as PDF, you need to create a class in the XWiki space and name it PDFClass. Next, edit the page in "Class" mode (e.g. http://yourserver/xwiki/bin/edit/XWiki/PDFClass?editor=class) and add the following TextArea properties:

  • style which contains the CSS rules that will override the default pdf.css values; by default, there won't be a pdf.css file on your filesystem, but you can create it in the folder \webapps\xwiki\templates\ or specify it in your skin page
  • xhtmlxsl which contains the XHTML2FO XSL transformation that will override the default one
  • fopxsl which contains the FOP XSL transformation that will override the default one

CreatePDFClass.png

Then, create the wiki page for which your want to customize the PDF export (e.g. XWiki.PDFTemplate) and add a "XWiki.PDFClass" object to it.

Supposing your wiki page contains a table, you have to edit it in "Wiki" mode and add a style parameter as shown below:

(% class="mytable" %)
|=Column 1|=Column 2
| data|data

Next, edit the page in "Objects" mode and write your own CSS rules in the "style" property:

CreatePDFTemplate.png

Because no template is used by default, you need to specify the pdftemplate parameter in the URL in order to use your own template: http://yourserver/xwiki/bin/export/XWiki/PDFTemplate?format=pdf&pdftemplate=XWiki.PDFTemplate.

CustomizedPDF.png

Even though RTF export is expected to work the same way, there are still some isues to be solved affecting how CSS properties control the final layout.

Override the xhtml2fo.xsl rules

As explained above, the entire code of xhtml2fo.xsl needs to be copied in the xhtmlxsl textarea and then customized.

For example, to disable the generation of clickable URLs in the PDF, modify the follwing section:
   <xsl:template match="html:a[@href]" mode="transform">
       <fo:basic-link xsl:use-attribute-sets="a-link">
           <xsl:call-template name="process-a-link"/>
       </fo:basic-link>
   </xsl:template>

as
   <xsl:template match="html:a[@href]" mode="transform">
       <fo:inline>
           <xsl:call-template name="process-a-link"/>
       </fo:inline>
   </xsl:template>

Configuring Wiki Syntaxes and default Syntax

Starting with XWiki Enterprise 1.6 it's possible to configure the Wiki syntaxes that are available to the user. To do so edit the WEB-INF/xwiki.cfg file and configure the xwiki.rendering.syntaxes property. It's a comma-separated list of syntax ids. For example:

xwiki.rendering.syntaxes = xwiki/1.0, xwiki/2.0, confluence/1.0, jspwiki/1.0, creole/1.0, mediawiki/1.0, xhtml/1.0, twiki/1.0

In addition starting with XWiki Enterprise 1.8 it's possible to set the default syntax to be used when creating new documents. To do so edit the WEB-INF/xwiki.properties file and configure the core.defaultDocumentSyntax property. For example to use XWiki Syntax 2.0 by default:

#-# Specifies the default syntax to use when creating new documents.
#-# Default value is xwiki/1.0.
core.defaultDocumentSyntax = xwiki/2.0
Hint: If it doesn't work check that you've edited the correct configuration file.

Title behavior

The following configuration parameters (found in xwiki.cfg) can be used to control title behavior:

#-# Defines whether title handling should be using the compatibility mode or not. When the compatibility
#-# mode is active, if the document's content first header (level 1 or level 2) matches the document's title
#-# the first header is stripped.
xwiki.title.compatibility=1

#-# Defines the maximum header depth to look for when computing a document's title from its content. If no header
#-# equal or lower to the specified depth is found then the computed title falls back to the document name.
#-# The default value is 2.
# xwiki.title.headerdepth=2

#-# Defines if setting the title field must be mandatory in the WYSIWYG and Wiki editors. It is mandatory when this
#-# property is set to 1. The default value is 0 (not mandatory).
# xwiki.title.mandatory=0

Link Label Generation

Starting with XWiki Syntax 2.0 it's possible to configure how labels are generated by the system when the user doesn't provide one (e.g. WebHome).

Her's an extract from the xwiki.properties file which is where this feature is configurable:

#-# [Since 1.8RC2]
#-# Specifies how links labels are displayed when the user doesn't specify the label explicitely.
#-# Valid values:
#-#   %w: wiki name
#-#   %s: space name
#-#   %p: page name
#-#   %P: page name with spaces between camel case words, i.e. "My Page" iff the page name is "MyPage"
#-#   %t: page title
#-#
#-# Note that if the page title is empty or not defined then it defaults to %p. This is also the case
#-# if the title cannot be retrieved for the document.
#-#
#-# The default is "%p". Some examples: "%s.%p", "%w:%s.%p".
# rendering.linkLabelFormat = %p

Rendering Cache

See the Performance page.

Allowed Pages for Inactive Users

The xwiki.cfg configuration file includes a property called xwiki.inactiveuser.allowedpages. This property can be used to build a whitelist of pages that can be read by inactive users. The format that should be used is a comma-separated list of pages that users that are marked as inactive are allowed to see.

This property is needed due to the fact that in XWiki, some users can be marked as inactive, for example when enabling user email verification in the administration. An inactive user has an account, but the account needs to be validated in order for the user to be able to access the wiki. Access rights do not apply to inactive users (they are recognized neither as XWikiGuest nor as members of XWikiAllGroup).

Inactive users are always allowed to see the XWiki.AccountValidation page in order to validate their account.

Rendering Transformations

You can control which Transformations are active (by default the Macro and Icon ones are active by default) by editing xwiki.properties:

#-# [Since 2.6RC1]
#-# Controls what transformations will be executed when rendering content.
#-# A transformation modifies the parsed content. For example the Icon transformation replaces some characters with
#-# icons, a WikiWord transformation will automatically create links when it finds wiki words, etc.
#-# Note that the Macro transformation is a special transformation that replaces macro markers by the result of the
#-# macro execution. If you don't list it, macros won't get executed.
#-# The default value is: rendering.transformations = macro, icon

For example if you wish to turn off the Icon Transformation in order to not render emoticons, you'd have to define the following property: rendering.transformations = macro.

Securing Groovy Scripts

See:

Sample xwiki.cfg

See xwiki.cfg.vm

Note that we generate the default xwiki.cfg file from this template file by applying Velocity on it during the build, so all $<something> properties that you see in this file are replaced at build time.

Sample xwiki.properties

See xwiki.cfg.vm

Note that we generate the default xwiki.cfg file from this template file by applying Velocity on it during the build, so all $<something> properties that you see in this file are replaced at build time.

Tags:
Created by VincentMassol on 2007/11/16 12:18
    

Get Connected