xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Yvan JANET

Hi. I've been working for a few days on the implementation of an authentication module to make my XWiki instance compatible with the Web SSO deployed in my company (Sun Access Manager). So I followed the authentication configuration guide to create my new authentication module. The class is compiling well on eclipse, as well as on the server, but it seems that its use in the XWiki app does not work. So I have a few questions that are not answered neither in the API documentation (does it exist ?), neither in the online doc : - what String is awaited by the XWikiUser constructor ? - what String is awaited by the Principal ? As of now, I'm using the user principal of Access Manager - which is a DN (AM uses a LDAP repository) - for both. - what should I put in my WEB-INF/xwiki.cfg instead of "form" in the auth type ? it seems not to work well with this. Thanks in advance. Yvan

17 years, 1 month

[xwiki-devs] Users added to group on each login with LDAP

by Paul Grodt

Greetings all, I'm new to XWiki both as an administrator and as a dev, so please forgive me if I'm a bit mistaken on behavior. I'm running XWiki with authentication through LDAP. I manually added my own username and granted admin privileges to that user. I then switched it to LDAP and set it so other users must login to view anything beyond the main page. Authentication works fine; users are able to login. My problem is that every time they login, a new entry is being added to the XWiki.XWikiGroups object. This can be seen by viewing the 5 pages of a single username in the XWikiAll group. I've checked jira and the list archives for this issue, and I thought I remembered seeing some mention of an issue like this, but on review I can't find anything. I have no doubt that either my LDAP configuration is wrong, or my LDAP server is insane. My XWiki user entry shows up as my LDAP login name, everyone else's shows up as their full name. But that's not my chief concern; I'll figure that out eventually. My thinking is that regardless of configuration, multiple entries of the same name should not be addable to the XWikiGroups object. This should either be inforced by treating it as a set or a map, or by searching the vector prior to added objects. I'm looking in the com.xpn.xwiki.XWiki.addUserToGroup() function (XWiki.java:2940) and I don't see evidence of such a check. I confess I haven't taken the time to look to see if the function is overridden, or how the overridden functions behave, nor have I run XWiki through the debugger yet, but am I right in thinking it should be checked as described here? If I can get some bit of confirmation from someone more familiar with the code, I'll gladly make a patch. Paul D. Grodt TECORE Wireless Systems Phone: +1 410 872 6225 Fax: +1 410 872 6010 email: pgrodt(a)tecore.com

17 years, 1 month

[xwiki-devs] [ApplicationManager] [Proposal] Insert matching string in the list of documents

by Thomas Mortagne

Hi all, Actually application descriptor contains a field that list all document application contains. I would like to add to Application Manager a way to be able to add "all the documents of space SpaceName" for example. I already implemented a solution and I would like you to comment and me to modify if needed. When XWikiApplication.resolveDocumentsNames is called, it list all document and one by one look if the document name is between "[" and "]", if so it consider document name as sql matching string usable with "like". So for example you will add "[XWiki.%]" if you want to add all documents in the XWiki space to the application document list. This feature is supported for "documents list" and also "document list to include" WDYT ? -- Thomas Mortagne

17 years, 1 month

[xwiki-devs] How to update Groovy from 1.0 jsr 06 to 1.0 stable?

by G.Schoepp

Hi, does anybody have an idea on how to update Groovy to 1.0 stable? IMHO this will affect a lot of XWiki documents. Will this affect the xwiki core library too? Guido

17 years, 1 month

Re: [xwiki-devs] scroll bar

by goldring, richard

Anuj, You can put this on the page: <DIV STYLE="overflow: auto; width: 900px; height: 500; border-top: 1px gray solid; border-left: 1px gray solid; border-bottom: 1px gray solid; padding:0px; margin: 0px"> ...put your page contents here </DIV Only if you edit it with the WYSIWYG editor it reformats this code so there's no overflow i.e. the XWiki style macro doesn't support overflow for scrollbars. Anyone know how the style macro can be updated to support 'overflow'? Could XWiki pages support scrollbars by default? - especially useful for large tables! It would be good to be able to hide the menu bars when not needed - have since this on other wiki implementations. Hope that helps. Regards, Richard -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of anuj sharma Sent: 05 October 2007 06:50 To: devs(a)xwiki.org Subject: [xwiki-devs] scroll bar Hi all, Can we add scroll bar in a page ? What if we can't see the picture or text at the right of the page as it gets overlapped by panels.......????? thanks, ANUJ SHARMA. _____ Unlimited freedom, unlimited storage. Get <http://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mai l/yahoomail/tools/tools-08.html/> it now Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 1 month

[xwiki-devs] scroll bar

by anuj sharma

Hi all, Can we add scroll bar in a page ? What if we can't see the picture or text at the right of the page as it gets overlapped by panels.......????? thanks, ANUJ SHARMA. --------------------------------- Unlimited freedom, unlimited storage. Get it now

17 years, 1 month

[xwiki-devs] e-mail field in registration page

by anuj sharma

Hi all, an anybody please tell me how can i make the e-mail field on the registration page mandatory??? Also,where does these registration information get stored???? thanks, ANUJ SHARMA. --------------------------------- Why delete messages? Unlimited storage is just a click away.

17 years, 1 month

[xwiki-devs] Plugins and xwiki.cfg

by Erin Schnabel

I had a thought,as I sit here pulling up 1.1.1(finally), is there a reason we have so many plugins enabled by default? I'm not even sure anyone knows how to use most of the ones that are enabled. AND, as they're plugins, they shouldn't be on or enabled unless they're actually needed. I propose a space: XWikiPluginGuide. Each plugin would have a page in the guide describing: a) how to enable the plugin, b) what options are used by the plugin, c) how to invoke and use the plugin, and optionally d) who wrote the plugin and the version information (which that document could retrieve via a getVersion, getAuthor, or whatever call back to the plugin). A lot of plugins have a place where they check to make sure that document artifacts that they need exist. One of the things they would check is if "PluginGuide.pluginname" exists, where pluginname is what they return in response to getName(). If "PluginGuide.pluginname" doesn't exist, they'll create one, setting the title, etc. They *could*, in theory, either add a field to that document or use the document's inherent version to decide whether or not the document should be all out replaced at some later point, so that when the plugin is updated/loaded, the page is updated. The plugin code itself is the repository of all knowledge as far as what xwiki properties it understands, how the methods should be invoked, etc. That way, if I want to know how to use the feed plugin, I can just go to PluginGuide.feed, and find out. THEN... Since we have options documented in the plugin guide, we can remove blocks like this from xwiki.cfg: # To enable it, add "com.xpn.xwiki.plugin.graphviz.GraphVizPlugin" to the list of plugins # in the xwiki.plugins property. # Uncomment and set the locations of the Dot and Neato executables #xwiki.plugin.graphviz.dotpath=c:/Program Files/ATT/GraphViz/bin/dot.exe #xwiki.plugin.graphviz.neatopath=c:/Program Files/ATT/GraphViz/bin/neato.exe Same with lazlo, captcha, LDAP, etc. Anything that can be turned off should be removed from xwiki.cfg w/ appropriate PluginGuide docs describing how to turn it back on. If we *can't* turn it off, meaning that the default skin needs it, then we should note that, eh? I think the calendar plugin, for example, is used by more than just the EventCalendar pages (though I forget exactly where at the moment.. but it's in the code, not in the templates). If the plugins become too central to wiki function, like the Packager plugin, for instance.. it isn't a plugin anymore, and shouldn't be in the xwiki.plugins list in xwiki.cfg. To steal an acronym from Vincent, WDYT? :-P -- 'Waste of a good apple' -Samwise Gamgee

17 years, 1 month

Re: [xwiki-devs] [ApplicationManager] [Proposal] Insert matching string in the list of documents

by goldring, richard

Hi, Does anyone know if the bug with XWiki rendering carriage returns has been fixed in the latest version of XWiki? My users don't like this 'feature' at all - they like to structure their text into paragraphs. Richard -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Thomas Mortagne Sent: 04 October 2007 09:40 To: XWiki Developers Subject: Re: [xwiki-devs] [ApplicationManager] [Proposal] Insert matching string in the list of documents I also would prefer to use subspaces but without that I much more prefer separate all aspect of an application in different spaces. In almost all use cases users only access XApp and XAppManager that contains only user oriented interfaces. 2007/10/4, Vincent Massol <vincent(a)massol.net>: > I would also use a single space at first glance. Make things better > isolated. > > What we really need are sub spaces or rather hierarchical paths. See > http://jira.xwiki.org/jira/browse/XWIKI-354 > > -Vincent > > On Oct 4, 2007, at 2:00 AM, Erin Schnabel wrote: > > > Now that I've picked it up... > > Is there any real reason why the AppManager has to span 6 spaces? > > > > I can understand having XAppManager, and perhaps XAppUtil or > > XAppResource (XAppApp doesnt' really work.. :-) but I don't like > > having XApp, and XAppClasses and XAppManager and XAppResources and > > XAppSheets and XAppTemplates.. > > that's just a waste of spaces... users ask for lists of spaces all of > > the time.. why should we be adding so many? > > > > I would prefer: > > > > XApp.XWikiApplicationXapp > > XApp.XWikiApplicationXwikiapplicationclass > > > > XAppManager.CreateApplication > > XAppManager.WebHome > > XAppManager.Translations > > XAppManager.XWikiApplicationClass > > XAppManager.XWikiApplicationClassSheet > > XAppManager.XWikiApplicationClassTemplate > > > > XAppManager is then clearly the XAppManager application, and XApp's > > are the applications it manages. I REALLY REALLY REALLY don't like > > having things spread out spaghetti in a lot of spaces... Maybe that's > > fine on small installs, but when you have 100 or so spaces, it's > > annoying to spontaneously pick up 4 more... > > > > > > > > On 10/1/07, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > >> 2007/10/1, Thomas Mortagne <thomas.mortagne(a)xwiki.com>: > >>> Hi Stéphane, > >>> > >>> 2007/10/1, Stéphane Laurière <slauriere(a)xwiki.com>: > >>>> Thomas Mortagne wrote: > >>>>> Hi all, > >>>>> > >>>>> Actually application descriptor contains a field that list all > >>>>> document application contains. > >>>>> > >>>>> I would like to add to Application Manager a way to be able to add > >>>>> "all the documents of space SpaceName" for example. > >>>> > >>>> That would be a nice feature indeed. > >>>> > >>>> I started using the ApplicationManager for the XWiki help desk > >>>> app. The > >>>> management of translations is really handy! I'm adding "{table}" at > >>>> the beginning and the end of the list of properties for a better > >>>> display. > >>>> > >>>>> I already implemented a solution and I would like you to > >>>>> comment and > >>>>> me to modify if needed. > >>>>> > >>>>> When XWikiApplication.resolveDocumentsNames is called, it list all > >>>>> document and one by one look if the document name is between > >>>>> "[" and > >>>>> "]", if so it consider document name as sql matching string usable > >>>>> with "like". So for example you will add "[XWiki.%]" if you > >>>>> want to > >>>>> add all documents in the XWiki space to the application document > >>>>> list. > >>>> > >>>> Sounds ok to me, but do we really need the brackets? > >>>> > >>>> Couldn't we simply write this type of list: > >>>> XAppManager.%|XAppResources.Translations > >>> > >>> I added % for... lets say security reasons as an URL and so a page > >>> name can contains "%" I thinks but not very sure on that. > >>> > >>>> > >>>> It would then be parsed and submitted to the sql engine directly, > >>>> couldn't it? We could use the "like" clause for all > >>>> occurrencies, or > >>>> check whether each occurrence contains the character '%' in case > >>>> the > >>>> "like" clause is more heavy than an exact match clause. > >> > >> I forgot, I said "one by one" but all "[]" matching in a list are > >> merged in only one sql request. It can also be easily merged between > >> applications and all his dependencies too. > >> > >>>> > >>>>> This feature is supported for "documents list" and also "document > >>>>> list to include" > >>>> > >>>> Actually, what's the purpose of the field "document list to > >>>> include" and > >>>> "document links"? I couldn't find the info from the online > >>>> documentation > >>>> at http://www.xwiki.org/xwiki/bin/view/Code/ > >>>> ApplicationManagerApplication > >>> > >>> "includes" and "links" target multi wikis. It is the pages that are > >>> included or linked when create a wiki from a template wiki. It is > >>> used > >>> to configure what is shared between wikis. > >>> > >>> "Links" is not used yet as it need not supported feature in XWiki : > >>> real links between pages, I forgot to hide it in interface. > >>> > >>>> > >>>> Cheers > >>>> > >>>> Stéphane > >>>> > >>>>> WDYT ? > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 1 month

[xwiki-devs] applications & plugins

by Erin Schnabel

I am just full of feedback today. Is there a reason that an application (which would of course go in a xar) is created so far away from the plugin it's interdependent with? i.e. the Application Manager is one application that consists of both XWiki documents in a xar file and an Xwiki plugin. Having one half in plugins, and the other half in applications doesn't make a lot of sense-- they're one thing. The same goes with some of the other plugins, actually.. Some might have macros associated with them, and maybe they want those macros to be in the DB. A few of the plugins get around this by creating the documents they need programatically (as I suggested with the PluginGuide), but it seems like there has to be a better way of managing "plugins with an application face" then having them in separate trees. Then again, maybe I'm nuts. :-P -- 'Waste of a good apple' -Samwise Gamgee

17 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs