Re: [xwiki-users] Importation issues
Marine Julian wrote: The first problem is that importation by splitting the document doesn't work in 2.3 version... I tried to split by heading of level 1. It said to me that the importation succeeds and showed me the link to the new page (said Rapports.parent) but when I accessed it I had the The page doesn't exist... Later, I realized that my document was imported in the Main.WebHome page !! Weird ! In fact, the importation succeeded but not where I wanted and asked for ! In fact, I had the equivalent of Rapports.parent in the Main.WebHome i.e. the content and the links to Rapports.child pages. Unfortunately, the links had the [?] of page not existing. Indeed, they links to Rapports.children pages which don't exist : the child pages were also imported behind the parent page (itself behind the content of Main.WebHome)... Does it need to be reported on jira ? I don't know in which case we must do it and if we are allowed to do it (perhaps only devs can report a bug...). Please note that, in wiki farm, from a subwiki, the document is not imported in its Main.WebHome page but in the Main.WebHome page of the admin wiki (Main wiki)... -- View this message in context: http://xwiki.475771.n2.nabble.com/Importation-issues-tp5107820p5120875.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Importation issues
On Mon, May 31, 2010 at 10:01, Marine Julian marine.jul...@gmail.com wrote: Marine Julian wrote: The first problem is that importation by splitting the document doesn't work in 2.3 version... I tried to split by heading of level 1. It said to me that the importation succeeds and showed me the link to the new page (said Rapports.parent) but when I accessed it I had the The page doesn't exist... Later, I realized that my document was imported in the Main.WebHome page !! Weird ! In fact, the importation succeeded but not where I wanted and asked for ! In fact, I had the equivalent of Rapports.parent in the Main.WebHome i.e. the content and the links to Rapports.child pages. Unfortunately, the links had the [?] of page not existing. Indeed, they links to Rapports.children pages which don't exist : the child pages were also imported behind the parent page (itself behind the content of Main.WebHome)... Does it need to be reported on jira ? I don't know in which case we must do it and if we are allowed to do it (perhaps only devs can report a bug...). Sure you have the right to do it ;) When anyone find what is a bug for sure (I did not followed the issue closely here so i don't know) he should always report it on jira (if it's not already there obviously). Please note that, in wiki farm, from a subwiki, the document is not imported in its Main.WebHome page but in the Main.WebHome page of the admin wiki (Main wiki)... -- View this message in context: http://xwiki.475771.n2.nabble.com/Importation-issues-tp5107820p5120875.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Thomas Mortagne ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Reset the stats
Hello, I use a 2.1.2 XWiki XE and the stats are activated. Is it possible to reset the counters of the Stats space ? Don't read anything on this topic in the manual. Thank you for your help. Maxime ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Help using m2eclipse to create an Xwiki java Macro
On 05/29/2010 12:05 AM, James Cuzella wrote: On Fri, May 28, 2010 at 12:46 AM, Vincent Massolvinc...@massol.net wrote: On May 28, 2010, at 1:16 AM, James Cuzella wrote: On Wed, May 26, 2010 at 12:10 AM, Vincent Massolvinc...@massol.net wrote: Hi James, I don't know what the problem is with m2eclipse (I haven't used it to run an archetype) but for the second problem it was because of an invalid dependency. I've fixed it in SVN. For now you can simply edit the generated pom.xml and replace xwiki-core-rendering-parser-wikimodel with xwiki-core-rendering-syntax-wikimodel Thanks for reporting this. -Vincent Thanks, that fixed it! Now have Eclipse working pretty well for coding, however I'm confused how I can debug or run my code within Eclipse for testing. Actually I think you should have a look at http://svn.xwiki.org/svnroot/xwiki/platform/xwiki-tools/trunk/xem-web-debug-eclipse/ It's an Eclipse project that is already configured for hacking XE. Just follow the instruction in the README.txt It's true that you should complement that information with that you found on the Wiki page (e.g., AspectJ configuration, etc.) Anyway I think that you should definitely start from the xem-web-debug-eclipse project. -Fabio ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Importation issues
tmortagne wrote: Does it need to be reported on jira ? I don't know in which case we must do it and if we are allowed to do it (perhaps only devs can report a bug...). Sure you have the right to do it ;) When anyone find what is a bug for sure (I did not followed the issue closely here so i don't know) he should always report it on jira (if it's not already there obviously). I didn't find jira report which deals with this issue so I created a new one : http://jira.xwiki.org/jira/browse/XAOFFICE-48 http://jira.xwiki.org/jira/browse/XAOFFICE-48 . I hope that I created it well... For the second issue I noticed, I think it's better if someone can try to reproduce this behavior. I'm not sure that is really a bug and I don't know where the problem comes. Marine wrote: The second issue (I don't know if it's a real one) : I created a word (.doc) document in which I imported an image (with Word 2007 interface). Then, when I imported the doc in the wiki, the image wasn't imported... Then, I tried by copying the image in the word document (and not importing it) and the wiki importation worked ! Can you reproduce this behavior ? It seems to be a little strange. -- View this message in context: http://xwiki.475771.n2.nabble.com/Importation-issues-tp5107820p5121459.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Reset the stats
Hi Maxime, On 05/31/2010 01:18 PM, GeLo wrote: Hello, I use a 2.1.2 XWiki XE and the stats are activated. Is it possible to reset the counters of the Stats space ? AFAIK there's no API for this purpose and thus no UI. The only thing you can do is to delete the stats records from the database (xwikistatsdoc, xwikistatsreferer and xwikistatsvisit tables). Now, even if you delete the stats recorded for documents in X space (e.g. how many times X.Y page was edited) by deleting the associated records from xwikistatsdoc table, you can't decrease the number of edits made by user A who edited 3 times X.Y page because xwikistatsvisit table contains aggregated visit stats so you don't know how many times A edited pages from X space. Hope this helps, Marius Don't read anything on this topic in the manual. Thank you for your help. Maxime ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Reset the stats
Thank you for your answer. I realize that my previous message was not very clear. My only need is to reset all the counters (for all spaces). I would mean : the statistic counters as they appear in the space entitled Stats. So, I will try to delete the content of theses tables. Best regards, Maxime 2010/5/31 Marius Dumitru Florea mariusdumitru.flo...@xwiki.com Hi Maxime, AFAIK there's no API for this purpose and thus no UI. The only thing you can do is to delete the stats records from the database (xwikistatsdoc, xwikistatsreferer and xwikistatsvisit tables). Now, even if you delete the stats recorded for documents in X space (e.g. how many times X.Y page was edited) by deleting the associated records from xwikistatsdoc table, you can't decrease the number of edits made by user A who edited 3 times X.Y page because xwikistatsvisit table contains aggregated visit stats so you don't know how many times A edited pages from X space. Hope this helps, Marius ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] [Proposal] Rights Management UI
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 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 d...@softec.lu wrote: On Thu, May 27, 2010 at 09:57, Ecaterina Valica vali...@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 vali...@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 d...@softec.lu wrote: Hi Caty, This one is simpler and more easy to understand than
Re: [xwiki-users] [xwiki-devs] [Proposal] Rights Management UI
On Mon, May 31, 2010 at 17:53, Ecaterina Valica vali...@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 d...@softec.lu wrote: On Thu, May 27, 2010 at 09:57, Ecaterina Valica vali...@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 vali...@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
Re: [xwiki-users] Crete xwiki pages from a template
Thanks Marius, That helps :) On Sun, May 30, 2010 at 10:50 PM, Marius Dumitru Florea mariusdumitru.flo...@xwiki.com wrote: Hi Abel, On 05/31/2010 12:05 AM, Abel Solórzano Astorga wrote: Hi, I was wondering what is the best way to give wiki users the possibility to create xwiki pages from a template. I was thinking of something like the CREATE PAGE feature on xwiki but with an additional field called template page. So when the page is created it has the same content as the template page. Is there a plugin or application that already does that? See http://lists.xwiki.org/pipermail/devs/2010-May/018869.html . This new feature will be available in XWiki Enterprise 2.4 final. Hope this helps, Marius Regards, Abel ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Error when installing Watch over an existing xwiki
Hello, I can install and run the standalone version of xwiki Watch with no problems. However, installing Watch app over an existing xwiki causes problems. Steps to reproduce: 1. I download xwiki-watch-1.0.xar 2. I start xwiki 2.3, and import the watch xar. The import tells me it was successfully accomplished 3. In Administration Preferences Programming, I add WatchCode.Translations as an Internationalization Document Bundle, and click Save 4. I go to Spaces, click Watch, and Go To xwiki Watch Reader. I get Error message: watch.errorwithcode - com.google.gwt.user.client.rpc.InvocationException. The call failed on the server: I also notice that under my Spaces in xwiki, WatchCode, WatchQueries, WatchSheets and Packager all have big blue question marks. This did not when I import other xwiki apps Has any one encountered this Error? Can you suggest how I can get around it? Thank you, Thomas ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Error when installing Watch over an existing xwiki
Hi Tom, xwiki watch 1.0 is only working with xwiki 1.4 or 1.5. In order to install an xwiki watch on xwiki 2.3, you'd need to build a 1.1 snapshot from sources, instructions are here http://watch.xwiki.org/xwiki/bin/view/Main/Installation#HBuildingandinstallinganXWikiWatchSnapshotoveranexistingXWikiEnterprise . Also, to build it for 2.3 you need to edit the toplevel pom.xml and replace platform.core.version1.8.4/platform.core.version platform.web.version1.8.4/platform.web.version product.enterprise.version1.8.4/product.enterprise.version with platform.core.version2.3/platform.core.version platform.web.version2.3/platform.web.version product.enterprise.version2.3/product.enterprise.version and gwt.version1.5.3/gwt.version with gwt.version2.0.3/gwt.version Happy hacking, Anca On 06/01/2010 01:19 AM, Tom Stevenson wrote: Hello, I can install and run the standalone version of xwiki Watch with no problems. However, installing Watch app over an existing xwiki causes problems. Steps to reproduce: 1. I download xwiki-watch-1.0.xar 2. I start xwiki 2.3, and import the watch xar. The import tells me it was successfully accomplished 3. In Administration Preferences Programming, I add WatchCode.Translations as an Internationalization Document Bundle, and click Save 4. I go to Spaces, click Watch, and Go To xwiki Watch Reader. I get Error message: watch.errorwithcode - com.google.gwt.user.client.rpc.InvocationException. The call failed on the server: I also notice that under my Spaces in xwiki, WatchCode, WatchQueries, WatchSheets and Packager all have big blue question marks. This did not when I import other xwiki apps Has any one encountered this Error? Can you suggest how I can get around it? Thank you, Thomas ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
