xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] Ideas on preventing problems in the database caused by a bug (e.g. XWIKI-1841)

by Fabian Gorsler

Hi, due to the translation bug (XWIKI-1841) I spent some time looking for inconsistent rows in our database (Postgres 8.1) and I found several documents inserted twice into the database, which lead to problems when editing and viewing the documents. For luck our coporate wiki has just 23 pages with problems caused by this bug (the same xwd_fullname with different xwd_id fields / the select statement can be found at the end of this mail, perhaps anyone is intrested in). The thing I'm quite confused about is that there are no unique constraints set on the the columns which could have prevented these problems. The DBMS would have forced the XWiki core to generate an error instead of inserting inconsistent data sets into the database. I neither know much about Hibernate, nor I have tested whether XWiki would use constraints with other DBMS, but would it be possible to set those constraints in future versions? At the moment I'm quite scared about reactivating I18N for our corporate wiki, because an similar programming might occour again, but with a clean constraint setup, those errors would not happend silently in the background, but instead appear as they occur transparent to everyone. From my point of view it should be possible to set an unique constraint on xwd_fullname and xwd_language. Up to now I did't understand why there is a need for the fields xwd_default_language and xwd_translation, but on the other I didn't investigate any time in this. Wouldn't it be enough to have the fields xwd_fullname and xwd_language? (The next thing is: Why is there a need for xwd_web, xwd_name and xwd_fullname? - Just because I'm curious.) Are there any similar thoughs? What do you think? For a modern DBMS (not MySQL 3.23 ;)) shoud be able to "support" XWiki and to prevent inconsistencies and corruption of data. But nevertheless I love XWiki 1.1! The renaming feature and the panel support are great. Just these two new features made any problems during the migration from 0.9.840 forgotten. :) The mentioned query from above for searching inconsistent rows in the database (working for Postgres 8.1): select xwd_fullname, xwd_version from xwikidoc where xwd_fullname in (select xwd_fullname from xwikidoc group by xwd_fullname having count(*) > 1) order by xwd_fullname; -- Best regards, Fabian.

16 years, 12 months

[xwiki-devs] Revert XWIKI-1802 (Detete all version related fields in XWikiDocument.toXMLDocument when withVersion=false)

by Thomas Mortagne

Hi all, I'm reverting http://jira.xwiki.org/jira/browse/XWIKI-1802 as it break some (rare but existing) use cases. I spoked with Vincent about some solutions to be able to export documents without version related informations and I will look about it a bit more. How we see that actually is to add a new parameter like "resetVersionInfos" (or "resetTechInfos" or anything else I'm not sure yet) which handle "author", "creationDate" etc. and force "withVersions" to false. See also http://tinyurl.com/2sx7s4 for initial thread on this subject. Thanks, -- Thomas Mortagne

16 years, 12 months

Re: [xwiki-devs] Default size for upload_maxsize? sorry, ignore the contents of my last message

by jvivien.m2 jvivien.m2

sorry, didnt read the mails properly. please ignore the contents of my last message

16 years, 12 months

[xwiki-devs] XWiki @ Javapolis

by Guillaume Lerouge

Hi fellow XWikiers, a quick e-mail to tell you that 3 XWiki team members will be at Javapolis ( http://www.javapolis.com/ ) in Antwerp, Belgium, from the 12/12 to the 14/12 2007. Javapolis is the biggest yearly Java event in Europe. Vincent Massol, Jean-Vincent Drean and me will be there to answer every question you may have about XWiki. You'll have the opportunity to meet people from other OW2 projects such as eXo too. Please let us know whether you'd be interested to attend the conference on the dedicated XWiki Facebook Event page at http://www.facebook.com/event.php?eid=14478490493 . You can check out XWiki's booth location on the floor plan (available on XWiki.org at http://www.xwiki.org/xwiki/bin/view/Blog/XWikiAtJavapolis2007 ) Looking forward to seeing you there, The XWiki team

16 years, 12 months

[xwiki-devs] [VOTE] Include Statistics into 1.2RC1?

by Vincent Massol

Hi, Marius has just submitted a patch for the Statistics feature. See: - http://jira.xwiki.org/jira/browse/XE-37 (UI) - http://jira.xwiki.org/jira/browse/XWIKI-1845 (API) I'd like to vote for including this in 1.2RC1. Even though RC is about improving the stability and fixing bugs I think we should include it for the following reasons: * It's a nice new feature, much needed * It's independent from the rest and won't impact the stability If we're not comfortable with having it in RC1 then we should create a 1.2M3 release and release it once the patch has been applied. However an extra release is quite some work (a full day of work + the associated stresss ;)) so I'd rather have it as part of 1.2RC1. So here's my +1 Thanks -Vincent

16 years, 12 months

[xwiki-devs] [ANN] XWiki Enterprise 1.2M2 Released

by Vincent Massol

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.2 Milestone 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the last milestone release for the 1.2 version. It's packed with new features and improvements. The next version will be 1.2 RC 1 and will focus on improving the stability. The roadmap is to release 1.2 final for beginning of December 2007. Main changes from 1.2M1: * Completely redesigned the UI for managing permissions and groups/ users. It's now a nice Ajax interface which scales to any number of users. * A new Mail Sender plugin has been added. It's a generic plugin that you can use from Velocity/Groovy pages and that is also used by the Watchlist feature below to send notification emails. * New Watchlist feature which allows watching pages and spaces and receive email notifications when they are modified. * The Scheduler Plugin and the Scheduler Application have been released in version 1.1 and are bundled with XWiki Enterprise 1.2 milestone 2. They allow you to create jobs (Groovy scripts) to be executed in the future. They are used for example in the Watchlist plugin to send email notifications for pages or spaces you are monitoring. * New displayPanelLayout Macro to display Panels in page. * New JODA Time plugin to allow using JODA time from Velocity/Groovy pages. * The top level edit menu has been reorganized. Separators have been added, the Rename and Delete actions have been moved in an Action menu and a new Watch menu has been added. * Entering URLs such as http://myserver/xwiki goes to the Main.WebHome page by default (it used to display some installation instruction page). * Panels from other virtual wikis can be used now. * Lucene Search UI and stability has been improved. * Removed the Presentation application from the default wiki (since it was not maintained and was buggy). + bug fixes and other improvements For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise12M2 Thanks -The XWiki dev team

16 years, 12 months

[xwiki-devs] openguide: plugins and skins

by Luis Alves Ferreira

Hi, I'm building a customized version of the xwiki enterprise. So far i've created a new skin and a new plugin. I want to: - define the new skin as default. I mean, instead of changing the xwiki.cfg or the skin class i would like to make it default at compile level. Everytime i do mvn install i should be selected as default. - include my new plugin in WEB-INF/lib automatically everytime i compile (just like the other plugins - jodatime etc) thank you very much for you attention. regards, Luis Ferreira

16 years, 12 months

[xwiki-devs] Migration from v0.9 to v1.2

by "Víctor A. Rodríguez"

Hi all, I'm fairly new to this list. Please forgive me for any inconvenience. With the new XWiki version on the road I just resume my migration assignment from v0.9 t v1.2. Let us make a little review: when trying to import the xar file to v1.2 (take a look at http://www.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HUpgradinganXWi…) it fails with a java.lang.NullPointerException As I can see it brokes at com.xpn.xwiki.web.ImportAction.render(ImportAction.java:42), but couldn't see why (yet?) I plan to fill a bug report and try to fix it (humbly I'm not sure of a success history here, but I'll try ...), so my questions are : * I need to add a new bug report or just add more info to the one already opened (http://jira.xwiki.org/jira/browse/XWIKI-1809). In my case is a null pointer exception when tries to open the file, but in the reported one its caused when tries to parse the xmlfile * Anyone is having the same problem and have fixed it or created a workaround ?? TIA -- Víctor A. Rodríguez (http://www.bit-man.com.ar) El bit Fantasma (Bit-Man) - Algorithm junkie Perl Mongers Capital Federal (http://cafe.pm.org/) GNU/Linux User Group - FCEyN - UBA (http://glugcen.dc.uba.ar/

16 years, 12 months

[xwiki-devs] [Proposal] Change content of feed article documents fetched by feed plugin

by ancapaula.luca＠xwiki.com

Hi all, I would like to change the feed plugin so that the content of the fetched documents can be easily changed. Currently, the content of the document containing a fetched article is hardcoded to "#includeSheet('XWiki.FeedEntryClassSheet')". I think that any code using the feed plugin should be able to set its own sheet or whatever content is needed. There are a couple of options to be analyzed: 1. regarding the content of the feed article document: a) any feed article includes a sheet b) any feed article contains some content, not necessarily a sheet inclusion. 2. regarding the way the content is set: a) through a String variable in the feed API, that can be set by the user through a call like xwiki.feed.setDefaultFeedDocContent("some content"), which defaults to the current value, for compatibility with the code already using the feed plugin. b) through an optional parameter to the updateFeed function(s) such that, each time the feeds are fetched the content can be specified 3. regarding the 'scope' of this default content for the feed entry document: a) it is specific to a feed aggregator and is set in the aggregator class b) it is specific to an update operation (as mentioned on 2.b) c) it is specific to the feed plugin and all documents through that plugin instance will have the same content (as specified on 2.a) WDYT?

16 years, 12 months

Re: [xwiki-devs] [xwiki-notifications] r6023 - trunks

by Vincent Massol

On Nov 19, 2007, at 5:41 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2007-11-19 17:41:09 +0100 (Mon, 19 Nov 2007) > New Revision: 6023 > > Modified: > trunks/pom.xml > Log: > Remove core and web from xem profile because XEM depends on 1.1 > branch. ah right, sorry... Thanks -Vincent > > > Modified: trunks/pom.xml > =================================================================== > --- trunks/pom.xml 2007-11-19 16:27:37 UTC (rev 6022) > +++ trunks/pom.xml 2007-11-19 16:41:09 UTC (rev 6023) > @@ -70,9 +70,7 @@ >  > <id>xem</id> > <modules> > - <module>xwiki-platform-core</module> > <module>xwiki-platform-plugins</module> > - <module>xwiki-platform-web</module> > <module>xwiki-platform-applications</module> > <module>xwiki-product-enterprise-manager</module> > </modules>

16 years, 12 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