The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.6 Milestone 2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
Last milestone of the XWiki Enterprise 1.6 version.
Main changes:
* XWIKI-2634 - Various tasks for the new rendering implementation
* XWIKI-2651 - Create a new WYSIWYG editor based on GWT - 1.6M2
* XWIKI-2635 - Experimental XWiki Query Language
* XWIKI-2623 - Update MSSQL hibernate mapping file and ship it with
xwiki distributions
* XWIKI-2643 - Ability to easy add languages in QueryManager via
QueryExecutor components
* XE-300 - The treeview should sort spaces by their name
Important bug fixes:
* XWIKI-2573 - viewrev action fails with ugly stacktrace for
documents with attachments when no revision number is requested
* XWIKI-2649 - xwiki.authentication.ldap.mode_group_sync is not
"always" by default
Note that general goals for XWiki Enterprise 1.6 are:
* Beta versions of new rendering + new WYSIWYG editor
* Revamped Blog UI + features
* Security issues already in JIRA (marked as high priority)
* Bug fixes
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise16M2
Thanks,
The XWiki dev team
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.2.1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the last XEM 1.2.x version, after that this branch is not
supported anymore.
It's an XE upgrade from 1.4.1 to 1.4.2 and also contains some UI improvements.
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM121
Thanks
-The XWiki dev team
Hi XWikiers,
I'd like to start the 1.6M2 release ASAP which means that the blog
overhaul will be postponed to 1.6RC1.
FYI I've been working on improving XWiki localization lately but I
won't able to commit it before the release, I'll send an email about
this later today.
Here's my +1.
Thanks,
JV.
Hi devs,
for better management of the XWatch data, I'd like to create a XWiki Watch
component (plugin) to handle Watch specific actions on the server side. The main
reason I wish to do this is to eliminate the duplicate query code in Watch,
caused by the fact that the same actions are needed from the GWT Servlet and the
wiki documents. Since querying is a matter of accessing Watch data, I see no
reason for maintaining duplicate, independent implementations for it and not
centralizing it in a component.
Besides eliminating duplicate code, the component would also provide support for:
- universal, easier access to Watch data regardless of the interface/API (GWT
servlet, default implementation of XWatch portal pages, custom wiki pages)
- better implementation of the Watch data model layer on top of xwiki data model
(object/document dependencies, data consistency, providing universal API for
safer manipulation of data from this pov).
By adding this component, Watch would be deployed as a plugin + xar, as other
XWiki applications are (but with some custom modifications in web.xml, required
by the GWT servlet).
I would like to implement this component in the following iteration of XWiki
Watch (1.1 M2) to have it fully tested and debugged until the 1.1 final release.
WDYT?
Happy coding,
Anca Luca
Hello XWikiers
does anybody know of an xwiki extension that could enable our xwiki (a
curriki) to play the role of an acegi server?
thanks in advance
paul
Hi devs,
As XE 1.4.2 as been released I would like to release a XEM 1.2.1 based
on it. Like for XE 1.4.2, it will be the last XEM 1.2 branch release
and the branch will be removed from svn after that.
You can see the release note at
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM121
--
Thomas Mortagne
Hi,
Wikimodel (and Doxia) both have the ability to pass parameters to some
events such as paragraphs, lists, tables, etc.
I'm proposing that we enable that in our rendering too.
This will allow writing things like:
(% param1="value1" param2="value2" %)
This is a paragraph
Example:
(% style="background-color: blue" %)
This is a paragraph
Note that we've already agreed to do that for tables. What I'm saying
here is that we should generalize it to other elements. Here's the
list I propose:
- paragraphs
- list and list items (including definition lists)
- section headers
- quotation (which is not yet implemented, on my todo list)
- tables
This solves our issue of styling without requiring a special macro and
in addition it's very generic and consistent with wikimodel/doxia.
WDYT?
Thanks
-Vincent