Hi devs,
I'm working on implementing the new link format we've decided, i.e.:
label>reference>param1=value1 ... paramN=valueN
Note that there's a potential ambiguity with the following link:
text>param=value
Since this can be considered as either:
* label = text, reference = "param=value"
* reference = text, parameters = "param=value"
Thus we have to decide that it's fordbidden to use "=" in document
names or we need to find a different link format.
I think forbidding "=" is fine.
WDYT?
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.6 final.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This release spanned a bit more than 2 months starting on the 23rd of
July 2008 and ending on the 3rd of October 2008. During that period we
have implemented issues, fixed bugs and added new features such as:
* New experimental support for other syntaxes (Confluence, JSPWiki,
Creole, MediaWiki, TWiki and XHTML), including a new XWiki Syntax
v2.0.
* New experimental WYSIWYG editor (Work In Progress).
* Improved page footer displaying : comments, attachments, history,
various information
* New "Password Renewal and Forgot Username" feature
* Default account validation & confirmation emails provided in the
wiki preferences
* Rights Management interface now support adding groups into groups
* Improvement of Query Manager which was introduced in 1.6M1.
* New experimental XWiki Query Language called XWQL.
* Added .xml extensions to all exported wiki pages (XAR)
* The name of the main database in virtual wiki mode is not hardcoded
to 'xwiki' anymore, and in virtual mode all database names can be
prefixed with a configurable value
New or improved translations:
* german
* french
* czech
* norwegian
* ukrainian
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise16
Thanks
-The XWiki dev team
Hello Devs,
Below is a review of what has been done in XWS 1.1 vs. what was
initially planned in the Roadmap :
* Improving usability : Adding tooltips, advices, etc. for a smoother user
experience
-> Not really done, but we re-worked all the french and english messages.
* UI Refactorings : especially global administration, dashboard, and All
my spaces UIs.
-> Not done (partly done in 1.2 M1)
* Quality insurance : keep adding more unit tests and integration tests.
(Yes, I will try to definitely fix the two tests that fails on our
continuum server ;))
-> Done, for the Integration Tests part. Tests has been fixed, and many
tests were added.
* Invitation management (see http://jira.xwiki.org/jira/browse/XWS-79)
-> Done
* Improvement of users and groups management (see
http://jira.xwiki.org/jira/browse/XWS-7)
-> Done
* RSS on space and dashboard stories
-> Not done
* More options exposed in the global administration
-> Done
Conclusion
----------
We did about half what we initially planned, and we did not respect
initially dates (the final release has been delayed by more than 1 month
and a half). This due to both a lack of resources (I have been taken by
other projects), and a too greedy roadmap.
We will take this into account when proposing the future roadmaps.
Regards,
Jerome.
hello guys,
I do the following:
- I have a class with a DBStringList property "mylist"
- In a velocity script, I do:
#set($obj = $doc.getObject("MyClass", $mynb)
#set($mylist = $obj.get("mylist"))
#set($mylist = "${mylist}|${mynewlistitem}")
#set($ret = $obj.set("mylist", $mylist))
#set($ret = $doc.save())
- I run this script and I can see in the DB that "mynewlistitem" was added
as listitem to "mylist" but the item doesn't appear in the object editor for
property "mylist" in my document.
- Moreover, I get some rendering exception in contentview.vm when I try to
access this object in other velocity scripts.
- When I create the link using the Object editor, then everything works well
but I don't see anything different in the DB from the previous state.
- I have tried the same with:
#set($obj = $doc.getObject("MyClass", $mynb)
#set($mylist = $obj.getProperty("mylist").getValue())
#set($ret = $mylist.add("${mynewlistitem}"))
#set($ret = $doc.save())
same result...
It seems the Object property is saved but it is not taken into account by
the object in the document.
Do you any clue for me?
regards
Pascal
hello,
I would like to write some scripts which do some more complex SQL extraction
requests using for example $xwiki.search(sql)... no modif of the DB, just
extraction for presentation... I would prefer not to be forced to code a new
Java module just for this...
But this function is protected by programming rights...
So I must give programming rights to allow people to view this page... I
find a bit disturbing because programming rights have a "sensitive" meaning
in my head...
What's your point of view about this? What's the lightest, cleverest and
fairest way to allow this? Any advice? :)
regards
Pascal
Hi devs,
Since we're in a rush for the final 1.6 release I'm proposing to
postpone creating the 1.6 branch to this Thursday. This means that
trunks stays 1.6 final and thus only bug fixes should be done.
Thus this means postponing any 1.7 change to after Thursday.
Is that ok with everyone?
Thanks
-Vincent
Hi devs,
You know we've been facing some problems in the new GWT editor. Marius
needs 2 days more to finish fixing the 2 important bugs related to:
- paragraph support
- bolding/unbolding (same for italic and underline I guess)
We also need 1 day to all test the new GWT WYSIWYG and try to find
more issues.
Note that since we've had to do low level JS, it's currently only
working for FF... So the editor won't work on IE or any other browser
to 1.6 final. It may work but it won't work perfectly well yet.
In addition and to reduce the 1.6 final release date (compared to the
original plan of 22nd of September), I propose that we release the
final 1.6 on this Thursday (the 2nd).
To do this I propose that we ALL spend time testing the current 1.6
trunk code to verify that all works fine.
This is a bet we're taking but I think we could easily win 1 or 2
weeks by doing it. In addition and should we need it we can quickly
release a 1.6.1 release.
Here's my +1 for this plan + for helping test it.
Thanks
-Vincent
Hi,
Can anyone tell me the functionality of "*Switch to Advanced edit mode and
Switch to Simple edit mode*" in the user profile.
I don't think both are different. Since both are doing the same
functionality.
--
Prathap