Last modified by Thomas Mortagne on 2023/10/13

<
From version < 51.1 >
edited by Thomas Mortagne
on 2016/02/09
To version < 51.3 >
edited by Eduard Moraru
on 2016/02/09
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ThomasMortagne
1 +XWiki.enygma
Content
... ... @@ -38,11 +38,18 @@
38 38  
39 39  For backwards compatibility with the existing untyped links, we have implemented the same mechanism we have applied for URLs, which is to:
40 40  
41 -* first try to link to a terminal page (i.e. if ##Some.Nested.Page## is actually a terminal page inside the ##Some.Nested## space; this was the previous default behavior)
41 +* first try to link to an existing terminal page (i.e. if ##Some.Nested.Page## is actually a terminal page inside the ##Some.Nested## space; this was the previous default behavior)
42 42  * if no such terminal page exists, then link to the non-terminal page (i.e. ##Some.Nested.Page.WebHome##) for both when the non-terminal page exists or when it does not (and should be a wanted link)
43 43  
44 44  The same thing applies for ##image~:## (e.g. ##image~:[email protected]## translates technically to ##image~:[email protected]##) and for ##attach~:## syntax (e.g. ##attach~:[email protected]## translates technically to ##attach~:[email protected]##).
45 45  
46 +=== Relative links to sibling Nested Pages ===
47 +
48 +To better support backwards compatibility with the pre-Nested-Pages behavior when the current document is a non-terminal document and an untyped relative link (e.g ##~[~[Page]]##) has not been resolved using the above mentioned algorithm, we perform 2 additional checks:
49 +
50 +* we try to link to an existing terminal page that is a sibling in the parent space (i.e. ##~[~[Page]]## is resolved to the equivalent of ##~[~[doc:parentSpace.Page]]##)
51 +* if no such terminal page exists, then link to the non-terminal page that is a sibling in the parent space (i.e. ##~[~[Page]]## is resolved to the equivalent of ##~[~[doc:parentSpace.Page.WebHome]]##) for both when the non-terminal page exists or when it does not (and should be a wanted link)
52 +
46 46  == Color Theme Displayer ==
47 47  
48 48  In the administration, an error message is displayed if the configured color theme is invalid. It could happen after an upgrade if you were using an old Colibri Theme.
... ... @@ -171,7 +171,7 @@
171 171  * With the improvement done in the wiki links, ##image~:## and ##attach~:## syntax, existing untyped links pointing to inexistent documents (e.g. ##~[~[Doc]]##) will no longer be resolved to point to a new terminal document in the same space (i.e. ##<currentSpace>.Doc##, when ##<currentSpace>.Doc## does not exist), but will be resolved to point to a new non-terminal document in the top level (i.e. ##Doc.WebHome##). The reason is because we don`t currently have a way to specify a relative link to a nested document (i.e. space) and we only use absolute links. This only affects wanted links, since for existing documents the backwards compatibility mechanism preserves the previous behavior.
172 172  * Mail API Unique Message Identifier (since 7.4.1): In order to solve [[XWIKI-12165>>http://jira.xwiki.org/browse/XWIKI-12165]], the unique identifier of each mime message sent has been change to a SHA1 based on the ##Message-ID## header and the list of recipients of the mails, ensuring uniqueness during a newsletter or mailing sending. To introduce this change, the ##MailContentStore## and the ##MailListener API## has been broken, and now use a new ExtendedMimeMessage instead of the simple ##MimeMessage## for all arguments. The values ##messageId## returned or used as argument in the API is no more equivalent to the ##Message-ID## header, but is now the unique identifier returned by ##ExtendedMimeMessage#getUniqueMessageId()##. Finally, the ##MessageMimeMessageFactory## now returns cloned ##MimeMessage## without changing the ##Message-ID##.
173 173  * If you have custom Velocity Uberspectors that implement ##org.xwiki.velocity.introspection.ChainableUberspector## or extend ##org.xwiki.velocity.introspection.AbstractChainableUberspector##, update them to ##org.apache.velocity.util.introspection.ChainableUberspector## and ##org.apache.velocity.util.introspection.AbstractChainableUberspector##. If you have a custom list of uberspectors specified under ##runtime.introspector.uberspect.chainClasses##, just use the ##runtime.introspector.uberspect## property for defining the list. Otherwise your custom configuration will be ignored!
174 -* We've introduced the possibility to explicitly create a link to a Space in XWiki Syntax 2.1, e.g. ##[~[space:Space1.Space2]~]##. However if you had a subwiki named ##space## the new notation will conflict with the syntax for referencing that wiki. Thus you'll need to edit existing links such as ##[~[space:something]~]## to ##[~[doc:space:something]~]##. And if you wish to reference a given space in the ##space## subwiki, you'd write ##[~[space:space:something]~]##.
181 +* We've introduced the possibility to explicitly create a link to a Space in XWiki Syntax 2.1, e.g. ##~[~[space:Space1.Space2]]##. However if you had a subwiki named ##space## the new notation will conflict with the syntax for referencing that wiki. Thus you'll need to edit existing links such as ##~[~[space:something]]## to ##~[~[doc:space:something]]##. And if you wish to reference a given space in the ##space## subwiki, you'd write ##~[~[space:space:something]]##.
175 175  
176 176  == API Breakages ==
177 177  

Get Connected