xwiki-devs December 2011

xwiki-devs@xwiki.org

24 participants
49 discussions

[xwiki-devs] [VOTE] Add DocumentAccessBridge#getDefaultDocument(DocumentReference)

by Marius Dumitru Florea

Hi devs, The default implementation of DocumentAccessBridge#getDocument(DocumentReference) has been modified a few months ago [1] to return the translated document. As a consequence, currently there's no way to access the default translation of a document from a component without depending on the old core (i.e. without using XWiki.getDocument()). Thus I'm proposing to add: /** * Retrieves the default translation of a document specified by its reference. * * @param documentReference a document reference * @return the default translation of the specified document * @throws Exception when the storage cannot be accessed * @since 3.4M1 */ DocumentModelBridge getDefaultDocument(DocumentReference documentReference) throws Exception; to DocumentAccessBridge. The default implementation will do exactly what DocumentAccessBridge#getDocument(DocumentReference) was doing before [1]. Note that the default translation of a document is important because it is the only one that provides the document objects. So if you want to access the objects of a document you have to do it through the default translation. Thanks, Marius [1] https://github.com/xwiki/xwiki-platform/commit/f1188a7be56600aa975d7ccc747a…

13 years

[xwiki-devs] brief message

by Ricardo.Julio.Rodriguez.Fernandez＠sergas.es

I know it could be a bit silly to jump into the list after a long silence only of this, but I would like to let you know that I keep following, using and promoting XWiki as much as possible! I've learnt, and keep learning, a lot from this community. Not only about software and collaborative environments. Mainly about how a great working team is created kept growing. Happy Christmas and all the best for 2012! Saúde! Ricardo -- Ricardo Rodríguez Research Management and Promotion Technician Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es ________________________________ Nota: A información contida nesta mensaxe e os seus posibles documentos adxuntos é privada e confidencial e está dirixida únicamente ó seu destinatario/a. Se vostede non é o/a destinatario/a orixinal desta mensaxe, por favor elimínea. A distribución ou copia desta mensaxe non está autorizada. Nota: La información contenida en este mensaje y sus posibles documentos adjuntos es privada y confidencial y está dirigida únicamente a su destinatario/a. Si usted no es el/la destinatario/a original de este mensaje, por favor elimínelo. La distribución o copia de este mensaje no está autorizada. See more languages: http://www.sergas.es/aviso_confidencialidad.htm

13 years

[xwiki-devs] [Proposal] Write a Distribution Maven Plugin

by Vincent Massol

Hi devs, I'd like to propose to write a Distribution Maven Plugin that would have the following features: * Ability to generate XWiki config files. * Ability to generate a full expanded XWiki Distribution. Here are the steps it will do (since I have a first working version I'm pasting what it currently does): ** Step 1: Expand Jetty resources into the package output directory. ** Step 2: Get the WAR dependencies and expand them in the package output directory. ** Step 3: Copy all JARs dependencies to the expanded WAR directory in WEB-INF/lib ** Step 4: Copy compiled classes in the WEB-INF/Classes directory. This allows the tests to provide custom code, for example to override existing components for the test purpose. As an example the link checker might want to override the HTTP Checker component so that checks are not done over the internet since the tests need to execute in a stable environment to prevent false positives. ** Step 5: Generate and copy config files. ** Step 6: Copy HSQLDB JDBC Driver ** Step 7: Unzip the Colibri Skin ** Step 8: Import specified XAR files into the database * Ability to generate a full zipped XWiki Distribution * Ability to import XARs Use cases: * Simplify the current build (XE, XEM, etc) by using this plugin * Use it to generate custom packaging to write functional tests for platform modules * Allow xwiki developers to easily generate custom distributions by handpicking platform modules + their own modules As mentioned above I've worked on this and I'm going to commit a first working version real soon. My current goal is to write some functional tests for the linkchecker-ui module. ATM I have added a new "package" mojo as part of the packager plugin but I'd like to create a new xwiki-platform-tool-distribution-plugin in the future and deprecate the current packager plugin. Thanks -Vincent

13 years

[xwiki-devs] Fwd: XWiki Search not happening even after giving him the proper rights|| Adding user to different group by default

by mohit gupta

Just a minor connection in ISSUE2. here it is :- * ISSUE2:-*.As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically.Actually I want to decide the default group name where user will be added by default based on some condition . i am not getting where should i make the change for this. ---------- Forwarded message ---------- From: mohit gupta <motgupta(a)gmail.com> Date: Thu, Dec 22, 2011 at 5:24 PM Subject: XWiki Search not happening even after giving him the proper rights|| Adding user to different group by default To: devs(a)xwiki.org I have two issues when i am trying to integrate my webapplication with XWiki. One is related to not able to search the content even after giving the proper rights and another is when .As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Below are the details:- * * *Issue1:- *My intention is if an user belongs to particular organisation and he is just a registered user but not admin user for that organization say Accenture he should be able to only view and search that organization spacevotherwise he should not be able to do any operation (not even search and view) on any other space *What I Did for to achieve above* :- I as admin created AccentureUser and AccentureUserGroup . Now i added AccentureUser under AccentureUserGroup. Also I created the space for this organization with Name AccentureSpace. Lets come to Rights Management. As there are two level of rights i.e at Wiki level and Space level. AT Wiki Level:- I gave only view rights to AccentureUserGroup AT Space Level:- I gave only view rights to AccentureUserGroup for AccentureSpace Now when i log in with AccentureUser credentials, i can see AccentureSpace space on a page just after log in but i am not able to search any content(space or page) for this AccentureSpace . Not Getting Why? Do i need to give any other Right too for search? I would be grateful if somebody can provide some insight about above issues on right management.Already I have gone thru below links but did not get through the issues http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement right management http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights access and rights *ISSUE2:-*.As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Posted issue 1 on XwikiUser group also but has not got any reply yet. Looking for quick reply.Thanks in advance.

13 years

[xwiki-devs] XWiki Search not happening even after giving him the proper rights|| Adding user to different group by default

by mohit gupta

I have two issues when i am trying to integrate my webapplication with XWiki. One is related to not able to search the content even after giving the proper rights and another is when .As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Below are the details:- * * *Issue1:- *My intention is if an user belongs to particular organisation and he is just a registered user but not admin user for that organization say Accenture he should be able to only view and search that organization spacevotherwise he should not be able to do any operation (not even search and view) on any other space *What I Did for to achieve above* :- I as admin created AccentureUser and AccentureUserGroup . Now i added AccentureUser under AccentureUserGroup. Also I created the space for this organization with Name AccentureSpace. Lets come to Rights Management. As there are two level of rights i.e at Wiki level and Space level. AT Wiki Level:- I gave only view rights to AccentureUserGroup AT Space Level:- I gave only view rights to AccentureUserGroup for AccentureSpace Now when i log in with AccentureUser credentials, i can see AccentureSpace space on a page just after log in but i am not able to search any content(space or page) for this AccentureSpace . Not Getting Why? Do i need to give any other Right too for search? I would be grateful if somebody can provide some insight about above issues on right management.Already I have gone thru below links but did not get through the issues http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement right management http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights access and rights *ISSUE2:-*.As a part of single sign on process of XWiki with my webapplication i am creating empty user with API context.getWiki().createEmptyUser. But that user is getting added to group XWikiAllGroup <http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup> automatically. I want to add this user to a to a different group say AccentureUserGroup instead of XWikiAllGroup<http://localhost:8888/myxwiki/bin/view/XWiki/XWikiAllGroup>. i am not getting where should i make the change for this. Posted issue 1 on XwikiUser group also but has not got any reply yet. Looking for quick reply.Thanks in advance.

13 years

[xwiki-devs] [Vote][Proposal] New Skin/ColorTheme Improvements for XE 3.4

by Ecaterina Moraru (Valica)

Hi, Ludovic suggested we should refresh the Default Color Theme for XE 3.4 with something new. Since (and long before) we dropped support for IE6 and IE7 (XE 3.2) I wanted to add some CSS3 enhancement to our default skin: shadows, gradients, round corners, etc. So this is a good time to make a proposal that integrates some CSS3 (gradients on menus, panels, tabs, buttons, forms; text-shadows; box-shadows; border-radius;) and a new ColorTheme into Colibri skin: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/34Proposal There are 3 directions that can be voted for this proposal: *Var A:* Integrate the proposed Skin improvements and the new ColorTheme into platform Demo at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WebHome *Var B: *Don't integrate anything in the 3.4 timeframe and wait for a new complete skin in 4.x = Current skin + default ColorTheme (no changes) Demo at http://incubator.myxwiki.org/xwiki/bin/view/Drafts/WebHome *Var C:* Integrate just the new proposed ColorTheme that will replace the current DefaultColorTheme Demo at http://incubator.myxwiki.org/xwiki/bin/view/Standards/WebHome *Important remarks when making a decision:* *Var B* and *Var C *does not involve any changes, problems or advantages from the current Colibri skin. Advantages for *Var A*: - Tested on IE7, IE8, IE9, Opera 11, Chrome 16, Firefox 8, Safari 5 and works beautifully. - Uses CSS3 declarations that makes the skin more nice (gradients, round corners, shades, etc.) Problems for *Var A*: - The existing ColorThemes (from the ColorThemes space and extensions.xwiki.org) will become deprecated for XE 3.4 since the new skin needs shades for the gradients (this means the existing ColorThemes variables will be either used in ways they were not intended or they will not have all the variables declared). See my previous mail about "[Discussion] Problematic ColorTheme extensibility"<http://xwiki.markmail.org/thread/ex6fgou6fl6vjwfr> - The CSS will become even more invalid (right now we have a -moz-border-radius and a word-wrap non valid declarations), but the new code contains 154 declarations for the gradients (covering -moz-linear-gradient, -webkit-gradient, -webkit-linear-gradient, -o-linear-gradient, -ms-linear-gradient, linear-gradient and filter: progid:DXImageTransform.Microsoft.gradient proprietary declarations). The invalidity comes because the proprietary declarations are not yet W3C standard (and will not ever be a standard). The proposed standard W3C declaration (linear-gradient) is not yet supported consistently and correctly by browsers, but when it will become standard we can remove all the other proprietary declarations. Please cast your vote. Thanks, Caty

13 years

[xwiki-devs] [VOTE] Create new xwiki-platform-messagestream-api and xwiki-platform-messagestream-ui modules

by Vincent Massol

Hi devs, Right now the Message Stream feature is split in several places: * xwiki-platform-messagestream/ for the API * xwiki-platform-user/xwiki-platform-user-ui for the Network tab of the user profile (XWikiUserNetworkSheet.xml) * xwiki-enterprise-ui/, in : ** Activity.xml which contains both the AS and the UI to post user messages ** MessageStreamConfig.xml: the admin page for message stream My proposal is to have instead: xwiki-platform-messagestream/ |_ xwiki-platform-messagestream-api/ |_ xwiki-platform-messagestream-ui/ Where xwiki-platform-messagestream-ui/ will contain: * XWikiUserNetworkSheet.xml as is (moved from xwiki-platform-user/xwiki-platform-user-ui) * MessageStreamConfig.xml as is (moved from xwiki-enterprise-ui/) * Creation of a new page (we need to find a name for it), for example: Main.MessageStream, which will contain the UI to post user messages and which will be included from Main.Activity Here's my +1 If you can think of a better split for Activity.xml please put it forward. Thanks -Vincent

13 years

[xwiki-devs] [Proposal] Use the XWiki.org JIRA project more

by Vincent Massol

(I sent this mail once but it didn't make it on the list apparently so resending) Hi devs, I'd like to propose that we use the XWiki.org JIRA project more: http://jira.xwiki.org/browse/XWIKIORG The idea is to create issues in it whenever we see stuff to improve on xwiki.org. I'm also proposing to do the following actions: * Modify it in JIRA so that this project doesn't have any Affects and Fix for fields. The idea is to simple have a list of issues and no releases. * Add some documentation on the contribution page on xwiki.org to explain that creating jira issues for stuff to improve on xwiki.org is a way to contribute too * Send an email to the users list asking people to create jira issues for stuff to improve on xwiki.org * Modify the xwiki.org feedback form on xwiki.org to ask users to create jira issues for stuff they'd like to see improved * Move documentation located in JIRA Platform project (and possibly others) to the XWiki.org JIRA project Are you ok about this? Once this is all done I'll send another email to propose to start again the Doc Days (say one per month). Thanks -Vincent

13 years

Re: [xwiki-devs] How to use WikiWords?

by Hamster

I still can't figure out how to use WikiWords. I have searched with Google on "XWiki +WikiWords", but nothing relevant came up. I have searched the XWiki-site for documentation on how to use WikiWords, but can't find any docs. Does anyone have a clue for me? Thanks! -- View this message in context: http://xwiki.475771.n2.nabble.com/How-to-use-WikiWords-tp7070568p7077791.ht… Sent from the XWiki- Dev mailing list archive at Nabble.com.

13 years

[xwiki-devs] [VOTE] Create new User Application in platfom (and refactor Admin App)

by Vincent Massol

Hi Devs, Right now the Administration Application includes user profiles pages. I'd like to propose to move them to a new user application in platform: - in xwiki-platform-user/xwiki-platform-user-ui (the reason for this directory structure is because in the future we'll probably have an -api module for User API) - or directly in xwiki-platform-user/ FTM and refactor later on when we have the need for a user -api module The rationale for moving the user profile pages out of the Administration app is the following: * IMO we need to make the Admin app only contain technical pages making up the Admin page (i.e. http://localhost:8080/xwiki/bin/admin/XWiki/XWikiPreferences + the technical pages like ConfigurableClass, etc). * We should move specific admin pages to the extensions that bring them. For example WYSIWYG admin pages should be in the wysiwyg application and not in the administration app. * This will allow us to better document each feature. Right now the user has to know that he has to go to the Admin app to find documentation about user profile (which is missing btw ;)), wysiwyg administration, etc. More specifically here are the pages I'd like to move out in XE 3.4M1: * XWikiUserSheet * XWikiUserProfileSheet * XWikiUserPreferencesSheet * XWikiUserNetworkSheet Here's my +1 Thanks -Vincent

13 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs December 2011