Hi all,
I would like to know why the authenticate method in LDAPAuthServiceImpl is executed 3 times when whenever a user login. (Regardless whether the user exists in the database)
I am currently trying to update the database whenever the user attributes fetched from the active directory is different from the one in the database.
Thanks in adv,
Colin
______________________________________________________________________
Search, browse and book your hotels and flights through Yahoo! Travel.
http://sg.travel.yahoo.com
The XWiki development team is pleased to announce the final release of
XWiki Enterprise 1.2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the final 1.2 release, which brings a lot of improvements and
new features. The main improvements over version 1.1 are:
* Improved performances
* Better Interoperability with Confluence
* Clean and improvements to the XMLRPC interface
* Recycle bin feature for deleted documents
* Minor edits
* News rights management UI
* Mail sender plugin to send emails from Velocity
* Watchlist feature to be notified of pages in documents or spaces
* Scheduler plugin and application to schedule Groovy scripts to be
executed at given times
* New macro to display panels inside pages
* JODA Time plugin to perform dates computations in Velocity scripts
* Lucene search stabilized and now works in multiwiki setups
* New statistics API and UI
* Add automatic database migrations for easier XWiki installs
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise12
Thanks
-The XWiki dev team
Hi,
I'd like to release Platform+XE 1.2 final today.
Note that I've fixed a missing jar for the PDF export in 1.2RC3 (http://jira.xwiki.org/jira/browse/XWIKI-2002
).
I hope enough people have tested 1.2RC3 but if we still have some
important bugs after 1.2 final is released we can always release a new
1.2.1 version.
Here's my +1
Thanks
-Vincent
Hi all,
I have some problems with wysiwug.
When I try to edit something like align center the text in a table cell and
click on "save and view" the modifications are not saved.
Can someone help me??
Thanks
Raffo
Hi,
I understand your point.
I have again one doubt here.
In the code we currently get the skin name and then generate the file path
(for velocity files) such as skins/<skin name>/<vm file name>.
If we go by option 2 then in this case if skin name is albatross we would
have to generate path as templates/ and for rest we would continue to use
the old file path. This would involve writing such if else condition in
xwiki code.
Would this be elegant way of handling skins?
How would this be handled in the code.
Thanks
Sachin
> Date: Wed, 16 Jan 2008 17:06:24 +0100
> From: Vincent Massol <vincent(a)massol.net>
> Subject: Re: [xwiki-devs] Moving the xwiki.org skin as part of our
> distribution
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <86A70FC8-9A1F-421C-ACED-4BFE22374B3E(a)massol.net>
> Content-Type: text/plain; charset="us-ascii"
>
>
> On Jan 16, 2008, at 4:56 PM, sachin mittal wrote:
>
> > Hi,
> > I have few doubts here:
> > Currently templates directory have their own vm files.
> > So would the first task be copy the vm files under albatross
> > directory to templates directory and merge the common templates file.
> >
> > Next other wiki skins have their own vm files and leaving them in
> > their respective skins directory is not a good (uniform) idea.
> > So these should also be moved (shouldn't it).
>
> We have 2 options:
> 1) Create templates that work for all current skins: dodo, finch and
> albatross
> 2) Consider that dodo and finch are history, make them use their own
> templates and not use any of the templates in templates/, clean the
> templates dir and replace them by the albatross vm files.
>
> 2) is much easier but 1) is nicer. I prefer 2).
>
> > Best would be to create sub directories under templates directory
> > with same structure as skins directory.
>
> That would defeat the notion of templates IMO.
>
> > Lastly regarding your point:
> > Another thing to do would be to "clean" the albatross templates so
> > that they are lighter, generate less style elements, etc.
> >
> > I completely agree to this. In fact to get ExtJs working with the
> > html content created by albatross vm files I had to delete lot of
> > unnecessary style elements, merge lot of vm files in single files. I
> > feel that vm files under albatross are lot scattered and having few
> > compact vm files would be much better.
> > Would this improve the performance too? (I don't know that)
>
> No idea.
>
> Thanks
> -Vincent
>
>
On Jan 16, 2008 11:39 AM, Nicolas Réau <nicolas.reau(a)gmail.com> wrote:
> Hi,
>
> Using Ubuntu 7.10 here all day, with Firefox and an nVidia driver too, and
> never got such problem on xwiki.org.
>
> The problem might come from your version of Ubuntu don't you think? Are
> you using compiz?
>
> -Nicolas
>
> PS: By the way, discussing it on another thread could be better, no?
Hmmm...might be, but I have only problems with scrolling on this pages. No
compiz (at least not knowingly). Strange. I'll download a 7.10 Live-CD
later...
Hmm...just now, while copying the text in another gmail instance I've the
same issue...many boxes = slow scrolling performance...it's not a
XWIKI-issue then...
Hi all,
I've build xwiki enterprice using maven and it creates the war file. Can I
deploy the war file under the xwiki enterprice installation ... how to do
it?
Ragards
Raffo
Hi,
I have few doubts here:
Currently templates directory have their own vm files.
So would the first task be copy the vm files under albatross directory to
templates directory and merge the common templates file.
Next other wiki skins have their own vm files and leaving them in their
respective skins directory is not a good (uniform) idea.
So these should also be moved (shouldn't it).
Best would be to create sub directories under templates directory with same
structure as skins directory.
Lastly regarding your point:
Another thing to do would be to "clean" the albatross templates so
that they are lighter, generate less style elements, etc.
I completely agree to this. In fact to get ExtJs working with the html
content created by albatross vm files I had to delete lot of unnecessary
style elements, merge lot of vm files in single files. I feel that vm files
under albatross are lot scattered and having few compact vm files would be
much better.
Would this improve the performance too? (I don't know that)
Thanks
Sachin
------------------------------
>
> Message: 5
> Date: Wed, 16 Jan 2008 16:42:46 +0100
> From: Vincent Massol <vincent(a)massol.net>
> Subject: Re: [xwiki-devs] Moving the xwiki.org skin as part of our
> distribution
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <3542AB82-3970-4CA7-9155-41A53603839C(a)massol.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
>
> On Jan 16, 2008, at 4:34 PM, Sachn Mittal wrote:
>
> >
> > Hi,
> > What is exactly you want help on.
> > I am anyway modifying the albatross skin to build the complete UI on
> > ExtJS,
> > so maybe any work on this front can help me also.
> > Right now I am modifying the default vm files in the albatross skin.
> > It would be nice if all the vm files are placed under xwiki
> > \templates and
> > skins have only css, images, js and other static content files.
>
> Yes that's exactly a task we have to do so this would be an example of
> the help I'd need.
>
> However we should not break dodo and finch skins so I guess the
> templates they use could be moved to their skin directory.
>
> WDYT?
>
> Another thing to do would be to "clean" the albatross templates so
> that they are lighter, generate less style elements, etc.
>
> Thanks
> -Vincent
>
> > vmassol wrote:
> >>
> >> Hi,
> >>
> >> Just to let you know that I had a discussion with Laurent Lunati (the
> >> author of the xwiki.org skin) and we agreed on the following:
> >>
> >> * Laurent will modify the skin so that it can support layouts with
> >> panels on the left. There are also some little things to fix like the
> >> panel wizard, etc. Laurent will try his best to finish all this by
> >> 15th of Feb
> >>
> >> * On our side we need to do the following:
> >> - move all vm files into the templates dir so that the albatross skin
> >> is mostly CSS files + images
> >> - move skins out of the web/standard module
> >> - future (can be done later): create maven plugin to transform a file
> >> system skin into a XAR so that our skins can be easily installed on
> >> existing xwiki installations
> >>
> >> The idea would be to finish this work by the 15th of Feb, in time for
> >> the 1.3M2 release.
> >>
> >> Is anyone interesting in helping out for doing this?
> >>
> >> Thanks
> >> -Vincent
> >>
> >> _______________________________________________
> >> devs mailing list
> >> devs(a)xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/devs
> >>
> >>
> >
> > --
> > View this message in context:
> http://www.nabble.com/Moving-the-xwiki.org-skin-as-part-of-our-distribution…
> > Sent from the XWiki- Dev mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
>
>
>
> ------------------------------
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
>
> End of devs Digest, Vol 7, Issue 24
> ***********************************
>
Hi,
Just to let you know that I had a discussion with Laurent Lunati (the
author of the xwiki.org skin) and we agreed on the following:
* Laurent will modify the skin so that it can support layouts with
panels on the left. There are also some little things to fix like the
panel wizard, etc. Laurent will try his best to finish all this by
15th of Feb
* On our side we need to do the following:
- move all vm files into the templates dir so that the albatross skin
is mostly CSS files + images
- move skins out of the web/standard module
- future (can be done later): create maven plugin to transform a file
system skin into a XAR so that our skins can be easily installed on
existing xwiki installations
The idea would be to finish this work by the 15th of Feb, in time for
the 1.3M2 release.
Is anyone interesting in helping out for doing this?
Thanks
-Vincent
hello developers,
I've been somewhat (but only somewhat) successfully building Curriki
with mvn which, indeed, used the DB connection where I would install it.
I would like to understand a bit more of the architecture... should I
rather discuss it per email or open a wiki page that tries to sketch
it ?
Here's what I could see:
- curriki is made of many modules, some of which are xwiki modules,
some are own
- some of the own resources are XWiki documents
- the whole packaging ends up by building a web-archive and an xwiki-
archive
(the xwiki archive seems to contain a lot of the xwiki documents)
- the build process seems to upload this web-archive to the DB
(connected to a temporary curriki)
it's easy then to deploy the web-archive and use.
However the web-archive seems incomplete on the played.
A simple one to check is Main/Board.
I tried (re-)importing it but it complains that UselessPanel is not
there.
Three questions:
- is all the above correct ?
- is there another way to upload single xwiki documents ?
- how are XWiki documents in source code edited ? (that's velocity in
xml as far as I can see).
thanks in advance
paul