xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Xavier MOGHRABI

Hi, I've tested the latest build of XWiki and I've found a problem about the new User Rights edit interface. In the case of virtual wikis, XWiki doesn't show the users and the groups from the main wiki. This is really a problem for me since all registered users are only in the main wiki and I need to call them by using xwiki:XWiki.user. Regards -- Xavier MOGHRABI - Consortium ObjectWeb Phone: +33 4 76 61 52 35 Skype: xavier.moghrabi.bureau

18 years, 7 months

French corrections in RegisterNewUser

by thomas doucedame

I don't know the impact of " http://www.xwiki.com/xwiki/bin/edit/XWiki/RegisterJS" (probably nothing as I've seen)...

18 years, 7 months

Ludovic's architecture slide

by Julien Bourdon

Hi everyone! I translated the XWiki architecture slide from Ludovic's presentation at the ObjectWeb Conference. May I use it in our public project architecture description? Please feel free to add it to the XWiki documentation anyway. Here is the link: https://www.dcs.shef.ac.uk/wiki/pub/Darwin2005/DarwinThreeDesignXWiki/XWiki… (or http://tinyurl.com/s4lbo). -- _ _ Julien Bourdon (o)(o)--. http://purl.org/net/JulienBourdon \../ ( ) self isAddictedTo:(#Squeak&#linux) m\/m--m'`--. ^true

18 years, 8 months

News about the project and XWiki 1.0

by Ludovic Dubost

Hi, I wanted to give some news about the project and XWiki 1.0 because a lot has been going on in the last week. Thanks to our clients in 2005 and a good start in 2006, we have been able to grow the team and invest a little to improve XWiki and our organization. I'm saying a little because it's still risky to have more full-time employees but we have had the opportunity to get more interns on board and also to launch an off-shore team in Vietnam. As some of you might have been seen, there has been more commits in the last two weeks. The main reason was that I have been in Hanoi, Vietnam to train our new team there. I'm happy to present you Nam and Chung who have joined our team and will be working on the XWiki 1.0 code. During the two weeks a few enhancements have been made on the attachment code and on error handling. Work is also undergoing to improve the WYSIWYG Editor created during the Summer of Code project. In addition to that, we have a new intern (Jean-Vincent) who have joined the team last Monday. Jean-Vincent is from Epitech (the same school as Jeremi) and already has some very interesting Open Source business experience since he worked for IdealX and Linbox. We are very happy to have Jean-Vincent join us. The main objective will be that Jean-Vincent works on the XWiki 1.0 release as the lead developer and project manager. The current objectives for the 1.0 are easy of use and reliability. We are of course always open to suggestions on what should be or not in the 1.0 version. The roadmap is in JIRA. The first objective is to release an updated version called 1.0 Beta 1 which would have the WYSIWYG Editor in Beta. Also Jeremi has done great work from Dalian in China (I would never have thought having so much relationship with Asia !) to help organize the community and also helped a lot answering questions in the users and dev mailing list. On this subject I also want to thank other XWiki users and developers because everytime a question is answered by a member of the community it is very valuable time that I actually save (my kid is also grateful that his dad closes the laptop sometimes). Jeremi's responsibility will be to make sure that the community's voice will be heard during the road to XWiki 1.0. Thanks again for all your support and interest in XWiki. Welcome to the new team members. Ludovic -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

18 years, 8 months

Semantic wiki development: any XWiki related papers?

by Julien Bourdon

Hi all! First of all, let me introduce myself. My name is Julien Bourdon and I study at the University of Sheffield. My research team currently works on a semantic wiki implementation for the UK Environment Agency knowledge management system. We chose XWiki as a wiki layer since it's open-source, well maintained, written in Java and used in corporate environments. However, when we ran through the source code, we could not find any specified documentation. We checked the DevGuide on xwiki.org but the javadoc looks empty. Do you know where we could find any precise documentation about XWiki general architecture, any papers presented in conference or whatever? Any language would be fine since our team is international (I mean even in French since I'm French). Thanks a lot! -- _ _ Julien Bourdon (o)(o)--. http://purl.org/net/JulienBourdon \../ ( ) self isAddictedTo:(#Squeak&#linux) m\/m--m'`--. ^true

18 years, 8 months

Re: [xwiki-users] IDEA: API Documentation wiki

by Ludovic Dubost

Hi, This is a brilliant idea. Indeed this would boost cooperation on the document of the XWiki API. Also I'm a big fan of user comments like for the MySQL documentation. I've thought a little about it and given the amount of work we could throw in on this and the way we currently work on the JavaDocs, I would suggest: 1/ We import the API by reading directly the source code using velocity scripts. We import this into XWiki Objects that comply with the each API structure. 2/ Each function would have it's own page 3/ a form would allow to publish the official documentation of each function 4/ comments would be opened on each page 5/ Links could be automatically created to functions of the same name or using similar Objects or types in the signature 6/ Given the amount of comments already present in the API we could manually copy-paste the current javadoc (a more generic solution would be to be able to import that documentation) 7/ If the work on the Wiki is conclusive and the documentation improves, then we write a program to reimport this documentation in the source code so that we have a javadoc compatible documentation 8/ If some people want to help we write some more program allowing to synchronize the documentation both ways 9/ Using AJAX we could load automatically the source code of a function from the SVN Web Viewer and show it right next to the API when needed. We could even copy the code of the function if we which to make it searchable. I've written a sample script to show how easy it is to extract the list of public APIs from the SVN Web Viewer See http://www.xwiki.org/xwiki/bin/view/JavaDoc/WebHome Who want's to help out writing the classes, forms and importer ? Ludovic THOMAS, BRIAN M (SBCSI) a écrit : > I am quite pumped on XWiki, but the lack of documentation is driving my co-workers bats (I'm already thoroughly nuts, so it doesn't bother me, except when I've got a deadline threatened by not knowing how to do something). > > Ludovic and Jérémi and other tireless souls are suffering with development and support, apparently, and can't get the docs updated, even though some better documentation would at least ease the support burden. Certainly, this mailing list is a major benefit, but searching the archives is a daunting task, since one needs not only to formulate a good query but also to search each and every one of a large number of monthly archives separately (from that perspective, probably a better indexer - one that would allow searching the entire archive at once - would be very helpful. Or, perhaps I misunderstand and there's already a better way? Please comment, someone, if that's the case). > > However, the idea that popped into my head early on this bright St. Louis Thursday morning was: What are the possibilities of Wikifying the API Javadoc pages? In this way, those of us who gain understanding of a particular part can share our hard-bought wisdom, lightening the load for everyone else. > > I have not delved into the uses of doclet technology, but it appears to me that a doclet could format its output as a wiki page could allow the wiki activity to take place as a supplement to the core javadoc output, which remains read-only. > > Further, if the javadoc output provides sufficient versioning information, successive versions of a package, class, or interface could continue to use the wiki annotations until someone noted that the new version changed something that was documented. Perhaps a scheme that recorded the version of a page that was current when the edit or comment is made would be all that was needed, so that whatever version of the javadoc was being explored, the versions of the wiki annotations valid for that version would be displayed. Using date information might be simpler, but it would be more useful to be able to tie a document version to a javadoc file version, because annotations made when a later version was current might have been valid with earlier versions, and a simple date scheme would not allow viewers of those versions to benefit from things documented later. > > So an XWiki template or templates could be made that would filter the Javadoc output, modifying the external javadoc-generated links to retrieve wiki pages named for the documented entities, and displaying any annotations associated with the specific entities. If Velocity isn't up to the job as-is, then (if I understand correctly) a plugin to its rendering engine could explore the DOM model and inject the wiki annotations appropriately. Another way to do it would be to write Javascript so the browser could do the work, which would probably be simpler and save bandwidth on individual page sends, but lose the benefits of server caching. > > The above approach would probably be instead of a doclet, which I think would take the opposite approach and drive the wiki formatting from the javadoc content. This would have the advantage of not needing any plugins or special wiki pages (maybe) and would probably be easier to accomplish but might tend to wrest control of navigation from XWiki in inconvenient ways. > > At any rate, the idea of making the wiki annotations independent of the javadoc pages is a major design goal and could permit anyone anywhere to put up a wiki that allowed annotating any javadoc repository, regardless of whether they controlled its content. > > I've discussed this far too much for one mail message, especially for one who little understands what he's talking about. If there is interest, should we put up a page on xwiki.org to develop the requirements and design? Or has someone already thought of this and it's already available? > > brain[sic] > > -----Original Message----- > From: Erwan Arzur [mailto:earzur@gmail.com] > Sent: Thursday, March 16, 2006 3:27 AM > To: xwiki-users(a)objectweb.org > Subject: Re: [xwiki-users] Hs_err_pid XWiki 0.9.840 + tomcat 5.5.9 + vm1.5.0_06 > > > Hey Leonard, > > yes i'm taking care of xwiki.com. Yes recently it has been a real PITA, most of the instability problem were due to comment spammers hitting us hard. Since last saturday we are running mod_security on our frontend servers and i do not have to check every hour if one of those assholes took us down again ! what a relief ! > > (take care with the latest gotroot rules for mod_security, our apache ate all available memory then had to be killed - blacklist.conf is too big, i don't use it anymore) > > I'll check the system requirement route, but we don't experience VM crashes very often. > > One hint about your particular VM crash. As every thread appears to be locked when it happens, it seems to be garbage collecting related, and i'd investigate tuning the new generation and related stuff. I've got this already on my TODO list and will let you know the outcome. > > I posted a note about this on my weblog > (http://www.arzur.net/index.php?English) where i suggest every spammers taken to courts should pay a check to the OSS anti-spam project of his choice. Another way of financing OSS. Most of the good tools in this field are open source anyway. SpamAssassin, SpamBayes, mod_security, gotroot.com ... come to mind. > > Erwan > > On 3/15/06, Leonard Lin <leonard.lin(a)unic.com> wrote: > >> Hi Yoav >> >> Thanks a lot for your hint. >> As far as i have seen the problems stated on the sun-website are >> concerning Old kernels or older glibc >> >> We use >> Kernel: 2.6.9-11.ELsmp >> glibc: 2.3.4 >> >> Though the following link seems to me heading into a similiar >> direction: >> http://forum.java.sun.com/thread.jspa?threadID=643360&start=0&tstart=0 >> >> regards >> >> -----Original Message----- >> From: Yoav Shapira [mailto:yoavs@computer.org] >> Sent: Mittwoch, 15. März 2006 14:47 >> To: xwiki-users(a)objectweb.org >> Subject: Re: [xwiki-users] Hs_err_pid XWiki 0.9.840 + tomcat 5.5.9 + >> vm1.5.0_06 >> >> Hola, >> As someone with Tomcat (though not XWiki) experience, 99% of the time >> these SIGSEGV faults result from a problem with the JVM installation >> missing required OS patches. Start at >> http://java.sun.com/j2se/1.5.0/install.html, pick the edition you're >> installing, and click on the Linux Notes link from the resulting page >> for required patch levels for things like glibc. I hope that helps, >> >> Yoav >> >> On 3/15/06, jeremi joslin <jeremi23(a)gmail.com> wrote: >> >>> On 3/15/06, Leonard Lin <leonard.lin(a)unic.com> wrote: >>> >>>> Hi >>>> >>>> Are you running xwiki.com on a virtualized system such as VMWare? >>>> One of our programmers suggested, that it might have something to >>>> do with VMWare (in our case) because of the SIGSEGV issued, >>>> Pointing to either errornous implementation in javaVM or failing >>>> Hardware. >>>> >>> No, xwiki.com is running on 3 real computers under Debian Sarge. For >>> the rest, i don't know. >>> >>> Jeremi >>> -- >>> Blog: http://www.jeremi.info >>> LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 >>> Project Manager XWiki: http://www.xwiki.org >>> skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com >>> >>> >>> -- >>> You receive this message as a subscriber of the >>> xwiki-users(a)objectweb.org mailing list. To unsubscribe: >>> mailto:xwiki-users-unsubscribe@objectweb.org >>> For general help: mailto:sympa@objectweb.org?subject=help >>> ObjectWeb mailing lists service home page: >>> http://www.objectweb.org/wws >>> >>> >>> >>> >> -- >> Yoav Shapira >> Nimalex LLC >> 1 Mifflin Place, Suite 310 >> Cambridge, MA, USA >> yoavs(a)computer.org / www.yoavshapira.com >> >> >> >> >> >> -- >> You receive this message as a subscriber of the >> xwiki-users(a)objectweb.org mailing list. To unsubscribe: >> mailto:xwiki-users-unsubscribe@objectweb.org >> For general help: mailto:sympa@objectweb.org?subject=help >> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws >> >> >> >> > > > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the xwiki-users(a)objectweb.org mailing list. > To unsubscribe: mailto:xwiki-users-unsubscribe@objectweb.org > For general help: mailto:sympa@objectweb.org?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

18 years, 8 months

Build XWIki from SVN and conversion of an old xwiki install

by Christian van der Leeden

Hi, just built xwiki from the latest svn. I noticed, that the build.xml file is "wrong". It references the exo 1.0 jars (which are not present any more). I've attached the svn diff below. I just converted our wiki to the latest svn release (it was 0.9-840 before). The first thing I've noticed (which doesn't work anymore) is the reverse proxy through a https server. all urls are correct but point to "http" instead of "https". My guess is, that it is in XWikiServerURLFactory.getServerURL which always adds a "http" in front of the host if the x-forwarded-host was found. CU Christian -- ------------------------------------------ Logic United GmbH Email: leeden(a)logicunited.com Tel: +49-89-189488-66 Index: build.xml =================================================================== --- build.xml (revision 972) +++ build.xml (working copy) @@ -109,7 +109,8 @@ includes="servlet-api-2.4.jar" /> <fileset id="libs.exo.fileset" dir="${lib.dir}" - includes="picocontainer-1.0.jar,exoplatform.container-1.0.jar,exoplatform.services.chart.api-1.0.jar,exoplatform.services.chart.impl-1.0.jar,exoplatform.services.common.api-1.0.jar,exoplatform.services.organization.api-1.0.jar,exoplatform.services.organization.impl-1.0.jar,exoplatform.services.security.api-1.0.jar,exoplatform.services.security.impl-1.0.jar,exoplatform.services.database.api-1.0.jar,exoplatform.services.database.impl-1.0.jar,exo-base-services-1.0.jar,exo-chart-service-1.0.jar,exo-chart-service-impl-1.0.jar,exo-commons-1.0.jar,exo-organization-service-1.0.jar,exo-security-service-1.0.jar" /> + includes="picocontainer-1.0.jar,exo-platform.commons.jar,exo-platform.container-2.0.jar,exo-platform.service.chart.api-2.0.jar,exo-platform.service.chart.impl-2.0.jar,exo-platform.service.common.api-2.0.jar,exo-platform.service.database.api-2.0.jar,exo-platform.service.database.impl-2.0.jar,exo-platform.service.organization.api-2.0.jar,exo-platform.service.organization.impl-2.0.jar,exo-platform.service.sercurity.api-2.0.jar,exo-platform.service.sercurity.impl-2.0.jar" /> +  <fileset id="libs.tests.fileset" dir="${lib.dir}" includes="cactus-1.7.jar,cactus-ant-1.7.jar,aspectjrt-1.2.1.jar,httpunit-1.6.jar,junit-3.8.1.jar,nekohtml-0.9.1.jar,clover-1.3.9.jar,jmock-1.0.1.jar,jmock-cglib-1.0.1.jar,org.mortbay.jetty-5.1.3.jar" />

18 years, 8 months

Back button after preview in IE

by Craig Muth

Didn't get any response from xwiki-users. Hitting the back button after previewing a change to a wiki page results in the change going away, in IE. Steps to reproduce: 1. In XWiki, through MS Internet Explorer, Click "Edit this Page" on any page 2. Add a line at the top 3. Click Preview 4. Click the browser's Back button The line you added in step 2 is gone. This appears to be counter to the default behaviour in IE. I made a test page with a <textarea>, and IE doesn't whipe out the text when I go to another page, and then back. I added the default xwiki meta header tags, thinking that might be the culprit, but that doesn't have any affect. Any ideas? Thanks, --Craig

18 years, 8 months

[xwiki-dev] Why two "add object" forms in editobject.vm?

by Robin Fernandes

Hi, What is the purpose of the second Add Object menu (with a free text input instead of dropdown selection of available classes) on virtual wikis, as defined in editobject.vm:106 by this code? #if($xwiki.isVirtual()) <form id="objectadd2" method="post" action="$doc.getURL("objectadd")" onsubmit="cancelCancelEdit()"> <p style="text-align: center"> <input type="hidden" name="xredirect" value="$xwiki.getFormEncoded($redirect)" /> <input type="text" name="classname" size="20" /> <input type="submit" value="$msg.get("addobjectfromclass")" /> </p> </form> #end Regards, Robin

18 years, 8 months

"velocity" access level?

by Craig Muth

Is it possible to allow a group to edit, but with these restrictions? - Can use wiki syntax - Can't use velocity features (looping and calling macros and functions) I'd like to allow a group to edit pages, but without the risk of their using velocity to call the xwiki database, or make an infinte loop on the page. Thanks, --Craig

18 years, 8 months

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