Search: concept

Documents listed here will ne copied in the new wiki but with overloaded contents that include the template wiki one ex : {{code}} #includeInContext("templatewiki:Space.Document") {{/code}} (% style="list-style-type: square" %) * documents to link in place of copy (not used yet) : same concept as include overload at copy but here with a real link.

But it works, and its a good proof of concept. If anyone is up to writing a cleaner, more efficient version - please do, and share.

. == Namespaces == Component API comes with "namespace" concept. The format of the namespaces is ##<type>:<id>##.

It's instantiated in the ##XWikiServletContextListener## class (in the ##xwiki-platform-container-servlet## module). == Accessing components in legacy code == The XWiki project is older that this component concept and sometimes you can find yourself in code which cannot really inject components, you should ideally try to convert it to the components world.

This means that Extension Manager will install all of them by default but optional dependencies won't have any impact on the validity of the extension: if the optional dependency install plan fail the extension is installed without it if the optional dependency is uninstalled it won't uninstall the extension if the optional dependency is missing at startup it won't make the extension invalid Managed dependencies Since 8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's element.

{{/info}} = Managed dependencies = Since 8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's {{code}}<dependencyManagement>{{/code}} element.

Applications of the discussions application dedicated to end users can be found in: * the [[discussions message stream application>>Extension.Discussions - Message Stream.WebHome]] * the [[ActivityPub Application>>Extension.ActivityPub Application]] {{/warning}} Discussions Macro is built on top of several modules that can be useful when integrating the discussions in a new context: * [[Extension.Discussions Server.WebHome]] * [[Extension.Discussions REST.WebHome]] = Concepts = == Discussion Context == A discussion context represents a context that can be linked to a discussion.

However, since Discussions 2.0 it's possible for the applications which relies on Discussions to configure where to store the different elements, and to dynamically chose the storage location. To do so, two concepts have been put in place: an ###applicationHint### must be used in the various API which defines the ###DiscussionStoreConfiguration### component that should be used.

. == Best Practices == * ((({{version since="11.3RC1"}}There's now the concept of a Syntax Registry and new Syntaxes are expected to register themselves in that registry.

It means that you will no longer find the "space" concept in the UI. Instead, each page has now the ability to have children pages, except if it is marked as "Terminal".

* **Query scripts:** scripts that will generate a list of documents that should be gardened based on a given concept. For example, a script fetching every document updated in the past X minutes

:) You will also need programming right to use wiki components and Groovy. The Concept Create a wiki page and transform it into a Wiki Component This Component will only serve as a way to define our Script Service or execute our script.

See the documentation on the [[Script Component>>doc:Extension.Script Component.WebHome]] extension page about how to achieve this. The general concepts explained on this page remain valid, though.

:) You will also need programming right to use wiki components and Groovy. = The Concept = * Create a wiki page and transform it into a Wiki Component * This Component will only serve as a way to define our Script Service or execute our script.

In addition, this macro introduces the concept of **children order** for a parent. However, the children order is used by default only by the hierarchy macro; if this order needs to be used in other places in the wiki as well, those places need to be customized to use this additional information introduced by the macro.