Search: concept

summary : Starting XWiki 10.4 we started to introduce the concept of [[page "Types">>extensions:Extension.XAR Module Specifications||anchor="Hpackage.xml"]]. * ((( Several ways to protect extension pages are now provided and can be configured in ##xwiki.properties##: {{code language="properties

description : Traditional wikis in which you can enter text and images are no longer the hype. You could even argue that traditional wikis are loosing traction or mindshare. Other concepts have arisen in the past such as CMS (Content Management System) and WCM (Web Content Management). However what user

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages. Summary There are 2 main use cases when you'd use a Wiki instead of Nested Pages: You want to provide custom Applications

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages. = Summary = There are 2 main use cases when you'd use a Wiki instead of Nested Pages: * You want to provide custom

content : These two versions introduce the concept of [[custom filters>>extensions:Extension.WikiLinkURLNormalizer.WebHome||anchor="HCustomfilters"]], allowing forcing conversions of some URLs into internal wiki links. This is useful for cases when URLs cannot be automatically recognized as pointing to internal links (e.g. ##https

extract : These two versions introduce the concept of [[custom filters>>extensions:Extension.WikiLinkURLNormalizer.WebHome||anchor="HCustomfilters"]], allowing forcing conversions of some URLs into internal wiki links. This is useful for cases when URLs cannot be automatically recognized as pointing to internal links (e.g. ##https

description : API to gather external news related to XWiki. The following concepts are used: * News Source Type: The type of source of news, in the form of a component hint. For example ##xwikiblog## represents an XWiki Blog Application news type (which means getting the news from the RSS feed generated

of installed applications to the "Flavors" concept. In XWiki, a flavor is simply a bundle of extensions

this new concept. For more informations, do not hesitate to check out [[Caty's blog post>>Blog.XWiki

and authenticating registered authenticators. This library has no concept of accounts, sessions

Concept This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: wiki pages (*.xml files) velocity templates (*.vm files) Strategy Specifically the idea is to be able to write integration tests that use the real code except

{{box cssClass="floatinginfobox" title="**Contents**"}} {{toc/}} {{/box}} = Concept = This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: * wiki pages (##*.xml## files) * velocity templates (##*.vm## files) = Strategy

://extensions.xwiki.org/xwiki/bin/view/Extension/Model%20Module]] module to understand the concept of references

description : {{info}} You can also check the [[XWiki Platform Developer's Guide>>xwiki:Documentation.DevGuide.Scripting||anchor="HVelocitySpecificInformation"]] for information about Velocity scripting in the XWiki Platform {{/info}} This module offers APIs to evaluate content with Velocity. The following concepts