On Tue, Jun 8, 2010 at 09:01, Denis Gervalle <dgl(a)softec.lu> wrote:
> On Mon, Jun 7, 2010 at 17:00, Ecaterina Valica <valicac(a)gmail.com> wrote:
>
> > > It will if it display the inheritance source in a column. For right set
> > at
> > > current level this column could even precise what inheritance has been
> > > overwritten, both in terms of allowance and origin.
> > >
> > > Denis.
> >
> >
> > Hi Denis,
> >
> > "Something" like this:
> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights51Space
>
>
> Yes, "something" like that. I would have expected a "back to basic" button
> in place of "advanced, and the removal of the basic interface to avoid
> duplicating basic rights. Maybe the menu should be horizontal in the
> advanced interface, I do not know. Also add some hyperlinks to upper level
> in the column explaining inheritance. And put the highlight of changes over
> the rest of the row (includes name and inheritance)
>
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights51Space
About:
> I would have expected a "back to basic" button
> in place of "advanced, and the removal of the basic interface to avoid
> duplicating basic rights
>
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights43Propos…
This removal of the basic interface will be set from the user profile's
variables (if it has advanced type)? I mean if the user is advanced, all the
rows will be presented in advances?
I'm asking because I think the collapsed view is great to see changes up in
the table, where you don't care the advanced status of those rights.
> WDYT ? Is this interesting ?
>
it's nice :P I would love to see some other opinions.
Thanks,
Caty
I'm trying to create a live table similar to the "All Docs" one in
Main, but filtered for a specific space (in this case, named
Software).
i've used the Live table snippet for the table page itself:
-------------------------------------------
{{velocity}}
#set($collist = ["doc.name", "doc.space","doc.date", "doc.author", "_actions"])
#set($colprops = {
"doc.name" : { "type" : "text" , "size" : 30,
"link" : "view"},
"doc.space" : { "type" : "text", "link" : "space"},
"doc.date" : { "type" : "date" },
"doc.author" : { "type" : "text", "link" : "author"},
"_actions" : {"actions": ["copy","delete","rename","rights"]}
})
#set($options = { "resultPage":"XWiki.SofwareTableresults",
"translationPrefix" : "xe.index.",
"rowCount": 15 })
#livetable("allsoftwaredocs" $collist $colprops $options)
{{/velocity}}
-------------------------------------------
And here's the Software table results page:
-------------------------------------------
{{include document="XWiki.LiveTableResultsMacros" /}}
{{velocity}}
#set($extra = "")
#if("$!request.space" != "") #set($extra = "${extra} and doc.space =
'$request.space'") #end
#if("$!request.orphaned" == "1") #set($extra = "${extra} and
doc.parent='' and doc.name<>'WebHome'") #end
#gridresultwithfilter("$!request.classname",
$request.collist.split(","), "doc.space = 'Software' ", "${extra}")
{{/velocity}}
-------------------------------------------
As soon as I added the ""doc.space = 'Software' " parameter to the
gridresultfilter(), it broke the page and gives: "Failed to execute
macro: velocity"
What is the correct way to filter the query?
Thanks,
- James Cuzella
Hi,
I'd like to start a wiki for practitioners of Hapkido, a Korean martial art.
We (a group of students of Hapkido) will use the wiki to store and share
learned techniques.
myxwiki username: jmorfit3
desired wiki server name: hapkido.myxwiki.org
alternate wiki server name: omaahkd.myxwiki.org
Thanks,
/John Morfit
Hi xwiki-users,
I seem to be having trouble including JARs in my Groovy classpath. I'm
trying the following:
{{groovy jars="attach:test-1.0.jar"}}
try {
def x = Class.forName("com.test.TestMe")
out.println(x)
}
catch(e) {
out.println("FAILURE: " + e)
}
{{/groovy}}
This ends up with the text "FAILURE: ClassNotFoundException", but if I
change the first line to:
Class.forName("com.test.TestMe", false, this.getClass().getClassLoader())
it seems to work. But, when I try this instead:
{{groovy jars="attach:wiki:Sandbox.Test"}}
try {
def x = Class.forName("com.test.TestMe", false,
this.getClass().getClassLoader())
out.println(x)
}
catch(e) {
out.println("FAILURE: " + e)
}
{{/groovy}}
it "red-boxes" me with a NullPointerException at the end (at
com.xpn.xwiki.doc.DefaultDocumentAccessBridge.getAttachmentContent(DefaultDocumentAccessBridge.java:510)).
And, same issue if I try it without the ClassLoader.
Ultimately, I'm trying to wrap this in a WikiMacro, but none of these
options work if I put the code in a WikiMacro object. Anyone have luck with
JAR attachments? Thanks in advance!
Hi,
I try to configure annotations on cop-1.myxwiki.org without success
The annotation menu doesn't appear on that wiki
Can you help please. I've read somewhere in the forum that it is related to developer right on a space but I don't know how I can deal with that.
Kind regards
http://epist.bouygues-construction.com/images/structis.gif<http://epist.bouygues-construction.com/images/structis.gif>
Eric JUIN
Directeur Partage de la Connaissance - e|services
STRUCTIS - Gie Informatique BOUYGUES CONSTRUCTION
e.juin(a)bouygues-construction.com
Tél: + 33 1 30 60 21 07
Mob: +33 6 60 35 21 07
http://epist.bouygues-construction.com/images/feuille.jpg<http://epist.bouygues-construction.com/images/feuille.jpg>
Respectons l'environnement, n'imprimez ce message que si nécessaire
Please consider the environment before printing this mail
--
Les donnees et renseignements contenus dans ce message sont personnels, confidentiels et secrets. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee. Si vous n'etes pas le bon destinataire, nous vous demandons de ne pas lire, copier, utiliser ou divulguer cette communication. Nous vous prions de notifier cette erreur a l'expediteur et d'effacer immediatement cette communication de votre systeme.
Any data and information contained in this electronic mail is personal, confidential and secret. Any total or partial publication, use or distribution must be authorized. If you are not the right addressee, we ask you not to read, copy, use or disclose this communication. Please notify this error to the sender and erase at once this communication from your system.
A small variation for Version 3
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3AProposal
Changes:
- improved the display of inheritance of rights within a role
description;
- emphasize the display of "Inherited"|"Allow"|"Deny" by using color and
icon representation.
For Rights version 4 I'll remove the concept of Role.
Thanks,
Caty
On Thu, May 20, 2010 at 15:30, Ecaterina Valica <valicac(a)gmail.com> wrote:
>
>
> On Wed, May 19, 2010 at 21:04, Denis Gervalle <dgl(a)softec.lu> wrote:
>
>> On Wed, May 19, 2010 at 16:33, Ecaterina Valica <valicac(a)gmail.com>
>> wrote:
>>
>> > Hi Denis,
>> >
>> > On Wed, May 19, 2010 at 16:52, Denis Gervalle <dgl(a)softec.lu> wrote:
>> >
>> > > On Wed, May 19, 2010 at 12:39, Ecaterina Valica <valicac(a)gmail.com>
>> > wrote:
>> > >
>> > > > On Tue, May 18, 2010 at 18:29, Denis Gervalle <dgl(a)softec.lu>
>> wrote:
>> > > >
>> > > > > On Tue, May 18, 2010 at 17:08, Guillaume Lerouge <
>> > guillaume(a)xwiki.com
>> > > > > >wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > On Tue, May 18, 2010 at 11:03, Ecaterina Valica <
>> valicac(a)gmail.com
>> > >
>> > > > > wrote:
>> > > > > >
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > I've reviewed some of your feedback and added them to Rights
>> > > > Management
>> > > > > > UI
>> > > > > > > Proposal *VERSION 3*:
>> > > > > > >
>> > > > > > > *Partial Prototype*
>> > > > > > >
>> > > > > > > - Wiki Level:
>> > > > > > >
>> > > >
>> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3Wiki
>> > > > > > > - Space Level:
>> > > > > > >
>> > > > >
>> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3Space
>> > > > > > > - Page Level:
>> > > > > > >
>> > > >
>> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3Page
>> > > > > > >
>> > > > > > > *Desired Interaction*
>> > > > > > >
>> > > > > > > -
>> > > > > > >
>> > > > > >
>> > > >
>> >
>> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3Proposal
>> > > > > > >
>> > > > > > > Thanks,
>> > > > > > > Caty
>> > > > > > >
>> > > > > >
>> > > > > > I like the separation between rights definition and rights
>> > > affectation.
>> > > > > > Only
>> > > > > >
>> > > > >
>> > > > > Nice indeed, but I do not understand how it could fits with
>> current
>> > > > > implementation.
>> > > > >
>> > > > >
>> > > > > > downside -> inherited rights are displayed less clearly than
>> what
>> > > they
>> > > > > were
>> > > > > > in version 2.
>> > > > > >
>> > > > >
>> > > > > and I do not see any inherited information anymore.
>> > > > >
>> > > >
>> > > > For example, in Space Level
>> > > > http://localhost:8084/xwiki/bin/view/Improvements/Rights3Space
>> > > > the text in yellow represents the inherited users and inherited
>> roles
>> > > from
>> > > > upper level.
>> > > >
>> > > > The text in black (evalica with Reviewer and the Reviewer
>> definition)
>> > is
>> > > > specified only for this level.
>> > > >
>> > > > After the save the added "Reviewer" right is gonna look like this:
>> > > >
>> > > >
>> > >
>> >
>> http://localhost:8084/xwiki/bin/download/Improvements/Rights3Proposal/addU6…
>> > >
>> > >
>> > > Thanks for these precision, I have better understand your idea.
>> > (Personally
>> > > I have some difficulties with colors (partially color blind), so
>> > > information
>> > > based on colors is not always easy for me.)
>> > >
>> >
>> > So you're a great test candidate :). I also received a mail from Roman
>> (he
>> > wanted icons to represent rights), so what I can do for you is to try a
>> > version with color + little icon to represent
>> "Inherited"|"Allow"|"Deny". I
>> > will think about it.
>> >
>>
>> I think that could be nice to have more visual than color information
>> for inheritance. The way it was in proposal 2 was fine, since this was
>> more
>> intensity than color.
>> And I will be pleased to be your candidate. Be careful that using icons
>> for
>> representing specific rights could add complexity when (later) components
>> add new rights dynamically.
>>
>>
>> >
>> >
>> > >
>> > >
>> > > > >
>> > > > > So, proposal 3 seems less interesting than proposal 2. I do not
>> see
>> > > what
>> > > > it
>> > > > > solves based on previous comments either.
>> > > > > Caty, could you explain further your goals with this proposal ?
>> > > > >
>> > > >
>> > > > I tried in proposal 3 to make it more easy to use. People told me
>> that
>> > > they
>> > > > didn't understood the "Containing Spaces/Pages" so I've removed it.
>> > > > This proposal gives the users the possibility to create Roles that
>> can
>> > > have
>> > > > semantically value to them and thus making the rights more easy to
>> use.
>> > > >
>> > > > This proposal accommodates the case: "Not sure it's scalable. In the
>> > > future
>> > > > applications/components will be able to register new rights".
>> > > > Having the rights displayed vertically and only on Add, makes the UI
>> > more
>> > > > scalable, and in the code we could add as many rights as we would
>> want.
>> > > > Also
>> > > > the spaces is now more economical having just "Allow"/"Deny"
>> columns.
>> > > >
>> > >
>> > > I completely agree that proposal 3 is clearer. The problem is that
>> > > your samples and the structure of this proposal are really far from
>> > current
>> > > implementation.
>> > > Proposal 2 were fitting better but the samples where also not
>> realistic
>> > and
>> > > remarks from Thomas about global wiki users should also be integrated.
>> > >
>> >
>> > About Thomas feedback, don't you like
>> >
>> >
>> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3Proposal#HN…
>> > ?
>> >
>> >
>> > >
>> > > So, I am puzzle by your goals here. Aren't we going too fast ?
>> > > Since there is very poor documentation about the way XWiki rights
>> works
>> > (I
>> > > would be happy to improve that, but it will require some time), I have
>> > the
>> > > impression that there is a important misunderstanding of how
>> inheritance
>> > is
>> > > effectively applied. So the design of a proper UI is not easy. I have
>> > also
>> > > read the draft of Sergiu that aims to improve the documentation, but
>> > either
>> > > I have not understand it or it does not describe current behavior.
>> > >
>> > > So the question is for me, are we designing this UI to think about
>> future
>> > > possibilities or to replace the current UI ?
>> > >
>> >
>> >
>> > My purpose is "to make rights easy to use at last". IMO this means do
>> > whatever it takes to make them "easy to use" :) I try to base my
>> proposal
>> > on
>> > existing code, but I never disregard new functionalities that I can add
>> if
>> > this means the UI and experience is gonna be improved.
>> >
>> > The only thing Rights version 3 is adding is the "Role" part, which is
>> some
>> > kind of groups for rights. If the solution given is gonna be convincing
>> > enough to be use in the rights part (not yet .... but maybe some version
>> of
>> > it) I'm sure there will be someone that is gonna want to implement it.
>> > Until
>> > then I will continue to prototype and find out how we can add all that
>> > functionality in one place.
>> >
>>
>> Well, this precisely the grouping of right that is a big change.
>> Currently,
>> right are inherit individually, not as a group.
>> Moreover, the inheritance is a little bit particular, since allowing a
>> given
>> right at lower level, will deny that same right for anybody else even if
>> this right is allowed at a higher level.
>> Said another way, once an allowance for a given right has been found and
>> you
>> are not part of it, you are denied.
>> Of course, there is an exception to this rules regarding global admin
>> rights, these ones are evaluated before and gets priority.
>>
>> I would agree if you find this to be not the correct way of evaluating
>> right, but this is the way it works since the beginning. There is also an
>> option to evaluate rights based on a hierarchy of spaces, but this one is
>> usually disabled. It will probably be revived when such hierarchy of space
>> are bring back using the new reference model.
>>
>> So, I am convinced that current right management is poor, but changing it
>> will require important changes, and time.
>>
>> Hope you get a better idea of my concerns. For detailled information on
>> how
>> rights are processed, you may want to have a look at
>> http://dev.xwiki.org/xwiki/bin/view/Drafts/XWikiRightServiceReversed.
>> This
>> is really bare documentation of the code, but it tells the truths.
>>
>
> Denis, thanks for the extra info
> Caty
>
>
>>
>> Denis
>>
>>
>> >
>> > And yes... I need to focus more on the inheritance again.
>> >
>> > Thanks,
>> > Caty
>> >
>> >
>> > > Denis
>> > >
>> > >
>> > > > Thanks,
>> > > > Caty
>> > > >
>> > > > >
>> > > > > Denis
>> > > > >
>> > > > >
>> > > > > >
>> > > > > > Also, a drop-down might be better than an autosuggest when
>> > selecting
>> > > > > which
>> > > > > > right should be added to a role.
>> > > > > >
>> > > > > > Guillaume
>> > > > > >
>> > > > > >
>> > > > > > > _______________________________________________
>> > > > > > > devs mailing list
>> > > > > > > devs(a)xwiki.org
>> > > > > > > http://lists.xwiki.org/mailman/listinfo/devs
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Guillaume Lerouge
>> > > > > > Product Manager - XWiki SAS
>> > > > > > Skype: wikibc
>> > > > > > Twitter: glerouge
>> > > > > > http://guillaumelerouge.com/
>> > > > > > _______________________________________________
>> > > > > > devs mailing list
>> > > > > > devs(a)xwiki.org
>> > > > > > http://lists.xwiki.org/mailman/listinfo/devs
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Denis Gervalle
>> > > > > SOFTEC sa - CEO
>> > > > > eGuilde sarl - CTO
>> > > > > _______________________________________________
>> > > > > users mailing list
>> > > > > users(a)xwiki.org
>> > > > > http://lists.xwiki.org/mailman/listinfo/users
>> > > > >
>> > > > _______________________________________________
>> > > > users mailing list
>> > > > users(a)xwiki.org
>> > > > http://lists.xwiki.org/mailman/listinfo/users
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Denis Gervalle
>> > > SOFTEC sa - CEO
>> > > eGuilde sarl - CTO
>> > > _______________________________________________
>> > > 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
>> >
>>
>>
>>
>> --
>> Denis Gervalle
>> SOFTEC sa - CEO
>> eGuilde sarl - CTO
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
Hi Denis,
I want to thank you again for all the help you are giving :P
Please take a look at a proposal for "V3 and my 3)" version with elements
from Rights2 :)
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Proposal
and in "action"
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Space
The prototype is not reflecting the "desired" interaction: both inherited
info and rights change appear on hover (right icon and arrow), instead of
hover | click.
That "v" needs to be an arrow like the one we use in the action menus.
On Tue, Jun 1, 2010 at 19:06, Denis Gervalle <dgl(a)softec.lu> wrote:
> Caty,
>
> Really nice and interesting post, I will try to reach that level... but
> without visual :\
>
> I really think that using the collapsed view for editing would helps basic
> users to have a simplified and more easy interface to understand. We may
> even imagine that only "advanced user" (those marked so in their profile),
> has access to the expanded view.
>
> I think that the collapsed view missed an additional icon that summarize
> the
> rights that are not shown. This one would only be shown if there is any
> non-defaulted additional right in action.
This is a signal that extended
> rights are in use (See it like the grey box of Windows when special rights
> are setup, which is inviting to go into advanced view to know more). This
> one would be obviously not editable, and should probably work like the ...
> or replace it ? In place of the ... . Concerning the ..., I am not sure,
> but
> I would also prefer to see a textual link "advanced" in small font, and
> only
> visible when row is hovered.
>
>
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Proposal#H…
> Order of right are not significant, so I would prefer that in all view,
> these where in the same order, with the basic right first (V/C/E/D/A/P) and
> the additional right in their order of registration (hope that it will stay
> constant... or we will have to find a way to keep them ordered).
> The "right" part of each icon should be grayed if the right is inherited
> and
> not grayed if the right is set locally, this improve the information
> provided in V3.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Proposal#H…
The problem with this icons (taken from Silk) is that there is little
difference for View, Comment, Admin icons between the two states (inherited,
locally set) - but this is something we can easily improve (by changing the
icons and looking for some more contrast).
Example: This is how they look when all rights are set locally (full color)
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights43Propos…
> I also think that the +/- (which is never grayed) could be
> nearer to the right icon. Maybe you could use a green V and a read "stop"
> in
> place of +/- ?
>
The other mockup versions (like
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights41Space) used
v/x for the allow/deny representation, and yes, I agree that they are more
suited than +/-.
The problem is that we are using in XWiki, X to represent delete, so having
two xX was too much, that's why I introduced +/-. Maybe we can find another
solution.
>
> Regarding the collapsed view, I see three possibilities to investigate for
> allowing edition while improving readability (note that readability has the
> same issue in expanded view, but it seems to be less annoying) :
>
> 1) use V3, but when hovering a row, use V2 on that row and allow drag/drop
> (keeping V2 until drop even is hover is temporary lost). Not sure this will
> be nice in practice ? see 2)
>
> 2) use a presentation in 4 columns, for both collapsed and expanded view,
> the first column behing a read-only summary like V3, and the 3 column being
> an ordered V1. However, dragging from summary would be allowed. The 3
> detailed column could be shown only when a drag is started from summary, or
> with a global horizontal expansion button... Basic user would have access
> to
> this, but not necessarily to vertical row expansion. Not sure this is not
> an
> increase in complexity ? so, see 3)
>
> 3) use V3, and a similar interface to what we have in current right
> management interface. Since saved are postponed (not like we have
> currently), using this one may be both practical and could helps the
> transition for existing user as well. With all the belts and whistle added
> to clearly state changes and inheritance, this will be similar but really
> better than what we have.
>
> If we go for V3 and my 3) proposal, I also wonder if the current table
> header is well done. I do not like it when nothing is expanded since it is
> confusing, too large, and not significant. It will be even more unexpected
> if you follow me on the "advance user" case, when a basic user look at it.
> Maybe you could try a changing header, only expanding when there is
> expanded
> row, or, you could move the expanded header in each expanded row, keeping a
> simplified header at the top.
>
> WDYT ?
>
> Denis
>
>
Other problem that this proposal has is the representation of "advanced
rights". If we don't like the textual description and we want to add icons,
IMO we have two solutions:
A) use the same abstract icon, but with different color, ex. a key or lock
icon with color representation ("blue" for "programming", "green" for
"captchaComment", etc)
- the problem here is for the people that have some kind color blindness and
will not distinguish between some color tones (this is the case when we
gonna have lots of "advanced" | non default rights)
B) use the same abstract icon and with an order index (like numbers 1, 2,
etc or characters A, B, etc)
These representations are based on the fact that "advanced rights" will be
added by other developers and the icon will not be custom made for a specif
right.
Another thing we need to consider for this proposal is how the filtering is
gonna be made.
>
> On Tue, Jun 1, 2010 at 12:54, Ecaterina Valica <valicac(a)gmail.com> wrote:
>
> > On Tue, Jun 1, 2010 at 10:03, Denis Gervalle <dgl(a)softec.lu> wrote:
> >
> > > Caty,
> > >
> > > I probably have an issue with my browser (Chrome/Mac) but I cannot see
> > the
> > > icons :(
> > >
> >
> > Fixed: thanks.
> >
> > Made some screenshots with how it suppose to look like:
> > - Wiki:
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> > - Space:
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> >
> >
> > > Anyway this seem to me nice, but I am not sure you should prevent
> > changing
> > > rights in summary mode. I think that summary mode should allow simple
> > right
> > > management, and for 'casual' or less knowledgeable users, this should
> be
> > > the
> > > only mode used. This is not only a summary, but also a simplified
> > > interface.
> > >
> > > WDYT ?
> > >
> >
> > I had your vision (changing rights in summary mode) in mind when I
> started
> > prototyping. Let me show you some versions:
> >
> > V1_space) First version took the exact order from the extended view
> (first
> > Allow, second Deny rights)
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> >
> > + this version lets the user drag its right to the appropriate column
> > +- has the same representation as the extended version
> > --- there is no scanability: if I want to see the status of "delete"
> right
> > for different groups/users I have to search for them (making me dizzy :P
> )
> > + there is no gapping space between rights
> >
> > V2_space) Tried to fix the dizziness by providing same order/position for
> > rights
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> > +- this version lets the user drag its right to the appropriate column,
> > but the user has not control over the position he choose to drop the
> > target:
> > the right will appear on the column it's suppose to be
> > +- doesn't have the same representation as the extended version
> > (allowed/denied order broke, determined order present)
> > + scanability: it's easy to scan for the searched column/position
> > - gap space between rights: ex. evalica-DenyDelete: some users might
> not
> > like that gap and may not understand why is there (is it a bug?)
> >
> > See also:
> > V2_wiki)
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> > V2_wiki_expanded)
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> >
> > As you see in V2) has the same functionality as the expanded version.
> > The main benefit is that is occupying less space, but we still need the
> > expanded view for the Inherited/detailed information for each right.
> >
> > The down side of version 2
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> > is that if I want to *summarize *a global state for a given right (ex see
> > for what users 'delete' is allowed/denied) at a global level, not at a
> > group/user level, the same dizziness effect appears (I have to search for
> > 'delete' right in three columns, for all the users)
> >
> > V3) is the current proposal, it compresses the 3 column spread
> information
> > in one view.
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> > - this version doesn't lets the user drag its right to the appropriate
> > column
> > +- doesn't have the same representation as the extended version
> > + scanability: it's easy to scan for the searched column/position at a
> *
> > global* level
> > + there is no gapping space between rights
> >
> > V3_wiki)
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> > is equivalent to
> > V2_wiki)
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> >
> > I prefer V3) over V2):
> > + Summary does what is suppose to: give a global summary of existing
> > rights, without being concerned of the type of the right (inherited,
> > locally
> > allowed, locally denied)
> > + Good Readability
> > +/- Doesn't allow rights to be dragged around. I prefer changing rights
> in
> > expanded mode because there you also have more information, like source
> of
> > the inheritance + 3 columns.
> >
> > Being compact it's easier to understand the "local source of inheritance"
> > for a given right. For example, allowing "view" right for 'evalica' will
> > deny it for 'unregistered users' and 'registered users'. Being on the
> same
> > column is easier to look for the change and see it in action (being
> > highlighted).
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights4Proposa…
> >
> > Please tell me what you think about this rationale. It would be great if
> > you
> > have ideas about how to make the summary being draggable, but also
> keeping
> > scanability and less gaps.
> >
> > Thanks,
> > Caty
> >
> >
> > > Denis
> > >
> > > On Mon, May 31, 2010 at 16:54, Ecaterina Valica <valicac(a)gmail.com>
> > wrote:
> > >
> > > > On Mon, May 31, 2010 at 17:53, Ecaterina Valica <valicac(a)gmail.com>
> > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Summary Icons for standard rights:
> > > > >
> > > > > *Space Level:*
> > > > >
> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights42Space
> > > > > *Wiki Level*:
> > > > >
> > >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights4Proposal
> > > > >
> > > >
> > > > Sorry: link for Wiki is
> > > >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights42Wiki
> > > >
> > > >
> > > > >
> > > > > Bug:
> > > > > - when clicking on "more" next to the summary, all columns should
> > > expand,
> > > > > not just one column at a time.
> > > > >
> > > > > Missing:
> > > > > - expand/collapse all + pagination, etc
> > > > >
> > > > > Remarks:
> > > > > - Summary view is good for quick scanning of the rights. Rights
> > > > management
> > > > > (changing) and inheritance explanations are available in expanded
> > view.
> > > > > - Icons presented just for: view, comment, edit, delete, admin,
> > > register,
> > > > > programming. Extended rights|Expand mode are represented by "..."
> > > (more)
> > > > >
> > > > > Thanks,
> > > > > Caty
> > > > >
> > > > >
> > > > > On Thu, May 27, 2010 at 11:26, Denis Gervalle <dgl(a)softec.lu>
> wrote:
> > > > >
> > > > >> On Thu, May 27, 2010 at 09:57, Ecaterina Valica <
> valicac(a)gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >> > Hi,
> > > > >> >
> > > > >> > I want to talk a bit about:
> > > > >> >
> > > > >> > > The inheritance is a little bit particular, since allowing a
> > given
> > > > >> right
> > > > >> > at
> > > > >> > > lower level, will deny that same right for anybody else even
> if
> > > this
> > > > >> > right
> > > > >> > > is allowed at a higher level.
> > > > >> > >
> > > > >> >
> > > > >> > I want to know how hard this would be to be changed.
> > > > >> >
> > > > >>
> > > > >> Changing this is not hard, but it will increase complexity since
> we
> > > will
> > > > >> need a backward compatibility mode for existing wikis.
> > > > >>
> > > > >>
> > > > >> > Another question is why this has been done in the first place?
> Can
> > > > >> someone
> > > > >> > give a valid use case when this is more productive than other
> > ways.
> > > > >> >
> > > > >>
> > > > >> I really do not know, and I am curious as well.
> > > > >>
> > > > >>
> > > > >> > It is very confusing and users need to do additional steps in
> > order
> > > to
> > > > >> give
> > > > >> > the rights they want.
> > > > >> >
> > > > >>
> > > > >> I completely agree, this is poor.
> > > > >>
> > > > >> I think is a problem of how the Groups are perceived. Only as a
> > rights
> > > > >> > mechanism or as a semantically grouping.
> > > > >> >
> > > > >>
> > > > >> We should not decide this, since groups maybe synchronized from
> > > external
> > > > >> system (ie LDAP), imposing groups for rights is not correct. By
> the
> > > way,
> > > > >> groups may contains groups, but I am almost sure that this will
> work
> > > > >> properly in practice.
> > > > >>
> > > > >>
> > > > >> > If we use groups just to give rights than the current
> > implementation
> > > > is
> > > > >> > usable. But if you have groups, like Tech team, Design team,
> > > > Marketing,
> > > > >> > Happy team ... etc in order to classify our users in other ways
> > > beside
> > > > >> > rights management, giving permission to a user is breaking all
> the
> > > > >> > inheritance from upper levels.
> > > > >> >
> > > > >> > Example:
> > > > >> > Group A(Managers) has View (default allowed) at wiki level -
> this
> > > > means
> > > > >> > that
> > > > >> > they should be allowed to view all the pages in the wiki.
> > > > >> > Group B(Tech Team) has View (explicitly denied) at spaceX level
> -
> > > this
> > > > >> > means
> > > > >> > they shouldn't be allowed to view this space.
> > > > >> >
> > > > >> > But I have a person (the managerX) in Group B that is supposed
> to
> > > see
> > > > >> the
> > > > >> > info in spaceX level. So the first logical move would be to give
> > him
> > > > >> allow
> > > > >> > at space level (having in mind that space rights are stronger
> that
> > > > wiki
> > > > >> > rights and the view right has been overriden). But, if I give
> > > managerX
> > > > >> view
> > > > >> > right, all the other groups (incluing Managers) will be denied
> for
> > > > >> spaceX
> > > > >> > level. This means I need to know that and "repair" again all the
> > > > rights
> > > > >> I
> > > > >> > ALREADY set at the higher level.
> > > > >> >
> > > > >> > This behavior is not logical for me.
> > > > >> >
> > > > >>
> > > > >> It is not logical for me and I imagine many others !
> > > > >>
> > > > >>
> > > > >> >
> > > > >> > A solution would be to take out managerX form Group B and leave
> it
> > > > just
> > > > >> in
> > > > >> > Managers group. Yes, this way my problem is solved, but this
> means
> > > > >> Groups
> > > > >> > are only used for Rights purposes. Group B (Tech Team) is no
> > longer
> > > > >> > semantically compact and I can't further give this group compact
> > > > tasks,
> > > > >> > etc.
> > > > >> >
> > > > >> > Please tell if is a way to change this behavior and please have
> in
> > > > mind
> > > > >> > XWiki 3.0, where Groups are going beyond rights management and
> > they
> > > > >> should
> > > > >> > be seen as collaboration mechanisms (which need to be
> semantical).
> > > > >> >
> > > > >>
> > > > >> IMO, XWiki 3.0 should have a complete rework of the right service
> > > > >> implementation, and breaks with the past.
> > > > >> Since this will cause many migration issue, I am not in favor of
> > > > >> progressive
> > > > >> changes, and I would prefer to see a big single change that fix
> > this,
> > > > and
> > > > >> also the current discussion on script rights.
> > > > >>
> > > > >> Denis
> > > > >>
> > > > >> Rights should be inherited from upper level and should affect only
> > the
> > > > >> > user/group where a change is made, not make some complicated
> > > > >> implications
> > > > >> > at
> > > > >> > other levels and groups.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > Caty
> > > > >> >
> > > > >> > On Wed, May 26, 2010 at 16:48, Ecaterina Valica <
> > valicac(a)gmail.com>
> > > > >> wrote:
> > > > >> >
> > > > >> > > Hi,
> > > > >> > >
> > > > >> > > Did:
> > > > >> > > - source of inheritance is per rights;
> > > > >> > > - local source of inheritance: if the a right is allowed to
> > anyone
> > > > >> else
> > > > >> > at
> > > > >> > > the same level, it is implicitly disallowed for any others;
> > > > >> > > - inheritance from upper levels / groups.
> > > > >> > >
> > > > >> > > Please see if I put the rights correctly:
> > > > >> > > Wiki Level:
> > > > >> > >
> > > >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights41Wiki
> > > > >> > > Space Level:
> > > > >> > >
> > > > >>
> > > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights41Space
> > > > >> > >
> > > > >> > > Obs. Summary view + icons not done yet.
> > > > >> > >
> > > > >> > > Thanks,
> > > > >> > > Caty
> > > > >> > >
> > > > >> > >
> > > > >> > > On Sat, May 22, 2010 at 11:31, Denis Gervalle <dgl(a)softec.lu>
> > > > wrote:
> > > > >> > >
> > > > >> > >> Hi Caty,
> > > > >> > >>
> > > > >> > >> This one is simpler and more easy to understand than proposal
> 2
> > > > >> (which I
> > > > >> > >> liked but were complex). It is your best try IMO. I agree
> with
> > > Caty
> > > > >> that
> > > > >> > >> using icons too reduce the place taken will not allow easy
> > > > >> extensions.
> > > > >> > But
> > > > >> > >> Alex proposal would help to have a summary view, which is
> nice
> > to
> > > > >> have
> > > > >> > >> too.
> > > > >> > >>
> > > > >> > >> Maybe we could do both in fact. Propose a summary view (by
> > > > default),
> > > > >> > which
> > > > >> > >> fit a single line per user, this view would present the
> common
> > > > rights
> > > > >> > >> (V/C/E/D/A/(R/P)) using icons, and a last icon would be used
> to
> > > > >> mention
> > > > >> > >> there is more special rights either inherited, allowed or
> > denied.
> > > > So
> > > > >> we
> > > > >> > >> only
> > > > >> > >> need to use (and think about) a short icon representation for
> > > > common
> > > > >> > >> rights,
> > > > >> > >> and extended rights will be represented by a single special
> > > > >> > >> representation.
> > > > >> > >> Rows could be expanded individually or globally so if you
> want
> > a
> > > > more
> > > > >> > >> detailled information, you may reach it either for a single
> > user
> > > or
> > > > >> all
> > > > >> > at
> > > > >> > >> once. Changing common rights would be allowed in collapsed
> mode
> > > and
> > > > >> > >> expanded
> > > > >> > >> mode, but changing special rights would only be allowed in
> > > expanded
> > > > >> > view.
> > > > >> > >>
> > > > >> > >> If you want to keep the width even smaller, you may also
> > colspan
> > > > the
> > > > >> > >> user/group column over the others, using 2 rows per user, but
> I
> > > am
> > > > >> not
> > > > >> > >> sure
> > > > >> > >> it will be nice. (Could this be only when horizontal space is
> > > short
> > > > >> ?)
> > > > >> > >>
> > > > >> > >> I really like this one because it is simple to learn without
> > > > >> > documentation
> > > > >> > >> and could also help learning how rights works, but there is
> > again
> > > > >> > >> some inconstancies with the current implementation. Compare
> to
> > > > >> proposal
> > > > >> > 3,
> > > > >> > >> these inconsistencies may be nicely fixed and really helps
> > > > >> understanding
> > > > >> > >> why
> > > > >> > >> the right is disallowed at any time. You can do it like this:
> > > > >> > >>
> > > > >> > >> - the inheritance pop-up information should be at the right
> > > level
> > > > in
> > > > >> > >> the inheritance columns. The rights are inherited and check
> > > > >> > individually,
> > > > >> > >> so
> > > > >> > >> the precise source of inheritance is per rights, not only per
> > > user
> > > > or
> > > > >> > >> group
> > > > >> > >> - there is a local source of inheritance: if the a right is
> > > > allowed
> > > > >> to
> > > > >> > >> anyone else at the same level, it is implicitly disallowed
> for
> > > any
> > > > >> > others.
> > > > >> > >> So the source of inheritance is the local level, implying a
> > deny
> > > > >> because
> > > > >> > >> the
> > > > >> > >> local level has at least a specific allow. This means than
> when
> > > you
> > > > >> drag
> > > > >> > >> the
> > > > >> > >> first time a right in the allow column, all other user/group
> at
> > > the
> > > > >> same
> > > > >> > >> level will have that right inherited deny from the current
> > level.
> > > > >> (For
> > > > >> > >> those
> > > > >> > >> who wonder and will check the source of the right service,
> yes,
> > > > there
> > > > >> is
> > > > >> > >> potential performance improvement by immediately denying when
> a
> > > > >> > >> non-matching
> > > > >> > >> allow is found, currently we continue to check right at
> higher
> > > > level
> > > > >> for
> > > > >> > >> more deny, this is not really clever)
> > > > >> > >>
> > > > >> > >> With these changes, I really feel that this last proposal
> could
> > > be
> > > > a
> > > > >> > real
> > > > >> > >> improvement in the way rights are applied, and keeps the
> > > interface
> > > > >> > simple
> > > > >> > >> at
> > > > >> > >> the same time.
> > > > >> > >>
> > > > >> > >> WDYT ?
> > > > >> > >>
> > > > >> > >> Denis
> > > > >> > >>
> > > > >> > >> On Sat, May 22, 2010 at 07:57, Ecaterina Valica <
> > > valicac(a)gmail.com
> > > > >
> > > > >> > >> wrote:
> > > > >> > >>
> > > > >> > >> > On Fri, May 21, 2010 at 21:42, Alex Busenius <
> > > > >> alex.busenius(a)xwiki.com
> > > > >> > >> > >wrote:
> > > > >> > >> >
> > > > >> > >> > > I like this version, it makes clear what is
> allowed/denied
> > > and
> > > > >> why,
> > > > >> > >> but
> > > > >> > >> > > it takes a lot of space. What if those rights names would
> > be
> > > > >> > replaced
> > > > >> > >> by
> > > > >> > >> > > big icons and placed side by side? Like this (sorry for
> > > > >> ASCII-art):
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >>
> -------------------+-------------------------------------+--+------
> > > > >> > >> > > Unregistered users | [+V] [+C] [+R] [-D] [-A] [-P] [-CC]
> |
> > |
> > > > >> [-E]
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > Big Icons:
> > > > >> > >> > We are using Silk set for our icons and this is
> constraining.
> > > > Also,
> > > > >> > >> Rights
> > > > >> > >> > version 3-4 were made having rights extensibility in mind,
> > for
> > > > use
> > > > >> > cases
> > > > >> > >> > like adding "captchaComment" right, or "annotate" right, or
> > > > >> > >> > "applicationXusage" right .... so I don't think is very
> good
> > if
> > > > >> > >> > applications
> > > > >> > >> > are gonna have to choose their custom icon to represent
> their
> > > > >> custom
> > > > >> > >> right,
> > > > >> > >> > because is gonna be a mess in the UI.
> > > > >> > >> >
> > > > >> > >> > There are few possible icons to choose from (in order to
> keep
> > > the
> > > > >> > >> look&feel
> > > > >> > >> > unitary) and having the developers choose their own icon
> for
> > > the
> > > > >> right
> > > > >> > >> they
> > > > >> > >> > extend is gonna break the UI consistency.
> > > > >> > >> > I think is much easier, extensible and less visual cryptic
> to
> > > > >> textual
> > > > >> > >> > describe an extensible right.
> > > > >> > >> >
> > > > >> > >> > Placed side by side:
> > > > >> > >> > Version 4 takes a lot of space, yes, but the problem with
> > side
> > > by
> > > > >> side
> > > > >> > >> is
> > > > >> > >> > that is less readable (harder to scan the rights order).
> Also
> > > > it's
> > > > >> > >> easier
> > > > >> > >> > to
> > > > >> > >> > have a bigger area to select when you want to drag an item.
> > > > >> > >> >
> > > > >> > >> > Thanks Alex for your feedback,
> > > > >> > >> > Caty
> > > > >> > >> >
> > > > >> > >> > >
> > > > >> > >> > > Alex
> > > > >> > >> > >
> > > > >> > >> > >
> > > > >> > >> > > On 05/21/2010 07:51 PM, Ecaterina Valica wrote:
> > > > >> > >> > > > Hi,
> > > > >> > >> > > >
> > > > >> > >> > > > Changes:
> > > > >> > >> > > >
> > > > >> > >> > > > - One additional column is added: "Default /
> Inherited
> > > > >> Rights",
> > > > >> > >> by
> > > > >> > >> > > > default all rights appear in this column
> > > > >> > >> > > > - By using drag'n'drop items are tossed around
> between
> > > > >> "Allow
> > > > >> > >> > rights",
> > > > >> > >> > > > "Deny rights" and "Default / Inherited Rights"
> > > > >> > >> > > >
> > > > >> > >> > > > Rights Proposal 4:
> > > > >> > >> > > >
> > > > >> > >> >
> > > > >> > >>
> > > > >> >
> > > > >>
> > > >
> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights4Proposal
> > > > >> > >> > > > Wiki Prototype:
> > > > >> > >> > > >
> > > > >> > >>
> > > > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights4Wiki
> > > > >> > >> > > > Space Prototype:
> > > > >> > >> > > >
> > > > >> > >>
> > > > >>
> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights4Space
> > > > >> > >> > > >
> > > > >> > >> > > > This proposal is done by using feedback provided by
> Roman
> > > > >> Muntyanu
> > > > >> > >> and
> > > > >> > >> > > > Raluca Morosan.
> > > > >> > >> > > > Thanks,
> > > > >> > >> > > > Caty
> > > > >> > >> > > > _______________________________________________
> > > > >> > >> > > > users mailing list
> > > > >> > >> > > > users(a)xwiki.org
> > > > >> > >> > > > http://lists.xwiki.org/mailman/listinfo/users
> > > > >> > >> > > >
> > > > >> > >> > > _______________________________________________
> > > > >> > >> > > devs mailing list
> > > > >> > >> > > devs(a)xwiki.org
> > > > >> > >> > > http://lists.xwiki.org/mailman/listinfo/devs
> > > > >> > >> > >
> > > > >> > >> > _______________________________________________
> > > > >> > >> > users mailing list
> > > > >> > >> > users(a)xwiki.org
> > > > >> > >> > http://lists.xwiki.org/mailman/listinfo/users
> > > > >> > >> >
> > > > >> > >>
> > > > >> > >>
> > > > >> > >>
> > > > >> > >> --
> > > > >> > >> Denis Gervalle
> > > > >> > >> SOFTEC sa - CEO
> > > > >> > >> eGuilde sarl - CTO
> > > > >> > >> _______________________________________________
> > > > >> > >> devs mailing list
> > > > >> > >> devs(a)xwiki.org
> > > > >> > >> http://lists.xwiki.org/mailman/listinfo/devs
> > > > >> > >>
> > > > >> > >
> > > > >> > >
> > > > >> > _______________________________________________
> > > > >> > users mailing list
> > > > >> > users(a)xwiki.org
> > > > >> > http://lists.xwiki.org/mailman/listinfo/users
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Denis Gervalle
> > > > >> SOFTEC sa - CEO
> > > > >> eGuilde sarl - CTO
> > > > >> _______________________________________________
> > > > >> users mailing list
> > > > >> users(a)xwiki.org
> > > > >> http://lists.xwiki.org/mailman/listinfo/users
> > > > >>
> > > > >
> > > > >
> > > > _______________________________________________
> > > > users mailing list
> > > > users(a)xwiki.org
> > > > http://lists.xwiki.org/mailman/listinfo/users
> > > >
> > >
> > >
> > >
> > > --
> > > Denis Gervalle
> > > SOFTEC sa - CEO
> > > eGuilde sarl - CTO
> > > _______________________________________________
> > > 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
> >
>
>
>
> --
> Denis Gervalle
> SOFTEC sa - CEO
> eGuilde sarl - CTO
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
Is it possible to get a list of all users that a user belongs to using velocity or groovy?
The getAllMatchedUsers() method in the XWikiGroupService looks like it would do what I need but this does not seem to be exposed in the xwiki api for use in velocity/groovy?
http://maven.xwiki.org/site/xwiki-core-parent/xwiki-core/apidocs/com/xpn/xw…
Radek Rekas
Hello Sergiu, hello xwiki-users,
I alreday thought, that there should be something very stupid... ;-)
Thanks to Sergiu I'm online now, thank you very much!
Best regards
Pierre
-----Original Message-----
From: Sergiu Dumitriu [mailto:sergiu@xwiki.com]
Sent: Tuesday, June 08, 2010 5:15 PM
To: XWiki Users
Subject: Re: [xwiki-users] Installation issue / import function
On 06/08/2010 12:32 PM, Dalluege, Pierre (extern) wrote:
> Hello xwiki users,
>
> After installing xwiki 2.3 (and 2.3.1 afterwards) on Centos5.5 with
> MySQL 5.x and Tomcat 5.5 I still have the issue that I cannot import
> the default .xar file. The same is true for all .xar files: I
> generated one from this wiki and I wanted to re-import it. No chance
yet.
>
> Unfortunately I cannot see any problem on xwiki / tomcat or mysql
level.
> Everything looks fine.
>
> As I shouldn't provide screen shots, you may have a look at
> http://m2m.fm:8080/xwiki/bin/admin/Main/WebPreferences.
Importing only works from the main (wiki) administration, not from space
administration. The correct link is
http://m2m.fm:8080/xwiki/bin/admin/XWiki/XWikiPreferences
I imported the default XAR for you.
>
> I am looking at this topic for some days now, with no result yet. ANY
> IDEAS?
>
> Thank you very much for your support.
>
> Best regards
>
> Pierre
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
hi,
a) yes i get a rendered content (html) of the page.
b) no, its not a problem of the url. there are all absolute.
its a problem of the rights. i need a additional login to get the
images from xwiki.
little workaround (not ideal)
i give show rigths for the specific page to unregistered users.... (very
bad)
Am 08.06.2010 16:57, schrieb Marius Dumitru Florea:
> On 06/08/2010 03:04 PM, -the- wrote:
>
>> hi,
>>
>> i'm new on the group but i use xwiki since 3 years.
>>
>> for a automatic display panel application we show a xwiki-page via rpc
>> like the reference
>> "http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC"
>>
>> but with this code we can't display images.
>> only the name of the picture will displayed.
>>
>> have anybody a solution/reference for this problem.
>>
> You get the rendered content (HTML) of a wiki page and display it in an
> HTML-aware widget? If so, the widget should take care of downloading the
> images too. Maybe they are not loaded because the URLs are relative. Can
> you debug and see how the image URL (the value of the src attribute)
> looks like in the HTML returned by the XMLRPC call? Also, can you try to
> insert an external image in a wiki page and see if that image is loaded
> in your panel. External images should have absolute URLs.
>
> Hope this helps,
> Marius
>
>
>> with regards
>> -the-
>>
>> _______________________________________________
>> 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
>
>
>
Hello xwiki users,
After installing xwiki 2.3 (and 2.3.1 afterwards) on Centos5.5 with
MySQL 5.x and Tomcat 5.5 I still have the issue that I cannot import the
default .xar file. The same is true for all .xar files: I generated one
from this wiki and I wanted to re-import it. No chance yet.
Unfortunately I cannot see any problem on xwiki / tomcat or mysql level.
Everything looks fine.
As I shouldn't provide screen shots, you may have a look at
http://m2m.fm:8080/xwiki/bin/admin/Main/WebPreferences.
I am looking at this topic for some days now, with no result yet. ANY
IDEAS?
Thank you very much for your support.
Best regards
Pierre
Hi,
I downloaded the Column20Macro jar and put it in my WEB-INF/lib directory.
Then, after restarting my server, I tried to use it to display two basic
columns but I had this error :
Failed to execute section macro :
org.xwiki.rendering.macro.MacroExecutionException: Section macro
expect at least one column macro as first-level children
at org.xwiki.rendering.internal.macro.column.SectionMacro.execute(SectionMacro.java:78)
at org.xwiki.rendering.internal.macro.column.SectionMacro.execute(SectionMacro.java:25)
at org.xwiki.rendering.internal.transformation.MacroTransformation.transformOnce(MacroTransformation.java:174)
at org.xwiki.rendering.internal.transformation.MacroTransformation.transform(MacroTransformation.java:119)
at org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:72)
[...]
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
It's quite weird because I used two column macro. Here my code :
{{section justify="true"}}
{{column}} a {{/column}}
{{column}} b {{/column}}
{{/section}}
When I wrote use only one column macro inside the section one, I didn't have
that error... But until two columns macro, the error appeared...
Did I miss something ?
Thanks,
Marine
Hello xwiki users, hello asiri,
Thank you very much for your personal support. I have no errors in the
tomcat log, but I also increased the packet size before.
BR
Pierre
-----Original Message-----
From: Asiri Rathnayake [mailto:asiri.rathnayake@gmail.com]
Sent: Tuesday, June 08, 2010 1:47 PM
To: XWiki Users
Subject: Re: [xwiki-users] Installation issue / import function
Hi,
On Tue, Jun 8, 2010 at 4:02 PM, Dalluege, Pierre (extern) <
p.dalluege(a)external.telekom.de> wrote:
> Hello xwiki users,
>
> After installing xwiki 2.3 (and 2.3.1 afterwards) on Centos5.5 with
> MySQL 5.x and Tomcat 5.5 I still have the issue that I cannot import
> the default .xar file. The same is true for all .xar files: I
> generated one from this wiki and I wanted to re-import it. No chance
yet.
>
> Unfortunately I cannot see any problem on xwiki / tomcat or mysql
level.
> Everything looks fine.
>
Are you sure tomcat logs don't have any exceptions logged? I have
experienced issues with importing when max_allowed_packet (mysql
configuration) is not large enough.
And did you make sure that your xar file is valid? (Not corrupted)
- Asiri
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
hi,
i'm new on the group but i use xwiki since 3 years.
for a automatic display panel application we show a xwiki-page via rpc
like the reference
"http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC"
but with this code we can't display images.
only the name of the picture will displayed.
have anybody a solution/reference for this problem.
with regards
-the-
Hello xwiki users, hello caleb,
The link links to the "life" system, so you simply may select the xar,
click on on importing, you get the toc of the xar and finally you may
import it with an error message of the importing tool.
Yes, we use Firefox (but it also happens on IE8).
Best regards
Pierre
-----Original Message-----
From: Caleb James DeLisle [mailto:calebdelisle@lavabit.com]
Sent: Tuesday, June 08, 2010 1:32 PM
To: XWiki Users
Subject: Re: [xwiki-users] Installation issue / import function
What happens when you try to import (how far do you get?)
Importing is part of the automated tests which are run on firefox, are
you using a different browser? We have had issues with Microsoft
browsers in the past.
Caleb
Dalluege, Pierre (extern) wrote:
> Hello xwiki users,
>
> After installing xwiki 2.3 (and 2.3.1 afterwards) on Centos5.5 with
> MySQL 5.x and Tomcat 5.5 I still have the issue that I cannot import
> the default .xar file. The same is true for all .xar files: I
> generated one from this wiki and I wanted to re-import it. No chance
yet.
>
> Unfortunately I cannot see any problem on xwiki / tomcat or mysql
level.
> Everything looks fine.
>
> As I shouldn't provide screen shots, you may have a look at
> http://m2m.fm:8080/xwiki/bin/admin/Main/WebPreferences.
>
> I am looking at this topic for some days now, with no result yet. ANY
> IDEAS?
>
> Thank you very much for your support.
>
> Best regards
>
> Pierre
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Hi,
Take a look at Rights 5
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights5Space
Added:
* information regarding the advanced rights (inherits, overrides)
* icons built together as a whole
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights5Space/i…
* representation of "advanced rights" with the same abstract icon, but with
different color (no text; we can debate this)
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights5Space/c…
* inheritance arrow married with +/-
IMGs (in case of browser problem)
- collapsed:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights5Space/r…
- expanded:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights5Space/r…
On Fri, Jun 4, 2010 at 10:42, Denis Gervalle <dgl(a)softec.lu> wrote:
> Hi Caty,
>
> On Thu, Jun 3, 2010 at 18:09, Ecaterina Valica <valicac(a)gmail.com> wrote:
>
> > Hi Denis,
> >
> > I want to thank you again for all the help you are giving :P
> >
>
> This is pleasure to participate especially because you provide really good
> proposals.
> I would also like to see others participating, currently the discussion is
> becoming to much bilateral IMO.
>
>
> >
> > Please take a look at a proposal for "V3 and my 3)" version with elements
> > from Rights2 :)
> >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Proposal
> > and in "action"
> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Space
>
>
> Really nice job ! I really appreciate.
>
>
> > The prototype is not reflecting the "desired" interaction: both inherited
> > info and rights change appear on hover (right icon and arrow), instead of
> > hover | click.
> >
>
> I am not sure what are really your intend. I think that the big tooltips
> describing the rights should be the only tooltips, and should be show on
> hover only after a small timeout (like the yellow one currently). Clicking
> any where on the +/- icon or v would then open the menu.
> Is it what you try ?
>
>
yes, on hover show the tooltip, on click show the menu.
>
> >
> > That "v" needs to be an arrow like the one we use in the action menus.
> >
> > On Tue, Jun 1, 2010 at 19:06, Denis Gervalle <dgl(a)softec.lu> wrote:
> >
> > > Caty,
> > >
> > > Really nice and interesting post, I will try to reach that level... but
> > > without visual :\
> > >
> > > I really think that using the collapsed view for editing would helps
> > basic
> > > users to have a simplified and more easy interface to understand. We
> may
> > > even imagine that only "advanced user" (those marked so in their
> > profile),
> > > has access to the expanded view.
> > >
> > > I think that the collapsed view missed an additional icon that
> summarize
> > > the
> > > rights that are not shown. This one would only be shown if there is any
> > > non-defaulted additional right in action.
> >
> > This is a signal that extended
> > > rights are in use (See it like the grey box of Windows when special
> > rights
> > > are setup, which is inviting to go into advanced view to know more).
> This
> > > one would be obviously not editable, and should probably work like the
> > ...
> > > or replace it ? In place of the ... . Concerning the ..., I am not
> sure,
> > > but
> > > I would also prefer to see a textual link "advanced" in small font, and
> > > only
> > > visible when row is hovered.
> > >
> > >
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Proposal#H…
>
>
> Sorry to insist, but the information regarding the advanced rights is still
> missing in collapsed mode.
> I really would like to have a indicator that some advanced rights has been
> set locally or not without having to go advanced mode. Else, you will have
> to expand all rows to check that information, which is not practical.
>
>
> >
> >
> > > Order of right are not significant, so I would prefer that in all view,
> > > these where in the same order, with the basic right first (V/C/E/D/A/P)
> > and
> > > the additional right in their order of registration (hope that it will
> > stay
> > > constant... or we will have to find a way to keep them ordered).
> > > The "right" part of each icon should be grayed if the right is
> inherited
> > > and
> > > not grayed if the right is set locally, this improve the information
> > > provided in V3.
> >
> >
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights43Proposal#H…
> >
> > The problem with this icons (taken from Silk) is that there is little
> > difference for View, Comment, Admin icons between the two states
> > (inherited,
> > locally set) - but this is something we can easily improve (by changing
> the
> > icons and looking for some more contrast).
> > Example: This is how they look when all rights are set locally (full
> color)
> >
> >
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Rights43Propos…
> >
> >
> >
> > > I also think that the +/- (which is never grayed) could be
> > > nearer to the right icon. Maybe you could use a green V and a read
> "stop"
> > > in
> > > place of +/- ?
> > >
> >
> > The other mockup versions (like
> > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights41Space)
> > used
> > v/x for the allow/deny representation, and yes, I agree that they are
> more
> > suited than +/-.
> >
> > The problem is that we are using in XWiki, X to represent delete, so
> having
> > two xX was too much, that's why I introduced +/-. Maybe we can find
> another
> > solution.
> >
>
> I think we need some polishing on the icons used. Building them
> specifically
> would be nice, but I do not know if you or anyone want to have a try at
> that. My feeling is that the couple +/- or better v/x and the right icon
> should be built together and closer to each other providing the information
> as a whole and not giving the impression of two part. Using a v for
> suggesting the menu is nice, could be even improved by styling some "button
> like" borders on hover.
>
> All menus could also be improved by using the inheritance arrow married
> with
> +/- (or v/x) to show immediately what will be the right if inheritance is
> used.
>
>
> >
> >
> > >
> > > Regarding the collapsed view, I see three possibilities to investigate
> > for
> > > allowing edition while improving readability (note that readability has
> > the
> > > same issue in expanded view, but it seems to be less annoying) :
> > >
> > > 1) use V3, but when hovering a row, use V2 on that row and allow
> > drag/drop
> > > (keeping V2 until drop even is hover is temporary lost). Not sure this
> > will
> > > be nice in practice ? see 2)
> > >
> > > 2) use a presentation in 4 columns, for both collapsed and expanded
> view,
> > > the first column behing a read-only summary like V3, and the 3 column
> > being
> > > an ordered V1. However, dragging from summary would be allowed. The 3
> > > detailed column could be shown only when a drag is started from
> summary,
> > or
> > > with a global horizontal expansion button... Basic user would have
> access
> > > to
> > > this, but not necessarily to vertical row expansion. Not sure this is
> not
> > > an
> > > increase in complexity ? so, see 3)
> > >
> > > 3) use V3, and a similar interface to what we have in current right
> > > management interface. Since saved are postponed (not like we have
> > > currently), using this one may be both practical and could helps the
> > > transition for existing user as well. With all the belts and whistle
> > added
> > > to clearly state changes and inheritance, this will be similar but
> really
> > > better than what we have.
> > >
> > > If we go for V3 and my 3) proposal, I also wonder if the current table
> > > header is well done. I do not like it when nothing is expanded since it
> > is
> > > confusing, too large, and not significant. It will be even more
> > unexpected
> > > if you follow me on the "advance user" case, when a basic user look at
> > it.
> > > Maybe you could try a changing header, only expanding when there is
> > > expanded
> > > row, or, you could move the expanded header in each expanded row,
> keeping
> > a
> > > simplified header at the top.
> > >
> > > WDYT ?
> > >
> > > Denis
> > >
> > >
> > Other problem that this proposal has is the representation of "advanced
> > rights". If we don't like the textual description and we want to add
> icons,
> > IMO we have two solutions:
> >
> > A) use the same abstract icon, but with different color, ex. a key or
> lock
> > icon with color representation ("blue" for "programming", "green" for
> > "captchaComment", etc)
> > - the problem here is for the people that have some kind color blindness
> > and
> > will not distinguish between some color tones (this is the case when we
> > gonna have lots of "advanced" | non default rights)
> >
> > B) use the same abstract icon and with an order index (like numbers 1, 2,
> > etc or characters A, B, etc)
> >
> > These representations are based on the fact that "advanced rights" will
> be
> > added by other developers and the icon will not be custom made for a
> specif
> > right.
> >
>
> Why not just use the big Icons from the menu (using the inheritance arrow
> married with +/- as proposed above), and directly followed by the v arrow.
> All this in front of the text ?
>
inheritance arrow + "right" - to describe "right" as inherited allowed
inheritance arrow - "right" - to describe "right" as inherited denied
+ "right" - to describe "right" allowed
- "right" - to describe "right" denied
yes - we could do that if we decide to use the textual variant.
>
> Using a generic icon will not improve information and detailed view of
> advanced right in collapsed mode is not expected.
>
> It is not clearly shown on your samples, how multiple advance right would
> be
> shown. I think one per row is nice, or if you want to limit space, 2 or 3
> at
> most, shown in columns ?
>
this depends on which version (textual, icons) we choose for the advanced
rights (I would prefer something linear)
> I also wonder is this would help or not to also extends basic rights in
> advanced mode, showing the icons and the text ?
>
> I think this would only add duplicates and mess a bit the meaning of
"advanced" by combining them with "regular".
>
>
> >
> > Another thing we need to consider for this proposal is how the filtering
> is
> > gonna be made.
> >
>
> Good point. Here is some proposal for each column:
>
> 1) a dropdown list proposing local (default), global or both ?
>
I would prefer rights separation depending on the location:
- if you want to see global rights - go to global;
- if you want to see wiki rights - go to wiki,
etc.
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Rights3Proposal#HN…
Why would you like to see both local and global? (filtering?) I think it
will be easier for the user if they are separated.
2) a textbox which filter on names
>
For advanced users would be nice to have queries, like "allow view" AND
"inherit deny delete" :)
> 3) a dropdown list proposing all (default), hide inherited only, and maybe
> the list of rights, showing only rows where the selected right is set
> locally ?
>
>
The dropdown with the list of rights (view, edit, etc.) could also have
another dropdown next to it to set the state of the right (inherited,
allowed, denied)
Thanks,
Caty
Hi,
I'm trying to install xwiki following all the steps included in
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMySQL.
I'm working with jboss and MySQL.
* First I download xwiki-enterprise-web-1.9.3.war then,
* I installed MySQL 5.1 in this step I created the Data base
- mysql -u root -e "create database xwiki"
- mysql -u root -e "grant all privileges on xwiki.* to
xwiki(a)127.0.0.1 identified by 'xwiki'"
- I included the MySQL JDBC Driver JAR in the WEB-INF/lib
folder
- I changed hibernate.xml with mysql properties
* I installed jboss-4.0.5.GA
- I tried to use a datasource but doesn't work for me, so I am
working without it.
As you see, I followed all the steps described in xwiki site, but I have
many errors and I haven't done nothing different
16:47:20,204 INFO [DefaultLoadEventListener] Error performing load
command
org.hibernate.ObjectNotFoundException: No row with the given identifier
exists: [com.xpn.xwiki.doc.XWikiDocument#104408758]
16:47:20,375 WARN [XWiki] Exception while getting wiki preference
[macros_languages]
java.lang.NullPointerException
16:47:20,469 WARN [XWiki] Exception while getting wiki preference
[macros_velocity]
java.lang.NullPointerException
16:47:20,547 WARN [XWiki] Exception while getting wiki preference
[macros_groovy]
java.lang.NullPointerException
16:47:42,032 WARN [XWiki] Exception while getting wiki preference
[macros_mapping]
java.lang.NullPointerException
16:47:43,313 INFO [DefaultLoadEventListener] Error performing load
command
org.hibernate.ObjectNotFoundException: No row with the given identifier
exists: [com.xpn.xwiki.objects.classes.BaseClass#-629142642]
16:47:56,048 INFO [DefaultLoadEventListener] Error performing load
command
org.hibernate.ObjectNotFoundException: No row with the given identifier
exists: [com.xpn.xwiki.doc.XWikiDocument#-1905796263]
16:47:56,439 WARN [XWiki] Exception while getting wiki preference
[backlinks]
java.lang.NullPointerException
I supposed that all of this errors are happening because I have to
install the *.xar files
And then I got this error and that's all. I can't see nothing else.
16:48:03,158 INFO [STDOUT] Hibernate: select xwikidocum0_.XWD_ID as
XWD1_0_0_, xwikidocum0_.XWD_FULLNAME as XWD2_0_0_, xwikidocum0_.XWD_NAME
as XWD3_0_0_, xwikidocum0_.XWD_TITLE as XWD4_0_0_,
xwikidocum0_.XWD_LANGUAGE as XWD5_0_0_,
xwikidocum0_.XWD_DEFAULT_LANGUAGE as XWD6_0_0_,
xwikidocum0_.XWD_TRANSLATION as XWD7_0_0_, xwikidocum0_.XWD_DATE as
XWD8_0_0_, xwikidocum0_.XWD_CONTENT_UPDATE_DATE as XWD9_0_0_,
xwikidocum0_.XWD_CREATION_DATE as XWD10_0_0_, xwikidocum0_.XWD_AUTHOR as
XWD11_0_0_, xwik
idocum0_.XWD_CONTENT_AUTHOR as XWD12_0_0_, xwikidocum0_.XWD_CREATOR as
XWD13_0_0_, xwikidocum0_.XWD_WEB as XWD14_0_0_, xwikidocum0_.XWD_CONTENT
as XWD15_0_0_, xwikidocum0_.XWD_VERSION as XWD16_0_0_,
xwikidocum0_.XWD_CUSTOM_CLASS as XWD17_0_0_, xwikidocum0_.XWD_PARENT as
XWD18_0_0_, xwikidocum0_.XWD_CLASS_XML as XWD19_0_0_,
xwikidocum0_.XWD_ELEMENTS as XWD20_0_0_,
xwikidocum0_.XWD_DEFAULT_TEMPLATE as XWD21_0_0_,
xwikidocum0_.XWD_VALIDATION_SCRIPT as XWD22_0_0_,
xwikidocum0_.XWD_COMMENT as XWD23_0
_0_, xwikidocum0_.XWD_MINOREDIT as XWD24_0_0_,
xwikidocum0_.XWD_SYNTAX_ID as XWD25_0_0_, xwikidocum0_.XWD_HIDDEN as
XWD26_0_0_ from xwikidoc xwikidocum0_ where xwikidocum0_.XWD_ID=?
16:48:03,173 ERROR [[action]] Servlet.service() for servlet action threw
exception
java.lang.NoSuchMethodError:
org.apache.commons.lang.StringUtils.join(Ljava/util/Collection;Ljava/lan
g/String;)Ljava/lang/Stri
at
com.xpn.xwiki.plugin.watchlist.WatchListPlugin.globalSearchDocuments(Wat
chListPlugin.java:596)
at
com.xpn.xwiki.plugin.watchlist.WatchListPlugin.sanitizeWatchlists(WatchL
istPlugin.java:629)
at
com.xpn.xwiki.plugin.watchlist.WatchListPlugin.init(WatchListPlugin.java
:122)
at
com.xpn.xwiki.plugin.XWikiPluginManager.initPlugin(XWikiPluginManager.ja
va:155)
at
com.xpn.xwiki.plugin.XWikiPluginManager.addPlugin(XWikiPluginManager.jav
a:92)
at
com.xpn.xwiki.plugin.XWikiPluginManager.addPlugins(XWikiPluginManager.ja
va:120)
at com.xpn.xwiki.XWiki.preparePlugins(XWiki.java:1022)
at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:742)
at com.xpn.xwiki.XWiki.<init>(XWiki.java:670)
at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:317)
at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:388)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:135)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
ocessor.java:431)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
236)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(Conversion
Filter.java:155)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:117)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:
68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestor
erFilter.java:295)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodi
ngFilter.java:112)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
r.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
sociationValve.java:175)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
ava:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnecti
onValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86
9)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
essConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorker
Thread.java:112)
at java.lang.Thread.run(Thread.java:619)
16:48:13,001 INFO [IndexUpdater] deleting 8 docs from lucene index
16:48:13,189 INFO [IndexUpdater] deleted 8 docs from lucene index
16:48:13,220 INFO [IndexUpdater] indexing 8 docs to lucene index
16:48:13,236 INFO [STDOUT] Hibernate: select xwikidocum0_.XWD_ID as
XWD1_0_0_, xwikidocum0_.XWD_FULLNAME as XWD2_0_0_, xwikid
idocum0_.XWD_CONTENT_AUTHOR as XWD12_0_0_, xwikidocum0_.XWD_CREATOR as
XWD13_0_0_, xwikidocum0_.XWD_WEB as XWD14_0_0_, xwikido
_0_, xwikidocum0_.XWD_MINOREDIT as XWD24_0_0_,
xwikidocum0_.XWD_SYNTAX_ID as XWD25_0_0_, xwikidocum0_.XWD_HIDDEN as
XWD26_0_0_
16:48:13,251 INFO [DefaultLoadEventListener] Error performing load
command
org.hibernate.ObjectNotFoundException: No row with the given identifier
exists: [com.xpn.xwiki.doc.XWikiDocument#723512152]
at
org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFact
oryImpl.java:375)
at
org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventLi
stener.java:143)
at
org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoad
EventListener.java:193)
at
org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEvent
Listener.java:101)
at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
at org.hibernate.impl.SessionImpl.load(SessionImpl.java:784)
at
com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore
.java:641)
at
com.xpn.xwiki.store.XWikiCacheStore.loadXWikiDoc(XWikiCacheStore.java:20
9)
at
com.xpn.xwiki.doc.XWikiDocument.getTranslatedDocument(XWikiDocument.java
:3676)
at
com.xpn.xwiki.plugin.lucene.IndexUpdater.runMainLoop(IndexUpdater.java:2
21)
at
com.xpn.xwiki.plugin.lucene.IndexUpdater.run(IndexUpdater.java:117)
at java.lang.Thread.run(Thread.java:619)
........
I hope that someone can help me!
Thanks in advance!
Carolina Ramirez P
Hi everybody,
I've just downloaded the xwiki-enterprise-wiki-2.3.1.xar default set to
import it in my empty 2.3.1 xwiki. And I think the xar isn't complete.
Indeed, there isn't the new Search Application section in the wiki
administration...
After comparison between the 2.4.1 default set and the 2.3.1 one, I noticed
that the following documents are missing in the 2.3.1 :
- Main.DatabaseSearch
- Main.Search
- XWiki.LuceneSearchAdmin
- XWiki.SearchAdmin
- XWiki.SearchCode
- XWiki.SearchConfigClass
Is it enough if I import them from the 2.4.1 xar or do I need to modify some
other existing pages ?
Thanks,
Marine
--
View this message in context: http://xwiki.475771.n2.nabble.com/Missing-documents-in-3-2-1-default-set-tp…
Sent from the XWiki- Users mailing list archive at Nabble.com.
hey guys,
I'm an individual interested in developing an open-source solution for
a referenced, collaborative textbook. I think that the Xwiki platform is
extremely exciting, and would be ideal for my needs. I would love to use
your community farm to develop and prototype. If you could host me on your
server, that would be excellent. Hopefully, when my skills have developed
more, I could contribute to some of the community project.
Best,
Philip Brunetti
Is there an easy way to systematically copy the date, content (and maybe
comments) of my posts on Blogger into a blog I've created in XWiki?
I've read some articles which suggest reading each blog entry as HTML,
converting that to XWiki markup and then using a XML-RPC to post them
programmatically to XWiki.
I thought about creating XAR files to import but this seems even more
difficult.
Any suggestions?
--
View this message in context: http://xwiki.475771.n2.nabble.com/Importing-a-blog-from-Blogger-tp5140337p5…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi,
we tried to connect our xwiki (version 2.2.2.) to our ActiveDirectory Server
(LDAP).
That failed. So we wanted to use log4j for logging the activities. We
configured it as described in the xwiki documentation. (Adding an
log4j.properties and the debug strings for LDAP.) But there are no
information about the LDAP connection or failures in the xwiki.log.
Did we forget something important?
Hoping for your help.
Martin
PS: We use Xwiki 2.2.2., tomcat 5.5 and MySQL
--
View this message in context: http://xwiki.475771.n2.nabble.com/log4j-doesn-t-log-information-about-LDAP-…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello,
When I start XWiki, all is working but I have a lot of warning in the log.
I'm wondering if it's really "dangerous" or how I can fix it. If somebody
could help me.
I put the warnings log under.
Thanks
Regards
Ben
2010-06-01 12:15:50,800 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.internal.DefaultCoreConfiguration] is being
overwritten by component [com.xpn.xwiki.internal.DefaultCoreConfiguration]
for Role/Hint [role = [com.xpn.xwiki.CoreConfiguration] hint = [default]].
It will not be possible to look it up.
2010-06-01 12:15:50,802 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.render.DefaultVelocityManager] is being overwritten
by component [com.xpn.xwiki.render.DefaultVelocityManager] for Role/Hint
[role = [org.xwiki.velocity.VelocityManager] hint = [default]]. It will not
be possible to look it up.
2010-06-01 12:15:50,802 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.render.XWikiVelocityContextInitializer] is being
overwritten by component
[com.xpn.xwiki.render.XWikiVelocityContextInitializer] for Role/Hint [role =
[org.xwiki.velocity.VelocityContextInitializer] hint = [xwiki]]. It will not
be possible to look it up.
2010-06-01 12:15:50,803 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.render.XWikiScriptContextInitializer] is being
overwritten by component
[com.xpn.xwiki.render.XWikiScriptContextInitializer] for Role/Hint [role =
[org.xwiki.script.ScriptContextInitializer] hint = [xwiki]]. It will not be
possible to look it up.
2010-06-01 12:15:50,810 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.doc.DefaultDocumentAccessBridge] is being
overwritten by component [com.xpn.xwiki.doc.DefaultDocumentAccessBridge] for
Role/Hint [role = [org.xwiki.bridge.DocumentAccessBridge] hint = [default]].
It will not be possible to look it up.
2010-06-01 12:15:50,817 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentEntityReferenceValueProvider]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentEntityReferenceValueProvider]
for Role/Hint [role =
[org.xwiki.model.reference.EntityReferenceValueProvider] hint = [current]].
It will not be possible to look it up.
2010-06-01 12:15:50,825 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentMixedEntityReferenceValueProvider]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentMixedEntityReferenceValueProvider]
for Role/Hint [role =
[org.xwiki.model.reference.EntityReferenceValueProvider] hint =
[currentmixed]]. It will not be possible to look it up.
2010-06-01 12:15:50,832 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentMixedReferenceEntityReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentMixedReferenceEntityReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceResolver]
hint = [currentmixed/reference]]. It will not be possible to look it up.
2010-06-01 12:15:50,840 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentMixedReferenceDocumentReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentMixedReferenceDocumentReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.DocumentReferenceResolver]
hint = [currentmixed/reference]]. It will not be possible to look it up.
2010-06-01 12:15:50,849 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentReferenceEntityReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentReferenceEntityReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceResolver]
hint = [current/reference]]. It will not be possible to look it up.
2010-06-01 12:15:50,856 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentStringEntityReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentStringEntityReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceResolver]
hint = [current]]. It will not be possible to look it up.
2010-06-01 12:15:50,864 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentStringDocumentReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentStringDocumentReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.DocumentReferenceResolver]
hint = [current]]. It will not be possible to look it up.
2010-06-01 12:15:50,872 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentMixedStringDocumentReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentMixedStringDocumentReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.DocumentReferenceResolver]
hint = [currentmixed]]. It will not be possible to look it up.
2010-06-01 12:15:50,879 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentMixedStringDocumentReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentMixedStringDocumentReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceResolver]
hint = [currentmixed]]. It will not be possible to look it up.
2010-06-01 12:15:50,887 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentReferenceDocumentReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentReferenceDocumentReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.DocumentReferenceResolver]
hint = [current/reference]]. It will not be possible to look it up.
2010-06-01 12:15:50,895 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CurrentStringAttachmentReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CurrentStringAttachmentReferenceResolver]
for Role/Hint [role =
[org.xwiki.model.reference.AttachmentReferenceResolver] hint = [current]].
It will not be possible to look it up.
2010-06-01 12:15:50,903 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CompactStringEntityReferenceSerializer]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CompactStringEntityReferenceSerializer]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceSerializer]
hint = [compact]]. It will not be possible to look it up.
2010-06-01 12:15:50,911 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.CompactWikiStringEntityReferenceSerializer]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.CompactWikiStringEntityReferenceSerializer]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceSerializer]
hint = [compactwiki]]. It will not be possible to look it up.
2010-06-01 12:15:50,919 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.model.reference.XClassRelativeStringEntityReferenceResolver]
is being overwritten by component
[com.xpn.xwiki.internal.model.reference.XClassRelativeStringEntityReferenceResolver]
for Role/Hint [role = [org.xwiki.model.reference.EntityReferenceResolver]
hint = [xclass]]. It will not be possible to look it up.
2010-06-01 12:15:50,929 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.DefaultSkinAccessBridge] is being overwritten by
component [com.xpn.xwiki.DefaultSkinAccessBridge] for Role/Hint [role =
[org.xwiki.bridge.SkinAccessBridge] hint = [default]]. It will not be
possible to look it up.
2010-06-01 12:15:50,934 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.hibernate.DefaultHibernateSessionFactory] is
being overwritten by component
[com.xpn.xwiki.store.hibernate.DefaultHibernateSessionFactory] for Role/Hint
[role = [com.xpn.xwiki.store.hibernate.HibernateSessionFactory] hint =
[default]]. It will not be possible to look it up.
2010-06-01 12:15:50,943 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.hibernate.query.HqlQueryExecutor] is being
overwritten by component
[com.xpn.xwiki.store.hibernate.query.HqlQueryExecutor] for Role/Hint [role =
[org.xwiki.query.QueryExecutor] hint = [hql]]. It will not be possible to
look it up.
2010-06-01 12:15:50,953 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.XWikiHibernateStore] is being overwritten by
component [com.xpn.xwiki.store.XWikiHibernateStore] for Role/Hint [role =
[com.xpn.xwiki.store.XWikiStoreInterface] hint = [default]]. It will not be
possible to look it up.
2010-06-01 12:15:50,961 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.XWikiHibernateVersioningStore] is being
overwritten by component [com.xpn.xwiki.store.XWikiHibernateVersioningStore]
for Role/Hint [role = [com.xpn.xwiki.store.XWikiVersioningStoreInterface]
hint = [default]]. It will not be possible to look it up.
2010-06-01 12:15:50,968 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.XWikiHibernateAttachmentStore] is being
overwritten by component [com.xpn.xwiki.store.XWikiHibernateAttachmentStore]
for Role/Hint [role = [com.xpn.xwiki.store.XWikiAttachmentStoreInterface]
hint = [default]]. It will not be possible to look it up.
2010-06-01 12:15:50,975 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.hibernate.HibernateAttachmentVersioningStore]
is being overwritten by component
[com.xpn.xwiki.store.hibernate.HibernateAttachmentVersioningStore] for
Role/Hint [role = [com.xpn.xwiki.store.AttachmentVersioningStore] hint =
[default]]. It will not be possible to look it up.
2010-06-01 12:15:50,978 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.VoidAttachmentVersioningStore] is being
overwritten by component [com.xpn.xwiki.store.VoidAttachmentVersioningStore]
for Role/Hint [role = [com.xpn.xwiki.store.AttachmentVersioningStore] hint =
[void]]. It will not be possible to look it up.
2010-06-01 12:15:50,984 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.XWikiHibernateRecycleBinStore] is being
overwritten by component [com.xpn.xwiki.store.XWikiHibernateRecycleBinStore]
for Role/Hint [role = [com.xpn.xwiki.store.XWikiRecycleBinStoreInterface]
hint = [default]]. It will not be possible to look it up.
2010-06-01 12:15:50,989 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.store.hibernate.HibernateAttachmentRecycleBinStore]
is being overwritten by component
[com.xpn.xwiki.store.hibernate.HibernateAttachmentRecycleBinStore] for
Role/Hint [role = [com.xpn.xwiki.store.AttachmentRecycleBinStore] hint =
[default]]. It will not be possible to look it up.
2010-06-01 12:15:50,994 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.internal.ComponentManagerBridgeEventListener] is
being overwritten by component
[com.xpn.xwiki.internal.ComponentManagerBridgeEventListener] for Role/Hint
[role = [org.xwiki.observation.EventListener] hint =
[componentManagerBridge]]. It will not be possible to look it up.
2010-06-01 12:15:51,000 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.internal.DefaultWikiMacroFactory] is being
overwritten by component [com.xpn.xwiki.internal.DefaultWikiMacroFactory]
for Role/Hint [role =
[org.xwiki.rendering.macro.wikibridge.WikiMacroFactory] hint = [default]].
It will not be possible to look it up.
2010-06-01 12:15:51,003 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.internal.DefaultWikiMacroInitializer] is being
overwritten by component
[com.xpn.xwiki.internal.DefaultWikiMacroInitializer] for Role/Hint [role =
[org.xwiki.rendering.macro.wikibridge.WikiMacroInitializer] hint =
[default]]. It will not be possible to look it up.
2010-06-01 12:15:51,008 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.internal.XWikiStubContextInitializer] is being
overwritten by component
[com.xpn.xwiki.internal.XWikiStubContextInitializer] for Role/Hint [role =
[org.xwiki.context.ExecutionContextInitializer] hint =
[XWikiStubContextInitializer]]. It will not be possible to look it up.
2010-06-01 12:15:51,010 [main] WARN tion.ComponentAnnotationLoader -
Component [com.xpn.xwiki.internal.DefaultXWikiStubContextProvider] is being
overwritten by component
[com.xpn.xwiki.internal.DefaultXWikiStubContextProvider] for Role/Hint [role
= [com.xpn.xwiki.util.XWikiStubContextProvider] hint = [default]]. It will
not be possible to look it up.
2010-06-01 12:15:51,013 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.observation.remote.converter.DocumentEventConverter]
is being overwritten by component
[com.xpn.xwiki.internal.observation.remote.converter.DocumentEventConverter]
for Role/Hint [role =
[org.xwiki.observation.remote.converter.LocalEventConverter] hint =
[document]]. It will not be possible to look it up.
2010-06-01 12:15:51,015 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.observation.remote.converter.DocumentEventConverter]
is being overwritten by component
[com.xpn.xwiki.internal.observation.remote.converter.DocumentEventConverter]
for Role/Hint [role =
[org.xwiki.observation.remote.converter.RemoteEventConverter] hint =
[document]]. It will not be possible to look it up.
2010-06-01 12:15:51,018 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.observation.remote.converter.ActionExecutionEventConverter]
is being overwritten by component
[com.xpn.xwiki.internal.observation.remote.converter.ActionExecutionEventConverter]
for Role/Hint [role =
[org.xwiki.observation.remote.converter.LocalEventConverter] hint =
[action]]. It will not be possible to look it up.
2010-06-01 12:15:51,021 [main] WARN tion.ComponentAnnotationLoader -
Component
[com.xpn.xwiki.internal.observation.remote.converter.ActionExecutionEventConverter]
is being overwritten by component
[com.xpn.xwiki.internal.observation.remote.converter.ActionExecutionEventConverter]
for Role/Hint [role =
[org.xwiki.observation.remote.converter.RemoteEventConverter] hint =
[action]]. It will not be possible to look it up.
2010-06-01 12:15:51,437 [main] WARN tion.ComponentAnnotationLoader -
Component
[org.xwiki.rendering.internal.configuration.DefaultRenderingConfiguration]
is being overwritten by component
[org.xwiki.rendering.internal.configuration.XWikiRenderingConfiguration] for
Role/Hint [role = [org.xwiki.rendering.configuration.RenderingConfiguration]
hint = [default]]. It will not be possible to look it up.
2010-06-01 12:15:51,442 [main] WARN tion.ComponentAnnotationLoader -
Component [org.xwiki.rendering.internal.renderer.DefaultLinkLabelGenerator]
is being overwritten by component
[org.xwiki.rendering.internal.renderer.XWikiLinkLabelGenerator] for
Role/Hint [role = [org.xwiki.rendering.renderer.LinkLabelGenerator] hint =
[default]]. It will not be possible to look it up.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Warning-at-the-start-tp5125382p5125382.ht…
Sent from the XWiki- Users mailing list archive at Nabble.com.