Results 11 - 20 of 195 « previous page next page » Page 1 2 3 4 5 6 7 8 9 ... 20

Publication Workflow - Extend Workflow Scope To Child Pages

Located in
Last modified by slauriere on 2021/10/01
Rendered document content
or another one), or to a published page or a page that is not controlled by a workflow. concept covered by the concept of backlinks of XWiki platform Macro reference parameters, for instance in diagram or include
, or be published, or not under workflow. concept covered by the concept of backlinks of XWiki platform Links
Raw document content
. ** concept covered by the concept of backlinks of XWiki platform * Macro reference parameters, for instance
or by a distinct one, or be published, or not under workflow. ** concept covered by the concept of backlinks of XWiki platform * Links in large string properties of objects ** concept **not** covered by the concept

Improve the color theme editor

Located in
Last modified by Ecaterina Moraru (Valica) on 2018/04/25
Rendered document content
Concept I propose to improve the color theme editor to make it more powerful and flexible. In order to achieve this, I propose to: Add a new tab "Customized Variables" to the editor. This tab would allow us to add more LESS CSS variables and list them in a list We could use
Raw document content
== Concept == I propose to improve the color theme editor to make it more powerful and flexible. In order to achieve this, I propose to:\\ * (% style="line-height: 1.4em;" %)Add a new tab "Customized Variables" to the editor. This tab would allow us to add more LESS CSS variables and list them

IRC Archive for channel #xwiki on 10 November 2015

Located in
Last modified by Vincent Massol on 2015/11/10
Rendered document content
explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains
Raw document content
explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains

IRC Archive for channel #xwiki on 29 September 2015

Located in
Last modified by Vincent Massol on 2015/09/29
Rendered document content
page… seems we have blow up some concept too fast ! 10:20 <vmassol> IMO that's a mistake, we shouldn't be able to administer a non existing page 10:20 <vmassol> I don't see any issue of concept though 10
Raw document content
page… seems we have blow up some concept too fast ! 10:20 <vmassol> IMO that's a mistake, we shouldn't be able to administer a non existing page 10:20 <vmassol> I don't see any issue of concept though 10

Rights 9.x - Rights

Located in
Last modified by Ecaterina Moraru (Valica) on 2017/05/23
Rendered document content
pages are considered a deprecated concept, so we reduce this feature's visibility Page only rights can
Raw document content
into a single 'Page' category ** Terminal pages are considered a deprecated concept, so we reduce

XWiki Model 2.0

Located in
Last modified by Vincent Massol on 2020/02/21
Rendered document content
) further introduces the concept of shareable nodes which allows multiple paths of access to a node
the concept of journaled listeners which can ask the repository to re-play all events after a certain
. JSR283 hence introduces the (optional) concept of shareable nodes. This allows implementing multiple
Raw document content
://whiteboardjunkie.wordpress.com/2008/11/24/where-am-i-using-jcr-and-why/] * JSR 283 (JCR 2.0) further introduces the concept
navigations through content * JSR 283 further introduces the concept of journaled listeners which can ask
) concept of shareable nodes. This allows implementing multiple URIs for a given model object

Interface and Content Language Separation

Located in
Last modified by Marius Dumitru Florea on 2014/08/22
Rendered document content
There are multiple issues where users had problems understand the way we combine interface and content languages. This proposal tries to separate the two concepts: interface language and content language, and contains several display variants. Interface Language is set from Administration
Raw document content
There are multiple issues where users had problems understand the way we combine interface and content languages. This proposal tries to separate the two concepts: interface language and content language, and contains several display variants. * Interface Language ** is set from Administration

Idea: Help by Default

Located in
Last modified by Ecaterina Moraru (Valica) on 2017/06/22
Rendered document content
by them For beginner users, the demo applications helps them understand basic XWiki concepts, but after
Raw document content
helps them understand basic XWiki concepts, but after the initial steps they are still visibile * We

XWiki Forms & URL Mappings

Located in
Last modified by Philipp Roessler on 2020/01/28
Rendered document content
. Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object
Objects
comment : The combination of *actions* (like <tt>save</tt>) and *request parameters* (like <tt>xredirect</tt>) obviously is a very powerful means to work with XWiki documents. Is there any documentation on that? Where do these concepts belong to in the first place, Struts, XWiki, Velocity or another technology?
Raw document content
", or "1" {table} 1.1 Sample use cases TBD. Example to illustrate formentioned concepts. Ex: Ajax

Nested: Drawer

Located in
Last modified by Ecaterina Moraru (Valica) on 2018/01/09
Rendered document content
, where Spaces and Pages are replaced with a single Node (Page) concept. The entities hierarchy
Raw document content
a Nested Documents use case, where Spaces and Pages are replaced with a single Node (Page) concept
RSS feed for search on [concept]
Tags:

Get Connected