January 2007 - xwiki-users@xwiki.org

RE: RE: [xwiki-users] Object properties' translations
by Karttunen Petteri 10 Jan '07

10 Jan '07

Thank you Sergiu! That information clarified the issue for me and helps me a lot in planning. I can see from the schema and id generation algorithms that object linking on document translation level is not too simple thing to change. Maybe that’s a little too heavy an issue for me to contribute, but of curiosity: do you have plans already how to solve this? Code in SVN? In any case I’m interested of the panel and page code you mentioned so please send it to me. Thanks! Petteri From: Sergiu Dumitriu [mailto:[email protected]] Sent: 9. tammikuuta 2007 1:25 To: xwiki-users(a)objectweb.org Subject: Re: RE: [xwiki-users] Object properties' translations {quote} If you have more than one objects that must be translated on a page, you cannot use this function, because, as you see, there is no "number" parameter. However, you can write you own code that iterates over all objects. {/quote} Generally, it is recommended to have one main object per page. It is not a must, the final decision is yours, and it depends on the application profile. Sergiu On 1/9/07, Sergiu Dumitriu <HYPERLINK "mailto:[email protected]"sergiu.dumitriu(a)gmail.com> wrote: Hi, Internally, a document has only one principal version, the one in the original language. Translations are just variants of that original document. Objects are attached to a document, meaning that an object is bound to the original document. This way you can't have (for the moment) objects attached to a translation. This is bound to change in 1.1 (or later). However, you can simulate this by using (indeed) a language property. In detail: 1. You must add a StringProperty for each class you would like to be translatable, named "lang" (or any other name you like) 2. Replace doc.getObject("MyClass") with doc.getObject("MyClass", "lang", $context.language[, true]). This return an object with the "lang" property set to the current language. Of course, you can replace $context.language with a specific language. The optional true parameter stands for failover, meaning that if an object with the requested language was not found, try again without the language filter. You cannot automatically translate objects with the current skin. If you are interested, I can give you the code for a panel and a page that can be used for this. If you have more than one objects that must be translated on a page, you cannot use this function, because, as you see, there is no "number" parameter. However, you can write you own code that iterates over all objects. On 1/9/07, HYPERLINK "mailto:[email protected]" \npetteri.karttunen(a)kuopionkonservatorio.fi <HYPERLINK "mailto:[email protected]" \n petteri.karttunen(a)kuopionkonservatorio.fi> wrote: Yes, the wizard works correctly as far as I can see. The problem is perhaps more obvious with tagging for example (default XWiki.TagClass) ; if you want to tag the content of the same page differently depending on the page translation you have to add a TagClass instance for every translation and somehow bind them to translation in question(?) So is there a reason why the object's properties should be language independent? These are fundamental questions for me when planning the structure of my xwiki-based translation portal by no means impassable obstacles. Before fixing the custom class structure I would anyway very much like to hear your thoughts and developers' plans if the logic is going to stay this way in future releases. Thanks! Petteri -- You receive this message as a subscriber of the HYPERLINK "mailto:[email protected]" \nxwiki-users(a)objectweb.org mailing list. To unsubscribe: mailto:HYPERLINK "mailto:[email protected]" \n xwiki-users-unsubscribe(a)objectweb.org For general help: mailto:HYPERLINK "mailto:[email protected]" \nsympa(a)objectweb.org?subject=help ObjectWeb mailing lists service home page: HYPERLINK "http://www.objectweb.org/wws" \nhttp://www.objectweb.org/wws -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.7/619 - Release Date: 7.1.2007 18:29 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.7/619 - Release Date: 7.1.2007 18:29

4 5

includeTopic
by Marc Lijour 10 Jan '07

10 Jan '07

Hi quick question about #includeTopic 's behaviour (I am running 1252). Setup The main page contains a macro #buildPage() which takes an array. This macro calls #includeTopic() in a loop such as this: ## generating the includeTopic calls #foreach( $strand in $strandArray ) #includeTopic("${namespace}.${strand}") #end This macro is included in the main page with #includeMacros(). 2 conflicting behaviours observed 1) XWiki just started (no cache): only the first includeTopic page is rendered, the others are not 2) Once the pages (called in #includeTopic() ) are visited they display fine (I guess this is the work of the cache) Is this a normal behaviour? Any advice? At least is it possible to call programmatically the page to have it rendered in the cache? It is probably not the right way to do it.. Thanks. Marc

1 0

[ANN] XWiki 1.0 Beta 2 Released
by Vincent Massol 09 Jan '07

09 Jan '07

Hi everyone, We're happy to announce the 1.0 Beta 2 release. It's mostly a bug fix release but it also contains some new improvements such as new macros. * Lots of bugs fixed. Most of them are bugs related to the WYSIWYG editor and the new 1.0 skin. * Simplified Edit menu with only a single menu entry. This is to make it simpler for new users. It's possible to switch between Simple and Advanced from the user profile page. * New #info("This is some useful information"), #warning("Careful not to break something") and #error("You did something terrible") macros. * New #floatingbox() macro to display a floating box (aligned right by default). * __text__ is now the notation for underline * Lots of other minor improvements Full list: http://tinyurl.com/yz9ccw Thanks and enjoy -The XWiki Team ___________________________________________________________________________ D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions ! Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses http://fr.answers.yahoo.com

1 0

numbered list
by Duke Tantiprasut 09 Jan '07

09 Jan '07

Is there a way to get the numbered list (i.e. 1.) to continue the numbering instead of restarting if the list item is separated by some text, paragraph, etc? Thanks Duke

1 0

Re: RE: [xwiki-users] Object properties' translations
by petteri.karttunen＠kuopionkonservatorio.fi 09 Jan '07

09 Jan '07

Yes, the wizard works correctly as far as I can see. The problem is perhaps more obvious with tagging for example (default XWiki.TagClass) ; if you want to tag the content of the same page differently depending on the page translation you have to add a TagClass instance for every translation and somehow bind them to translation in question(?) So is there a reason why the object's properties should be language independent? These are fundamental questions for me when planning the structure of my xwiki-based translation portal by no means impassable obstacles. Before fixing the custom class structure I would anyway very much like to hear your thoughts and developers' plans if the logic is going to stay this way in future releases. Thanks! Petteri

2 2

Object properties' translations
by petteri.karttunen＠kuopionkonservatorio.fi 08 Jan '07

08 Jan '07

I'm creating a xwiki-based system where lots of textual metadata in custom metadata objects is systematically going to be attached to pages - which are going to be counted in thousands. When I create a page translation the metadata objects come along - which is desired - but I am not able to translate the object properties for the language in question separately. I had to be able to do that too. Does that mean that I either have to create the metadata classes for every possible language and attach them to translated pages accordingly or that I for example have to add an identifying language property for those classes and attach to a page as many instances of those classes as there are translations for a page? Is there possibly a better way to accomplish this? The system I'm creating is btw going to be a translation database and in this case I would consider it much more usable if the attached objects were dynamically instantiated for the page translations in question. Otherwise 1.0b seems so far just great from this point of view! Thanks in advance for your information! Petteri

2 1

RE: [xwiki-users] Slow public web site
by Gourment, Olivier 08 Jan '07

08 Jan '07

Hi, I am glad to hear that xwiki.org had a spike in visits. Regarding the access to JIRA, I still have a problem and it looks like a DNS configuration issue. Investigations using a DNS diagnostics site give the following results: How I am searching: Searching for jira.xwiki.org A record at i.root-servers.net [192.36.148.17]: Got referral to TLD3.ULTRADNS.org. (zone: org.) [took 187 ms] Searching for jira.xwiki.org A record at TLD3.ULTRADNS.org. [199.7.66.1]: Got referral to lanai.xpertnet.biz. (zone: xwiki.org.) [took 3 ms] Searching for jira.xwiki.org A record at lanai.xpertnet.biz. [195.242.99.118]: Reports that laam.xpertnet.biz. does not exist. [took 196 ms] Response: jira.xwiki.org. exists, and is a CNAME pointing to laam.xpertnet.biz., which does not exist Details: This is a very unusual response, and indicates that the DNS server is authoritative for both jira.xwiki.org. and laam.xpertnet.biz. and that while jira.xwiki.org. exists, it knows that laam.xpertnet.biz. does not exist. See RFC2308 2.1 for details. Thanks, Olivier -----Message d'origine----- De : Ludovic Dubost [mailto:[email protected]] Envoyé : 6 janvier 2007 08:53 À : xwiki-users(a)objectweb.org Objet : Re: [xwiki-users] Slow public web site Hi, We have had both some spam attacks which are slowing down the frontal servers and a spike in visits thanks the the Groovy 1.0 Release news which has mentionned XWiki. We are trying to tweak things around to improve the performance and will consider moving to more powerfull servers.. Is JIRA still down for you ? It's working fine for me. Ludovic Dan Murphy a écrit : > Hi Oliver, > > From personal experience, there can be some longish delays to the > first page access after a server restart as macros etc are compiled. > > Having said that just trying to download > http://www.xwiki.org/xwiki/skins/xwiki10b1/logo.png take a good 1/2 > second - perhaps xwiki.org <http://xwiki.org> isn't deployed to a > hugely powerful server / big a pipe as the other wiki's you've seen. > > With the server I have installed, the performance is acceptable & it's > only running on a 1.4 PIII with 1GB ram desktop machine ! > > Cheers, > Dan > > On 05/01/07, * Gourment, Olivier* <ogourment(a)optimuminformatique.com > <mailto:[email protected]>> wrote: > > > > Hi, > > > > I have been doing some research on wikis and looking at > www.xwiki.org <http://www.xwiki.org/> throughout the week and > observed slow response times pretty much consistently, compared to > other sites on the internet. > > > > http://www.xwiki.org/xwiki/bin/view/Main/WebHome > <http://www.xwiki.org/xwiki/bin/view/Main/WebHome> has taken up to > 15 seconds to display. > > > > What can explain this? > > > > Thanks, > > > > Olivier > > > > > > PS: http://jira.xwiki.org/ is down. > > > > > > > > <http://www.optimumgroup.com> > > > > *Olivier Gourment* > Architecte technologique > Technology Architect > > *OPTIMUM INFORMATIQUE** INC.* > > Téléphone > Télécopieur > *Courriel* > Web > > > > : (514) 288-1661 poste 515 > : (514) 288-8152 > *: ** ogourment(a)Optimuminformatique.com > <mailto:[email protected]>** > : ** www.optimuminformatique.com <http://www.optimuminformatique.com>* > > > > > > -- > You receive this message as a subscriber of the > xwiki-users(a)objectweb.org <mailto:[email protected]> > mailing list. > To unsubscribe: mailto: xwiki-users-unsubscribe(a)objectweb.org > <mailto:[email protected]> > For general help: mailto: sympa(a)objectweb.org > <mailto:[email protected]>?subject=help > ObjectWeb mailing lists service home page: > http://www.objectweb.org/wws <http://www.objectweb.org/wws> > > > -- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic

2 1

Porting from snipsnap to XWiki
by andreas.rami＠bizzons.com 08 Jan '07

08 Jan '07

Hi! I have SnipSnap (1.0b3) (snipsnap.org) running for a few months now. Is there a simple way to switch to a new installation of XWiki? Would be nice to here something about this topic, because XWiki is much better then snipsnap. Best regards Andreas Rami

2 1

Version tagging
by Lijour, Marc (EDU) 07 Jan '07

07 Jan '07

Is there a way to add a comment or some sort of tag to a version (each time we save a document) - as an option? If not it would be nice to have. The history view could display the comment/tag (if any) on another column to the right. I guess it should not be to hard to implement (the issue I would be worry of is about data migration). WDYT? Marc Lijour

4 6

How to get data from XWiki 0.9.840 working on XWiki 1.0 Beta 1?
by Fabian Gorsler 07 Jan '07

07 Jan '07

Hi, we have a XWiki 0.9.840 instance running with Postgres 8.1 and we would like to test the new 1.0b1 release with our existing wikis. How could we transfer the data between the old version and the new? The installation docs don't describe a proper way and just copying the dump of the old data to another database and running XWiki with this db doesn't work, too. The Hibernate mappings seem to have changed. What could we do? Our wiki has grown for about half a year and copying the data manually would take really long. Does there any kind of filter exist? Nevertheless, the 1.0b1 looks really nice. You did a really great work. :) I hope I'll be able to run the 1.0-series soon. :) Best regards, Fabian.

4 6