Hi devs,
Now that the virtual mode is on by default our users are having troubles when they install 5.0.1.
It's the second time in 2 days that I have to help someone.
The issue is that users will want to use URLs such:
http://myhost/xwiki/bin/view/Main/WebHome
And those URLs don't work anymore by default (which can be seen as a regression).
So I'm proposing the following change for 5.0.2/5.1M1:
* If there's only 1 wiki configured then always point to the main wiki.
WDYT?
We need to make it easy again to use XWiki initially.
Thanks
-Vincent
Hello GSoC Mentors,
As you are participating to Google Summer of Code, I'm wondering if you
could consider using Flower Dev Center [1] while working with students.
Flower Dev Center is an online platform for UML modeling diagramming,
with a strong focus on code synchronization, integration with dev tools
(Git, SVN, etc) and real time collaboration on diagrams (and a little
bit on code as well).
We think Flower Dev Center can be helpful for both: mentors and students
during Google Summer of Code. We have created an article on this topic
(i.e. Flower Dev Center + GSoC): [2], [3].
If you have a couple of spare minutes, could you tell us if you would
like to use Flower Dev Center? And/or raise topics that you think are
important (based on previous GSoC participations) to be supported by
Flower Dev Center?
REMARK1: Right now, Flower Dev Center is closed source and offered for
free to open-source projects. Starting with next version we'll begin to
open its API and source code, so that anyone could write extension
plugins, etc.
REMARK2: The next version of Flower Dev Center, the 2.0.0 planned for
June/July 2013, has major new features, that we did not demonstrate yet
and that will improve even more the collaboration between developers.
REMARK3: Flower Dev Center will support programming languages that are
not object oriented, starting with 2.0.0
Thank you in advance!
Best regards,
Mircea @ The Flower Platform Team.
[1] - Flower Dev Center web site - http://www.flower-platform.com
[2] - Video “Flower Dev Center + Google Summer of Code” -
http://learn-discuss.flower-platform.com/flower_dev_center/videos/flower_de…
[3] - Text version with same content as the above video -
http://learn-discuss.flower-platform.com/flower_dev_center/tutorials/flower…
Hi devs,
ATM the solution is described here: http://dev.xwiki.org/xwiki/bin/view/Community/Debugging#HDebuggingJavaScript
What would you think about doing this instead:
* Package both the minimized and the non minimized version in our WAR (it shouldn't add too much weight to our overall WAR size)
* Have a directory structure like this:
resources/.../<module>/
|_ <non minified js file here>
|_ min/<minified js files here>
* This would allow to put in our xwikivars.vm something like (pseudo code):
#if ("$!request.minify" == 'false')
#set ($jsDir = '/')
#else
#set ($jsDir = 'min/'
#end
* Then everywhere we reference JS files we use $jsDir. For example in attachmentsinline.vm:
$xwiki.jsfx.use('uicomponents/widgets/${jsDir}upload.js', {'forceSkinAction': true, 'language': ${xcontext.language}})
…
This would allow to remove the "debug" profile and make it much faster to debug XWiki issues, even in production systems.
WDYT?
Thanks
-Vincent
Hi,
We introduced in XWiki 4.3 a new experimental search based on Apache Solr
[A] .
Right now our Solr Search [B] is marked as experimental and I don't know
how many of you got a chance to play a bit with it.
In order for it to become default we need to make sure we are covering the
major use cases. So in this mail we should provide some feedback on what is
really needed from a relevance, user experience, performance, etc. point of
view.
I am very interested also in some general feedback on the Lucene Search:
major problems you had with it and limitations.
The following questions are mostly related to Solr Search:
1) The Solr implementation adds a 'Filtered Search'. Are all filters that
are available now needed (wiki, space, type, filetype)? Are we missing
some? What is the most important one? Should we have multiple select?
>From a technical point of view we could add a lot of things (object
properties, query boost, etc.) but I'm more interested, in production, what
are some advanced or common use cases of search usage. IMO our Lucene
implementation is too simplistic, but it would be a shame to add useless
complexity to the Solr one if we really don't need it. On the other hand
having a customizable search is a really nice thing.
The customization part is kind of complex, but also the most powerful. I
want to know how much would we need the ability to explicitly mention the
types of results we want vs. excluding things, etc.
2) The Solr search adds a 'Sort' feature. What do you think about that?
3) Search result metadatas: should we display the relevance? What other
information should be displayed besides name, location, type?
4) Other mentions.
Having a generic search is more complex, than knowing exactly what your
search needs to return. We need to make sure we don't add too many niche
things while keeping the functionality satisfiable for general use cases.
Thanks,
Caty
---------------
[A]
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki43#HExper…
[B]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Solr+Search+Application
Hello all,
I've been working on some improvements on user changing password (see
XWiki-6882). In particular, I tried to make mandatory, for an user wanting
to change his password, to submit also his current password, so that I
could check it.
The problem is that there is no way to make this check through velocity. I
tried to use some groovy instead, but it breaks the functional tests. So I
need to introduce a new method "checkPassword" accessible from velocity
scripts. The question is, where should I implement it ?
There are two possibilities
1) Wrote a new component
2) Add this method in an existing API.
I don't really like 1), as I feel it would be strange to introduce a new
service with only one method.
In the meanwhile, for 2), I don't really know in which API this method
could fit. Sergiu told me that I could perhaps put it in
com.xpn.xwiki.plugin.rightsmanager.RightsManagerPluginApi,
but that it wasn't really good either. Any ideas ?
Cheers,
Thomas
Hi all,
For security reasons, I would like to be able to perform some rights
checking in the HTML macro (i.e I would like to forbid use of scripts to
untrusted users). But as the HTML macro is currently defined only in
xwiki-rendering, I can't do anything like that (xwiki-rendering should be
independent from the platform).
So, I would like to override the HTML macro in platform, in order to be
able to perform the security checks I want. Does this seems acceptable to
you ?
Thanks,
Thomas
Hi devs,
I'd like to copy all Document*Event in xwiki-platform-model/src/main/java/org/xwiki/model/event/* and deprecate (move to legacy) all the ones in the bridge module.
It seems they don't need XWikiContext, XWikiDocument or the like so it should be pretty easy.
WDYT?
Thanks
-Vincent