Skip to Content

Published

Fix the PDF export and XAR export URL documentation of the Exports topic

Last modified by Eleni Cojocariu on 2026/08/21 10:59

Reviews the administrator Exports topic against Documentation.AdminGuide.ImportExport revision 35.1 (the legacy page it was converted from) and against the platform sources at 18.7.0-SNAPSHOT. Four of the nine pages of the tree are in this change request; the rest are deliberately left out, see the end of this description.

Two documented things do not work. Both were checked by actually exporting from a running 18.4.3 instance and unzipping the result:

  • The export parameter is licence, not license. ExportAction reads the British spelling, matching the licence element of package.xml, so the documented &license=GPL is silently ignored and the archive carries no licence element at all. Verified: &licence=BRITISH-OK writes a licence element holding BRITISH-OK, &license=AMERICAN-IGNORED produces nothing.
  • Several Pages excluded from the same pages go into one excludes value, separated by %26. DocumentSelectionResolver pairs excludes[i] with pages[i] and splits that one value on & before decoding each piece, so the documented &excludes=A&B form makes B a stray parameter name and exports the Page. Verified against a 4-Page space exporting 35 XML files: one exclusion gives 22 files, excludes=Page1%26Page2 gives 20, and the documented excludes=Page1&Page2 gives 22, so only the first exclusion applied. The example with a Page name containing & needs that & double-encoded (%2526) on top of the %26 separator, which is now spelled out.

Two images never rendered on PDF Generator Configuration: the two reference values chrome-docker-container-generator and remote-chrome-generator omit the .png extension, so the whole "Image" column of the generator table was empty although both attachments exist under the right name.

Exports was a topic page that routed to half its tree and explained nothing:

  • It linked Export content in XAR format and Configure the PDF Export but never linked its two office children, Connect to an Internal Office Server and Connect to an External Office Server, which were reachable only from the user Exports hub and from the automatic "More" table.
  • Its first sentence did not link its Extensions-wiki page, which a topic page owes.
  • In place of "administrators have additional options", it now says what the difference actually buys: the XAR archive is the only format XWiki reads back on import, the Administration export interface selects Pages anywhere in the wiki rather than from the Page being viewed, and the other formats depend on a service that has to be configured before users are offered them.

Configure the PDF Export for XWiki Pages misstated the setting that matters most:

  • "Replace FOP" does more than change a label. The page said only that the label is "PDF" vs. "PDF (Web)". The setting is enabled by default (isReplacingFOP() returns true), and what it does is remove the old FOP export from the Export modal (export_modal.vm sets that entry's enabled to !isReplacingFOP()); disabling it labels the new export "PDF (Web)" and brings the old one back as "PDF (FOP)". Neither the default nor the disappearance of the old export was documented.
  • The defaults are stated for "Page Ready Timeout" (60 seconds) and "Maximum Content Size", where the page said "The default value is 5MB" about a field it had just described as being in kilobytes; the value is 5000 KB.
  • Typo discrad, and the two screenshots that carried an empty alt.
  • It had no result step, which a How-to owes: it ended on "Click on Save". It now ends on what the reader should see, the section reporting the settings saved, with a screenshot captured on a local 18.4.3 instance.
  • The FAQ entry "Is there any other way to configure the PDF generator?" was identical on this page and on its child PDF Generator Configuration. It is kept on the child, which is the page about generator configuration.

PDF Generator Configuration was a Reference page that sent the reader elsewhere for the reference: it documented "XWiki URI" in a closing paragraph and pointed at the Extensions-wiki PDF Export Application page for everything else. It now carries the six settings the admin section actually exposes as a table (which generator each belongs to, its default and what it is for), read from ConfigurationSheet.xml and DefaultPDFExportConfiguration: "Chrome Docker Image", "Chrome Docker Container Name", "Docker Network", "Chrome Host", "Chrome Remote Debugging Port" and "XWiki URI". The default Chrome image is described as a pinned tag without quoting the version, since it moves at every release. The generator is also renamed to its actual label, "Remote Chrome" rather than "Remote Chrome Generator", and the four empty alt attributes are filled in.

Customizations for XAR Export Using URL Parameters additionally gains the parameters it omitted and loses its mechanical defects:

  • description (ExportAction.java), verified to land in package.xml alongside author and version.
  • filter (DocumentSelectionResolver), which takes an EntityTreeFilter component hint and counts as a selection on its own. Only installedExtensionDocument is worth documenting: it excludes the Extension Pages that hold no nested content Pages, so it exports the content of the wiki. (pinnedChildPages, the other hint that ships, returns an empty set of descendant exclusions, which is all the export uses, so it does nothing here.)
  • history and backup are described as taking true rather than "if defined", since both are read with Boolean.parseBoolean.
  • name now says what the default name is (backup for a whole wiki, export otherwise).
  • The six table rows ending with a stray |, which added a fourth empty column to a three-column table, and the enitre typo, and the excludes example that had lost its monospace formatting.
  • The Technical ID was empty; it is now the Administration Application, matching its parent.

Technical IDs are prefixed on all four pages (xwiki:org.xwiki.platform:...). Unprefixed, the Extension badge at the bottom of the page does not resolve.

Deliberately not in this change request, each because it needs something this one cannot carry:

  • The two office How-tos (Connect to an Internal / External Office Server) need a restructure, not an edit: the same 40-line xwiki.properties block is on both, both open with the same two steps, and both already carry an automatic "more than 5 FAQ entries" warning. That is a separate change request.
  • Export Content in XAR format and both XAR Format Specifications pages are already rewritten by the open change request "Finish the XAR format documentation conversion", so touching them here would conflict.
  • The "does exporting replace a proper backup?" FAQ entry is verbatim on three hubs (administrator Exports, user Exports, Imports), and the "ODT and RTF need an office server" fact is now on both Exports hubs. Giving each one home spans three trees, so it needs its own change request rather than a partial fix here.
  • remote-chrome-generator.png is attached to two pages and is not referenced by the content of Configure the PDF Export for XWiki Pages. Deleting that copy is an attachment operation, not a file change.

All changes

Edition of Exports

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,13 @@
1 -Administrators have additional options for exporting Pages compared to regular users. [[Users can export>>documentation.xs.user.exports.export-page.WebHome]] in different formats, administrators can export also while viewing a Page having the additional option to export as [[##XAR## files>>documentation.xs.admin.exports.export-content-xar-format.format-specifications.WebHome]]:
1 +Administrators export wiki content from the [[Administration Application>>doc:extensions:Extension.Administration Application]], which adds to the [[formats every user can export>>doc:documentation.xs.user.exports.WebHome]] one format of its own and the settings that decide how the other formats are produced.
2 2  
3 -{{image reference="export-types-admins.png" size="large" alt="The Export modal showing for administrators also the XAR option as a format"/}}
3 +Two capabilities belong to administrators only:
4 4  
5 -Administrators also have access to a dedicated export interface from the Administration section. Compared to [[exporting while viewing a Page>>documentation.xs.user.exports.export-page.WebHome]], this interface provides more advanced configuration options. From there, they can [[Export content in ##XAR## format>>documentation.xs.admin.exports.export-content-xar-format.WebHome]] and [[configure the PDF export for XWiki Pages>>documentation.xs.admin.exports.configure-pdf-export.WebHome]].
5 +* [[Export content in ##XAR## format>>doc:documentation.xs.admin.exports.export-content-xar-format.WebHome]]. A [[##XAR##>>doc:documentation.xs.admin.exports.export-content-xar-format.format-specifications.WebHome]] archive is the only format XWiki reads back on [[import>>doc:documentation.xs.admin.imports.WebHome]], with the objects and attachments of each Page and, optionally, its history. The same export can be [[driven entirely from the URL>>doc:documentation.xs.admin.exports.export-content-xar-format.xar-customization-url.WebHome]].
6 +* The export interface of the Administration, which selects Pages anywhere in the wiki instead of starting from the [[Page being viewed>>doc:documentation.xs.user.exports.export-page.WebHome]].
7 +
8 +{{image reference="export-types-admins.png" size="large" alt="The Export modal of a Page, showing the XAR entry that only administrators are offered"/}}
9 +
10 +The remaining formats are produced by a service that has to be configured first, and a format whose service is missing is not offered to users at all:
11 +
12 +* ##PDF## always works, but [[configuring the PDF export>>doc:documentation.xs.admin.exports.configure-pdf-export.WebHome]] decides which templates users may choose from and, through the [[PDF generator>>doc:documentation.xs.admin.exports.configure-pdf-export.pdf-generator-configuration.WebHome]], whether the file is produced by the reader's own browser or server-side by a headless Chrome.
13 +* ##ODT## and ##RTF## need an office server, either by [[connecting to an internal Office Server>>doc:documentation.xs.admin.exports.connect-internal-office-server.WebHome]] or by [[connecting to an external Office Server>>doc:documentation.xs.admin.exports.connect-external-office-server.WebHome]]. Until one of them answers, [[exporting in ODT or RTF>>doc:documentation.xs.user.exports.export-page.export-odt-rtf.WebHome]] is unavailable.
DocApp.Code.DocumentationExtensionClass[0]
Technical Identifier
... ... @@ -1,1 +1,1 @@
1 -org.xwiki.platform:xwiki-platform-administration-ui
1 +xwiki:org.xwiki.platform:xwiki-platform-administration-ui

Edition of Configure the PDF Export for XWiki Pages

Summary

Details

Page properties
Content
... ... @@ -5,15 +5,18 @@
5 5  {{image reference="pdf-export-item.png" size="medium" alt="Content settings dropdown from the Administration user interface"/}}
6 6  )))
7 7  1. Check the state of the [[PDF Generator>>||anchor="HWhatisaPDFgenerator3F"]]. Depending on the Generator configured, the state can be "Available" or "Currently unavailable".(((
8 -{{image reference="status-pdf-export.png" size="large" alt=""/}}
8 +{{image reference="status-pdf-export.png" size="large" alt="The state of the PDF generator, displayed next to the Generator setting"/}}
9 9  )))
10 10  1. Select and configure the settings of the PDF export:(((
11 -{{image reference="configuration-pdf-export.png" size="large" alt=""/}}
11 +{{image reference="configuration-pdf-export.png" size="large" alt="The settings of the PDF Export administration section"/}}
12 12  
13 13  * "Templates": set the list of PDF templates that the users can select from on the [[PDF Export Options modal>>documentation.xs.user.exports.export-page.pdf-modal.WebHome]].
14 14  * "Generator": [[select and configure the PDF generator>>documentation.xs.admin.exports.configure-pdf-export.pdf-generator-configuration.WebHome]].
15 -* "Page Ready Timeout": set the page ready timeout, that is the number of seconds to wait for the web page to be ready for print before aborting the PDF export.
16 -* "Maximum Content Size": set the maximum content size, in kilobytes (KB), that can be included in a PDF export. This limit is taken into account only when exporting multiple wiki Pages. The default value is 5MB. Disable the maximum content size by setting its value to 0.
17 -* "Replace FOP": set whether to replace the old PDF export based on Apache Formatting Objects Processor (FOP) or not; the label displayed on the Export Modal depends on this setting: "PDF" vs. "PDF (Web)"
15 +* "Page Ready Timeout": set the number of seconds to wait for the web page to be ready for print before aborting the PDF export. The default value is ##60##.
16 +* "Maximum Content Size": set the maximum content size, in kilobytes (KB), that can be included in a PDF export. This limit is taken into account only when exporting multiple wiki Pages. The default value is ##5000##. Disable the limit by setting the value to ##0##.
17 +* "Replace FOP": set whether to replace the old PDF export based on Apache Formatting Objects Processor (FOP). It is enabled by default, so the export of this application is labelled "PDF" on the [[Export Modal>>documentation.xs.user.exports.export-page.modal.WebHome]] and the old export is not offered at all. Disabling it labels this export "PDF (Web)" and brings the old one back as "PDF (FOP)".
18 18  )))
19 -1. Click on "Save" to save the configurations, or exit the Page to discrad. You can also "Reset" the changes to the default.
19 +1. Click on "Save" to save the configurations, or exit the Page to discard. You can also "Reset" the changes to the default.
20 +1. Check that the section reports the settings saved. They apply to the whole wiki, so the next PDF export any user runs uses them:(((
21 +{{image reference="pdf-export-saved.png" size="large" alt="The bottom of the PDF Export administration section, with a Saved confirmation under the Save and Reset buttons"/}}
22 +)))
pdf-export-saved.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.elenicojocariu
Size
... ... @@ -1,0 +1,1 @@
1 +12.4 KB
Content
DocApp.Code.DocumentationExtensionClass[0]
Technical Identifier
... ... @@ -1,1 +1,1 @@
1 -org.xwiki.platform:xwiki-platform-export-pdf-ui
1 +xwiki:org.xwiki.platform:xwiki-platform-export-pdf-ui

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,22 @@
1 -When [[configuring PDF export>>documentation.xs.admin.exports.configure-pdf-export.WebHome]], you have the option to choose the tool to use for generating PDFs:
1 +When [[configuring PDF export>>documentation.xs.admin.exports.configure-pdf-export.WebHome]], the "Generator" setting chooses the tool that produces the PDF:
2 2  
3 -{{image reference="generator-dropdown.png" size="medium" alt=""/}}
3 +{{image reference="generator-dropdown.png" size="medium" alt="The Generator setting of the PDF Export administration section, expanded on its three choices"/}}
4 4  
5 5  |=The tool used as a PDF Generator|=Description|=Image
6 -|User Browser|This is the default setting, it generates the PDF using the user's web browser on the client side. The main advantage of this approach is that it doesn't require any external services (such as Docker or a remote headless Chrome). However, a downside is that different users, depending on their web browser or its version, may experience variations in the final PDF output|{{image reference="user-browser-generator.png" size="large" alt=""/}}
7 -|[[Chrome Docker Container>>extensions:Extension.PDF Export Application.WebHome||anchor="HChromeDockerContainer"]]|The PDF can also be generated on the server side using a headless Chrome web browser running inside a Docker container. The application automatically handles the following tasks:(((
8 -* Pulling the correct Docker image if it is not found locally.
9 -* Creating and starting the container if no existing container is available.
10 -* Stopping the container when XWiki shuts down, if the container was created by XWiki.
11 -)))|{{image reference="chrome-docker-container-generator" size="large" alt=""/}}
12 -|[[Remote Chrome Generator>>extensions:Extension.PDF Export Application.WebHome||anchor="HRemoteChrome"]]|If you don't want to rely on Docker, or you don't want to give XWiki access to Docker for security reasons, but you still want to perform the PDF export on the server side then you also have the option to connect to a remote Chrome instance. |{{image reference="remote-chrome-generator" size="large" alt=""/}}
6 +|"User Browser"|The default setting. The PDF is generated client-side, by the print function of the user's own web browser, so it requires no external service such as Docker or a remote headless Chrome. The drawback is that the final PDF varies with the browser each user runs, and with its version.|{{image reference="user-browser-generator.png" size="large" alt="The User Browser generator selected, with no further setting to fill in"/}}
7 +|"[[Chrome Docker Container>>extensions:Extension.PDF Export Application.WebHome||anchor="HChromeDockerContainer"]]"|The PDF is generated server-side, by a headless Chrome web browser running inside a Docker container on the same server as XWiki. The application handles the container itself:(((
8 +* pulling the Docker image if it is not found locally,
9 +* creating and starting the container if no existing container is available,
10 +* stopping the container when XWiki shuts down, if XWiki is the one that created it.
11 +)))|{{image reference="chrome-docker-container-generator.png" size="large" alt="The settings of the Chrome Docker Container generator"/}}
12 +|"[[Remote Chrome>>extensions:Extension.PDF Export Application.WebHome||anchor="HRemoteChrome"]]"|The PDF is generated server-side, by a Chrome web browser running on another host. Use it to keep the export server-side without relying on Docker, or without granting XWiki access to Docker.|{{image reference="remote-chrome-generator.png" size="large" alt="The settings of the Remote Chrome generator"/}}
13 13  
14 -For both the Chrome Docker Container and the Remote Chrome generators, you can specify the base URI that the remote (headless) Chrome browser uses to access XWiki when generating PDFs (in particular, the print preview page). The host (domain name or IP address) is required. The scheme (e.g., ##HTTP## or ##HTTPS##) and the port (e.g., ##8080##) are optional and, if not provided, default to the values from the URL used to trigger the export. This setting replaces the deprecated XWiki Host configuration (##export.pdf.xwikiHost##).
14 +Selecting one of the two server-side generators reveals its own settings:
15 +
16 +|=Setting|=Generator|=Default|=Description
17 +|"Chrome Docker Image"|"Chrome Docker Container"|a pinned ##femtopixel/google-chrome-headless## tag|The Docker image used to create the container running the headless Chrome. The default names an exact Chrome version rather than ##latest##, because a Chrome upgrade changes the layout of the PDFs it produces.
18 +|"Chrome Docker Container Name"|"Chrome Docker Container"|##headless-chrome-pdf-printer##|The name of the container running the headless Chrome. Set it to the name of a container you manage yourself to have XWiki reuse it instead of creating one.
19 +|"Docker Network"|"Chrome Docker Container"|##bridge##|The name or id of the Docker network the Chrome container is added to. Set it when XWiki itself runs inside a Docker container, so that the two containers can reach each other.
20 +|"Chrome Host"|"Remote Chrome"|empty, and required|The host running the headless Chrome, specified either by its name or by its IP address.
21 +|"Chrome Remote Debugging Port"|both|##9222##|The port number used for communicating with the headless Chrome.
22 +|"XWiki URI"|both|##host.xwiki.internal##|The base URI the headless Chrome uses to reach this instance, in particular the print preview Page. The host is required; the scheme (##HTTP## or ##HTTPS##) and the port are optional and fall back to the ones of the URL that triggered the export. This setting replaces the deprecated XWiki Host configuration (##export.pdf.xwikiHost##).
DocApp.Code.DocumentationExtensionClass[0]
Technical Identifier
... ... @@ -1,1 +1,1 @@
1 -org.xwiki.platform:xwiki-platform-export-pdf-ui
1 +xwiki:org.xwiki.platform:xwiki-platform-export-pdf-ui

Edition of Customizations for XAR Export Using URL Parameters

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -You can [[export content in XAR format>>documentation.xs.admin.exports.export-content-xar-format.WebHome]], but you can also trigger a XAR export by changing the URL of Pages. For example, replacing "/view/" with "/export/", and adding the parameter ##format=xar## will export the enitre wiki:
1 +You can [[export content in XAR format>>documentation.xs.admin.exports.export-content-xar-format.WebHome]], but you can also trigger a XAR export by changing the URL of Pages. For example, replacing "/view/" with "/export/", and adding the parameter ##format=xar## will export the entire wiki:
2 2  
3 3  {{code language="none"}}http://server/xwiki/bin/export/Space/Page?format=xar{{/code}}, where "Space" is considered to be the [[top-level Page>>doc:documentation.xs.user.base.page.nested-pages.relations.WebHome]] of a hierarchy.
4 4  
... ... @@ -13,13 +13,15 @@
13 13  
14 14  |=Parameter|=Description|=Example
15 15  |##pages##|Specifies the Pages to include in the export, using a pattern that matches Page names. You can use multiple Pages parameters, each representing a Page pattern.|##&pages=Main.%25## (Exports all Pages from the Main space)
16 -|##excludes##|Specifies the Pages to exclude from the export, using a pattern that matches Page names. You can use multiple Excludes parameters. All special characters must be encoded in the URL.|&excludes=Main.%25 (Excludes Pages from the Main space)|
17 -|##name##|Specifies the name of the exported XAR file. If not specified, a default name will be used. |##&name=CustomExport.xar##|
18 -|##history##|If defined, then also export the [[Page's history>>documentation.xs.user.base.page.view.view-history.history-tab.WebHome]].|##&history=true##|
19 -|##backup##|If defined, the XWiki Page [[author>>documentation.xs.user.base.page.authors.WebHome]] of each Page remains the same as when exported, when reimported into an XWiki instance.|##&backup=true##
20 -|##author##|Specifies the author's name in the XAR export, which can later be viewed when reimporting into an XWiki instance.|##&author=John Smith##|
21 -|##license##|Specifies the license for the XAR export, which can later be viewed when reimporting into an XWiki instance.|##&license=GPL##|
22 -|##version##|Specifies the version of the export to the XAR.|##&version=1.0##|
16 +|##excludes##|Specifies the Pages to exclude from the export, using a pattern that matches Page names. Each ##excludes## parameter applies to the ##pages## parameter in the same position, so use an empty ##excludes## to keep the order when only a later ##pages## has exclusions. Several Pages excluded from the same ##pages## go into a **single** ##excludes## value, separated by ##%26##; a Page name that itself contains the ##&## character is encoded ##%2526##.|##&excludes=Main.Space1.%25## (Excludes the Pages under the Main.Space1 space)
17 +|##filter##|Restricts the export to the Pages kept by an entity tree filter, named by its component hint. The hint to use is ##installedExtensionDocument##, which leaves out the Pages belonging to an installed [[Extension>>documentation.xs.admin.imports.extensions.WebHome]] that hold no nested content Pages, so that only the content of the wiki is exported. A filter counts as a selection on its own, and combined with ##pages## it applies to the patterns whose Page name is ##%25##.|##&filter=installedExtensionDocument##
18 +|##name##|Specifies the name of the exported XAR file. If not specified, ##backup## is used for a whole-wiki export and ##export## for a partial one.|##&name=CustomExport.xar##
19 +|##description##|Specifies the description of the XAR export, which can later be viewed when reimporting into an XWiki instance.|##&description=The offices of our company##
20 +|##history##|Set to ##true## to also export the [[Page's history>>documentation.xs.user.base.page.view.view-history.history-tab.WebHome]].|##&history=true##
21 +|##backup##|Set to ##true## to mark the archive as a backup package, so that the XWiki Page [[author>>documentation.xs.user.base.page.authors.WebHome]] of each Page remains the same as when exported, when reimported into an XWiki instance.|##&backup=true##
22 +|##author##|Specifies the author's name in the XAR export, which can later be viewed when reimporting into an XWiki instance.|##&author=John Smith##
23 +|##licence##|Specifies the license for the XAR export, which can later be viewed when reimporting into an XWiki instance. The parameter uses the British spelling, matching the ##licence## element of the [[##package.xml## descriptor>>documentation.xs.admin.exports.export-content-xar-format.format-specifications.WebHome]]; the American spelling is ignored.|##&licence=GPL##
24 +|##version##|Specifies the version of the export to the XAR.|##&version=1.0##
23 23  
24 24  Examples of how to use the parameters:
25 25  
... ... @@ -38,9 +38,9 @@
38 38  http://server/xwiki/bin/export/Space/Page?format=xar&pages=Main.%25&excludes=Main.Space1.%25&pages=Other.%25
39 39  {{/code}}
40 40  )))
41 -* Exports all Pages in the ##subwiki:Main## space except a Page named ##subwiki:Main.Excluded&Other## and ##subwiki:Main.WebHome##:(((
43 +* Exports all Pages in the ##subwiki:Main## space except a Page named ##subwiki:Main.Excluded&Other## and ##subwiki:Main.WebHome##. Both exclusions belong to the same ##pages## parameter, so they are one ##excludes## value joined by ##%26##, and the ##&## of the first Page name is encoded ##%2526##:(((
42 42  {{code language="none"}}
43 -http://server/xwiki/bin/export/Space/Page?format=xar&pages=subwiki:Main.%25&excludes=subwiki%3AMain.Excluded%26Other&subwiki%3AMain.WebHome
45 +http://server/xwiki/bin/export/Space/Page?format=xar&pages=subwiki:Main.%25&excludes=subwiki%3AMain.Excluded%2526Other%26subwiki%3AMain.WebHome
44 44  {{/code}}
45 45  )))
46 46  * Exports all Pages in the ##Main## space and all in the ##Other## space except ##Other.Excluded## (see the empty excludes for respecting the order):(((
... ... @@ -48,3 +48,8 @@
48 48  http://server/xwiki/bin/export/Space/Page?format=xar&pages=Main.%25&excludes=&pages=Other.%25&excludes=Other.Excluded
49 49  {{/code}}
50 50  )))
53 +* Exports the whole wiki without the Pages that came with an installed Extension:(((
54 +{{code language="none"}}
55 +http://server/xwiki/bin/export/Space/Page?format=xar&filter=installedExtensionDocument
56 +{{/code}}
57 +)))
DocApp.Code.DocumentationExtensionClass[0]
Technical Identifier
... ... @@ -1,0 +1,1 @@
1 +xwiki:org.xwiki.platform:xwiki-platform-administration-ui
Aug 21, 2026, 10:59:09 AM

Approved by Eleni Cojocariu

Approvers

Approvers have not been explicitly defined for this Change Request. Approvers will be based entirely on approval rights.

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected