xwiki-users April 2015

xwiki-users@xwiki.org

42 participants
105 discussions

[xwiki-users] Fw : Re: Fw : livetable with multiple class?

by Pascal BASTIEN

> > I found my > query, something like this: > > #set($hql = > "select obj.name, prop.value from BaseObject obj, > StringProperty prop where ( > obj.className='FormSMQ.EAClass' or > obj.className='FormSMQ.PiacJ2Class' ) and > prop.id.id=obj.id and > prop.name='TypeFiche_RO'") > > > > > Now > I need the JSON format of my JSON data provider (resultPage > parameter: full name of the page to use as a JSON data > provider for the table) > > You > can use https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… > as an example of a custom results page. Thanks, I will give a try. With ResultPage, I wonder if I could use select list of livetable. Thanks you VERY much to make my week-end busy ;-)

10 years, 1 month

[xwiki-users] Fw : Re: Need help with xwiki search engine

by Pascal BASTIEN

> > > - > "search page" searching only Id value and not lib > value (of course because it is the id value that is stored > in EAClass object) > > i.e. I found pages, > if I search "25_dgec" but not if I search > "DGEC" > > Yes, this > is 'normal' because ATM only the raw value (id) is > indexed > for Database List properties. > > > - Result "search > page" displayed property name (and not the pretty name) > FAQ have same issue. > > - my solr facet > displayed my id value too. > > > > Do you know how can I fix this issue (if > someone understand my problem ;-) )? > > > Here I paste a nice screenchot: http://snag.gy/Joa7q.jpg > > ATM there's no solution > for the search results highlights. The > property name displayed there is part of the > highlight (the matched > text) and it cannot > be parsed (if the property value is large enough > and the match is somewhere at the end then the > property name is not > even included in the > match). > To resolve the problem I use lib column to display correct value (and not the id) > Regarding the raw > value (id) displayed in the facet, you can write a > custom facet that displays the label > corresponding to the raw value. > Yes I manage to did this solution, but I was confronted at multi class problem (again) Thxs anyway, I store pretty name in my Page with Class.

10 years, 1 month

[xwiki-users] Synchronize two XWiki installations

by Nicolas Delsaux

Hi, As I tried XWiki, I used my laptop as server with the Windows standalone install. Now, I want to have XWiki installed on a standard server with a standard DB/web server using the XWiki RPM (I guess this RPM will not install Jetty/SQLite, but Tomcat/??). But, I would better not have to reinstall the various extensions, recreate the users (with the same login/passwords) and rewrite the pages I already have. Is there any synchronisation mechanism available that would allow me to give the "official" XWiki my "prototype" one as a kind of upstream server and make sure their content and config is synchronized ? Thanks -- Nicolas Delsaux

10 years, 1 month

[xwiki-users] Links not Opening in New Tabs / Windows

by Shawn Woods

We are having an issue where some links that have been created are not opening up in a new tab or window. An unregistered user is prompted to download the linked attached document rather than opening up in a new tab or window, even if the option is set in the link. If the contributor that created the link does not have program right, we see the above behavior. If the admin account created the link, it works as expected. We are on version 6.3 Please advise. This e-mail, and any attachments, is intended only for the use of the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments, is strictly prohibited. If you have received this e-mail in error, please notify me via return e-mail immediately and permanently delete the original from your computer. Thank you, Mangar Industries Inc.

10 years, 1 month

[xwiki-users] Need help with xwiki search engine

by Pascal BASTIEN

Hello I created an application: - my Class EAClass contain a field DG MOA * : (P1_DgMoa: Database List) Display Type: select Sort: Id XWiki Class Name: FormSMQ.ListeDGClass Id Field Name: DGId Value Field Name: DGLib My Class (source of select list) FormSMQ.ListeDGClass have 2 fields: DG Id (DGId: String): contain l'Id of my list DG Lib (DGLib: String): contain lib (pretty name like) who is displayed on my list select. My data are: DGId:20_dgaln / DGLib: DGALN DGId:25_dgec / DGLib: DGEC DGId:30_dgitm / DGLib: DGITM ... Everything going well: -all pages based on EAClass displayed Lib Value in view mode and in edit mode too (the id value is stored in the page)... Except for search engine: I have some problems: - "search page" searching only Id value and not lib value (of course because it is the id value that is stored in EAClass object) i.e. I found pages, if I search "25_dgec" but not if I search "DGEC" - Result "search page" displayed property name (and not the pretty name) FAQ have same issue. - my solr facet displayed my id value too. Do you know how can I fix this issue (if someone understand my problem ;-) )? Here I paste a nice screenchot: http://snag.gy/Joa7q.jpg Thanks. Pascal B

10 years, 1 month

[xwiki-users] Fw : livetable with multiple class?

by Pascal BASTIEN

--- En date de : Ven 27.3.15, Pascal BASTIEN <pbasnews-xwiki(a)yahoo.fr> a écrit : > De: Pascal BASTIEN <pbasnews-xwiki(a)yahoo.fr> > Objet: [xwiki-users] livetable with multiple class? > À: "XWiki Users" <users(a)xwiki.org> > Date: Vendredi 27 mars 2015, 14h19 > If I understand documentation, to use > Livetable with multiple Class (with 3 or 4 common > properties: same name) I must use > Parameter $options: > resultPage The full name of the page to > use as a JSON data provider for the table. This option > allows to use a different data source than the default one > (XWiki.LiveTableResults) for specific needs not handled by > LiveTableResults (for example: complex cross-classes > queries, external data retrieved with a groovy script, > etc.). > ... > Can I do it with query in one (or two) shots or I must use a > foreach loop to rendering my JSON data? I found my query, something like this: #set($hql = "select obj.name, prop.value from BaseObject obj, StringProperty prop where ( obj.className='FormSMQ.EAClass' or obj.className='FormSMQ.PiacJ2Class' ) and prop.id.id=obj.id and prop.name='TypeFiche_RO'") Now I need the JSON format of my JSON data provider (resultPage parameter: full name of the page to use as a JSON data provider for the table)

10 years, 1 month

[xwiki-users] Fw : Re: A way to add some tags on saved page with class

by Pascal BASTIEN

> > > > A the > moment, I'm looking for another way, I read http://extensions.xwiki.org/xwiki/bin/view/Extension/WikiComponent+Module > > But documentation indicate: "The goal > is to listen ... DocumentUpdatingEvent events (note that > these events are fired before the page is saved and thus our > code doesn't need to perform the save itself > ..." > > > Then I can > not use this method either because I must add tag from new > value from my _Tag properties. > > It doesn't say the document doesn't > have the changes. But that the > event is > fired before the changes are saved. So if you listen to > this > event you should be able to get the new > property value and add the > tag. Just > don't call save() in the event handled because this is > done > automatically after the event is passed > to all handlers (including > yours). Ok thxs. Then I must try this method, I must found the way to execute my velocity script to add/remove some tags (all is ready, I need to pass this parameter on my velocity code: $request.PageSourceTo applyMyTag (and eventually) $!request.MyClassAttachedOnMyPage but I'm affraid than there will be some conflict (or loop) because my velocity script use $xwiki.tag.addTagToDocument(String tag, String documentName) : this method save document... Why I don't use full groovy script? Because I know API xwiki with velocity only (it is simple and groovy doc missing)

10 years, 1 month

Re: [xwiki-users] Advice on upgrade and testing

by Mahomed Hussein

I admit I didn't initially understand the WAR + UI upgrade relation. But now that it has been explained, I promise to upgrade both when I do my testing and production upgrades :) Kind regards, Mahomed -----Original Message----- From: users [mailto:users-bounces@xwiki.org] On Behalf Of vincent(a)massol.net Sent: 03 April 2015 12:39 To: Marius Dumitru Florea; XWiki Users Subject: Re: [xwiki-users] Advice on upgrade and testing Indeed not upgrading WAR + UI makes sense. Upgrading only WAR without the UI doesn’t. We agree :) Thanks -Vincent On 3 Apr 2015 at 13:37:48, Marius Dumitru Florea (mariusdumitru.florea(a)xwiki.com) wrote: On Fri, Apr 3, 2015 at 2:05 PM, vincent(a)massol.net <vincent(a)massol.net> wrote: > Hi Mahomed, > > 2 things: > > 1) if you pressed “later” XWiki will not ask you again until it’s restarted > 2) if you don’t upgrade now you are going to risk having stuff in your wiki that don’t work so it’s important you upgrade ASAP. Having a reminder at each XWiki restart is a good thing and bypassing that is not such a brilliant idea IMO :) My comment was about blocking the WAR upgrades not the UI upgrades (through the DW). When you install XWiki through APT you may get unwanted WAR uppdates because: * the system is configured to update automatically * the list of system updates is large and you don't notice that XWiki is included in the list Thanks, Marius > > Thanks > -Vincent > > On 3 Apr 2015 at 13:01:10, Mahomed Hussein (mahomed@custodiandc.com(mailto:mahomed@custodiandc.com)) wrote: >> Hi >> >> This is brilliant and just what I needed. Thank you very much! >> >> >> Kind regards, >> >> Mahomed >> >> >> >> >> -----Original Message----- >> From: users [mailto:users-bounces@xwiki.org] On Behalf Of Marius Dumitru Florea >> Sent: 03 April 2015 11:37 >> To: XWiki Users >> Subject: Re: [xwiki-users] Advice on upgrade and testing >> >> On Wed, Apr 1, 2015 at 12:50 PM, Thomas Mortagne >> wrote: >> > On Wed, Apr 1, 2015 at 11:35 AM, Mahomed Hussein >> > wrote: >> >> Hi >> >> >> >> I wonder if anyone could be kind enough to provide me with some advice and pointers. I’ve noticed that XWiki runs its distribution upgrade wizard automatically when a new version is detected, but even though I pressed “Later” it still went ahead and upgraded. Or at least it appeared to have upgraded part of the system as the core version at the bottom showed 6.4.3 when the extensions etc. were still for 6.4.2. We started with 6.4.2 (installed using apt-get on Ubuntu 14.04). So, to summarise my questions: >> >> >> >> >> >> · How do I stop Xwiki from automatically upgrading. I just want it to notify me then I can plan the upgrade >> > >> > You are mixing two different things. The upgrade wizard is only about >> > part of XWiki (the standard wiki pages) and it's been triggered >> > because you upgraded the WAR probably using apt-get upgrade. If you >> > don't want XWiki to be upgraded by apt-get you need to look at apt-get >> > configuration. >> >> > As far as I know you can indicate a list of packages to >> > not be taken into account automatically by apt-get upgrade. >> >> I successfully 'blocked' upgrades for XWiki by creating the file >> >> /etc/apt/preferences.d/xwiki >> >> with this content: >> >> Package: xwiki-* >> Pin: version 6.2.7 >> Pin-Priority: 1001 >> >> See https://help.ubuntu.com/community/PinningHowto >> >> Hope this helps, >> Marius >> >> > >> >> >> >> · How do you perform a controlled upgrade and test (I appreciate that this is a rather in-depth question)? What I need to be able to do is to do an upgrade and then be able to fairly easily test that the new version doesn’t break any of our documents or functionality that we depend on. Would the only way to do this be to keep a list of my changes and check them with every upgrade? >> > >> > The safest for this is usually to have a test server which is a clone >> > of the production server on which you do the upgrade and test it >> > before doing it on the production server. >> > >> >> >> >> Thanks in advance for your time and help. >> >> >> >> >> >> Kind regards, >> >> >> >> >> >> >> >> >> >> Mahomed Hussein >> >> Senior NOC Engineer >> >> >> >> P.S. We are finalists for Data Centre Colocation Supplier of the year, please help us to win and VOTE for us here >> >> >> >> Tel: +44 (0)1622 230382 >> >> >> >> | Email: Mahomed(a)CustodianDC.com > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

10 years, 1 month

Re: [xwiki-users] Advice on upgrade and testing

by Mahomed Hussein

Hi This is brilliant and just what I needed. Thank you very much! Kind regards, Mahomed -----Original Message----- From: users [mailto:users-bounces@xwiki.org] On Behalf Of Marius Dumitru Florea Sent: 03 April 2015 11:37 To: XWiki Users Subject: Re: [xwiki-users] Advice on upgrade and testing On Wed, Apr 1, 2015 at 12:50 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > On Wed, Apr 1, 2015 at 11:35 AM, Mahomed Hussein > <Mahomed(a)custodiandc.com> wrote: >> Hi >> >> I wonder if anyone could be kind enough to provide me with some advice and pointers. I’ve noticed that XWiki runs its distribution upgrade wizard automatically when a new version is detected, but even though I pressed “Later” it still went ahead and upgraded. Or at least it appeared to have upgraded part of the system as the core version at the bottom showed 6.4.3 when the extensions etc. were still for 6.4.2. We started with 6.4.2 (installed using apt-get on Ubuntu 14.04). So, to summarise my questions: >> >> >> · How do I stop Xwiki from automatically upgrading. I just want it to notify me then I can plan the upgrade > > You are mixing two different things. The upgrade wizard is only about > part of XWiki (the standard wiki pages) and it's been triggered > because you upgraded the WAR probably using apt-get upgrade. If you > don't want XWiki to be upgraded by apt-get you need to look at apt-get > configuration. > As far as I know you can indicate a list of packages to > not be taken into account automatically by apt-get upgrade. I successfully 'blocked' upgrades for XWiki by creating the file /etc/apt/preferences.d/xwiki with this content: Package: xwiki-* Pin: version 6.2.7 Pin-Priority: 1001 See https://help.ubuntu.com/community/PinningHowto Hope this helps, Marius > >> >> · How do you perform a controlled upgrade and test (I appreciate that this is a rather in-depth question)? What I need to be able to do is to do an upgrade and then be able to fairly easily test that the new version doesn’t break any of our documents or functionality that we depend on. Would the only way to do this be to keep a list of my changes and check them with every upgrade? > > The safest for this is usually to have a test server which is a clone > of the production server on which you do the upgrade and test it > before doing it on the production server. > >> >> Thanks in advance for your time and help. >> >> >> Kind regards, >> >> >> >> >> Mahomed Hussein >> Senior NOC Engineer >> >> P.S. We are finalists for Data Centre Colocation Supplier of the year, please help us to win and VOTE<http://www.dcsawards.com/voting.php> for us here<http://www.dcsawards.com/voting.php> >> >> Tel: +44 (0)1622 230382 >> >> | Email: Mahomed(a)CustodianDC.com >> >> >> | Web: www.CustodianDC.com<http://www.CustodianDC.com> >> >> >> | Info: info.CustodianDC.com<http://info.CustodianDC.com> >> >> >> [Custodian Data Centres]<http://www.CustodianDC.com> >> [ISO 27001 IS:567248] >> >> Click to VOTE<http://www.dcsawards.com/voting.php> for Custodian! [DCS Awards Finalist] >> >> >> [Like us on Facebook!][Follow us on Twitter][See us on YouTube!] >> [Link to us!][Google Plus!] >> >> >> Click here to view our email disclaimer<http://www.custodiandc.com/disclaimer.txt> >> Registered Office: Maidstone TV Studios, Vinters Park, Maidstone, Kent ME14 5NZ. Company Number: 07878023 >> >> >> >> >> _______________________________________________ >> users mailing list >> users(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/users > > > > -- > Thomas Mortagne > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list users(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/users

10 years, 1 month

[xwiki-users] Advice on upgrade and testing

by Mahomed Hussein

Hi I wonder if anyone could be kind enough to provide me with some advice and pointers. I’ve noticed that XWiki runs its distribution upgrade wizard automatically when a new version is detected, but even though I pressed “Later” it still went ahead and upgraded. Or at least it appeared to have upgraded part of the system as the core version at the bottom showed 6.4.3 when the extensions etc. were still for 6.4.2. We started with 6.4.2 (installed using apt-get on Ubuntu 14.04). So, to summarise my questions: · How do I stop Xwiki from automatically upgrading. I just want it to notify me then I can plan the upgrade · How do you perform a controlled upgrade and test (I appreciate that this is a rather in-depth question)? What I need to be able to do is to do an upgrade and then be able to fairly easily test that the new version doesn’t break any of our documents or functionality that we depend on. Would the only way to do this be to keep a list of my changes and check them with every upgrade? Thanks in advance for your time and help. Kind regards, Mahomed Hussein Senior NOC Engineer P.S. We are finalists for Data Centre Colocation Supplier of the year, please help us to win and VOTE<http://www.dcsawards.com/voting.php> for us here<http://www.dcsawards.com/voting.php> Tel: +44 (0)1622 230382 | Email: Mahomed(a)CustodianDC.com | Web: www.CustodianDC.com<http://www.CustodianDC.com> | Info: info.CustodianDC.com<http://info.CustodianDC.com> [Custodian Data Centres]<http://www.CustodianDC.com> [ISO 27001 IS:567248] Click to VOTE<http://www.dcsawards.com/voting.php> for Custodian! [DCS Awards Finalist] [Like us on Facebook!][Follow us on Twitter][See us on YouTube!] [Link to us!][Google Plus!] Click here to view our email disclaimer<http://www.custodiandc.com/disclaimer.txt> Registered Office: Maidstone TV Studios, Vinters Park, Maidstone, Kent ME14 5NZ. Company Number: 07878023

10 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-users April 2015