Wiki source code of Release Notes for XWiki Enterprise 4.2 Milestone 2
Version 16.1 by Sergiu Dumitriu on 2012/08/06
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{box cssClass="floatinginfobox" title="**Contents**"}} | ||
| 2 | {{toc/}} | ||
| 3 | {{/box}} | ||
| 4 | |||
| 5 | {{warning}} | ||
| 6 | This release is not finished yet, this is a work in progress | ||
| 7 | {{/warning}} | ||
| 8 | |||
| 9 | Second milestone of the 4.2 release. | ||
| 10 | |||
| 11 | = New and Noteworthy (since XWiki Enterprise 4.2 Milestone 1) = | ||
| 12 | |||
| 13 | == New field types for email and list of pages == | ||
| 14 | |||
| 15 | == Improved display of users and groups fields == | ||
| 16 | |||
| 17 | == Improvements to the Extension Repository Application == | ||
| 18 | |||
| 19 | We modified the extension sheet to display the release notes for all the available versions of an extension. Check for instance the release notes for the [[Extended TODO Application>>extensions:Extension.Extended Todo Application#HReleaseNotes]]: | ||
| 20 | |||
| 21 | {{image reference="ER-releaseNotes.png"/}} | ||
| 22 | |||
| 23 | == Improvements to Extension Manager == | ||
| 24 | |||
| 25 | An administrator of a subwiki can now install XAR extension (as long as it does not require a JAR extension). | ||
| 26 | |||
| 27 | = For Developers = | ||
| 28 | |||
| 29 | == Default custom displayers for Easier customization of the way object fields are displayed == | ||
| 30 | |||
| 31 | While XWiki allowed to specify a custom display for a given field, it was impossible to change the way field types, such as //DateProperty// or //IntegerProperty//, are displayed in general. Now it is possible to define custom displayers at the farm or wiki level, which gives the administrators more power to change the look and feel of the wiki. For example, this allows to use HTML5 input types for dates and numbers, to use custom suggestions for //list of users// fields, or to always add a validation input for all the //password// field types. | ||
| 32 | |||
| 33 | To use this feature, first you need to compute a //type// name for your property type. This is obtained from the java class simple name, removing the ##Class## suffix, and lowercasing. For example, for numbers the java class used is ##com.xpn.xwiki.objects.classes.NumberClass##, with the simple name ##NumberClass##, which gives ##number## as the type name. For a database list, we get ##dblist## from ##DBListClass##. | ||
| 34 | |||
| 35 | Next, there are three places where a default custom displayer can be defined. | ||
| 36 | |||
| 37 | 1. If a document whose name is the //type// capitalized and suffixed with ##Displayer## exists in the ##XWiki## space in the current wiki, then its content is used as the default custom displayer for that type of property. For example, ##localwiki:XWiki.NumberDisplayer## and ##localwiki:XWiki.DblistDisplayer##. | ||
| 38 | 1. If a document whose name is the //type// capitalized and suffixed with ##Displayer## exists in the ##XWiki## space in the main wiki, then its content is used as the default custom displayer for that type of property. For example, ##xwiki:XWiki.NumberDisplayer## and ##xwiki:XWiki.DblistDisplayer##. | ||
| 39 | 1. If a velocity template whose name is the //type// suffixed with ##.vm## exists in the current skin, then it is evaluated as the default custom displayer for that type of property. A skin file can be defined in many places, such as an attachment of a skin document, a file in a named skin on the filesystem, or a file in the ##templates/## directory. | ||
| 40 | |||
| 41 | If a specific class property provides custom display code in the XClass, then that code takes priority over an eventual default custom displayer for that property. | ||
| 42 | |||
| 43 | As with property custom displayers, when evaluating the display code several objects are placed in the context: | ||
| 44 | |||
| 45 | * ##name## is the name of the property being displayed | ||
| 46 | * ##prefix## is the HTML name prefix to append to an eventual input field name, and contains the XClass name, an underscore, the object number, and another underscore, for example ##XWiki.XWikiUsers_0_## | ||
| 47 | * ##object## is the object owning the displayed property, an instance of the public ##com.xpn.xwiki.api.Object## class | ||
| 48 | * ##type## is the target display type, one of ##view##, ##edit##, ##hidden## or ##search## | ||
| 49 | |||
| 50 | == New API to manipulate log level == | ||
| 51 | |||
| 52 | Several method as been added to ##org.xwiki.logging.LoggerManager## to manipulate the log level of registered loggers. | ||
| 53 | |||
| 54 | {{code language="java"}} | ||
| 55 | /** | ||
| 56 | * Associate the passed logger to the passed log level. | ||
| 57 | * | ||
| 58 | * @param loggerName the logger | ||
| 59 | * @param level the level of the logger | ||
| 60 | */ | ||
| 61 | void setLoggerLevel(String loggerName, LogLevel level); | ||
| 62 | |||
| 63 | /** | ||
| 64 | * @param loggerName the logger | ||
| 65 | * @return the log level associated to the logger | ||
| 66 | */ | ||
| 67 | LogLevel getLoggerLevel(String loggerName); | ||
| 68 | |||
| 69 | /** | ||
| 70 | * @return all the registered loggers | ||
| 71 | */ | ||
| 72 | Collection<Logger> getLoggers(); | ||
| 73 | {{/code}} | ||
| 74 | |||
| 75 | == Deprecated and Retired projects == | ||
| 76 | |||
| 77 | <description of deprecated and retired projects> | ||
| 78 | |||
| 79 | == Upgrades == | ||
| 80 | |||
| 81 | The following dependencies have been upgraded: | ||
| 82 | |||
| 83 | * GWT 2.5 RC1 | ||
| 84 | * Selenium 2.25 | ||
| 85 | |||
| 86 | == Miscellaneous == | ||
| 87 | |||
| 88 | * Office Importer/Exporter encoding issues have been fixed ({{jira style="enum" url="http://jira.xwiki.org"}}XWIKI-6377 | ||
| 89 | XWIKI-8007{{/jira}}). | ||
| 90 | |||
| 91 | == Translations == | ||
| 92 | |||
| 93 | The following translations have been updated: | ||
| 94 | |||
| 95 | {{language codes="code1, code2"/}} | ||
| 96 | |||
| 97 | = Tested Browsers = | ||
| 98 | |||
| 99 | Here's the list of browsers tested with this version (i.e. browsers that we've tested as working - Check the list of [[supported browsers>>dev:Community.BrowserSupportStrategy]]): | ||
| 100 | |||
| 101 | {{velocity}} | ||
| 102 | ## name = iexplorer, firefox, chrome, safari, opera | ||
| 103 | {{/velocity}} | ||
| 104 | |||
| 105 | {{browser name="browser" version="x.x"/}} | ||
| 106 | |||
| 107 | = Known issues = | ||
| 108 | |||
| 109 | * [[Bugs we know about>>http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=category+%3D+%22Top+Level+Projects%22+AND+issuetype+%3D+Bug+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC]] | ||
| 110 | |||
| 111 | = Test Report = | ||
| 112 | |||
| 113 | You can check the [[manual test report>>TestReports.WebHome#<anchor to test report>]] to learn about what was tested and the results on various browsers. | ||
| 114 | |||
| 115 | = Backward Compatibility and Migration Notes = | ||
| 116 | |||
| 117 | == General Notes == | ||
| 118 | |||
| 119 | You may also want to [[import the default wiki XAR>>Main.Download]] in order to benefit from all the improvements listed above. | ||
| 120 | |||
| 121 | {{warning}} | ||
| 122 | Always make sure you compare your ##xwiki.cfg## and ##xwiki.properties## files with the newest version since some configuration parameters were added. Note that you should add ##xwiki.store.migration=1## so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything. | ||
| 123 | {{/warning}} | ||
| 124 | |||
| 125 | == Issues specific to <projet> <version> == | ||
| 126 | |||
| 127 | <issues specific to the project> | ||
| 128 | |||
| 129 | == API Breakages == | ||
| 130 | |||
| 131 | The following APIs were modified since <project> <version - 1>: | ||
| 132 | |||
| 133 | {{code language="none"}} | ||
| 134 | <clirr output here> | ||
| 135 | {{/code}} |
