Hello all,
I would like to ask for your opinion regarding the documentation for the
new skin we’re working on. Would you rather prefer:
a) The documentation to be conducted in parallel with the current version
(6.1 for the Colibri skin as well as for the Flamingo skin)?
b) Or would you prefer to begin the documentation for the Flamingo skin
with version 6.2, which would imply cancelling the maintenance for the
Colibri skin?
Please express your view in a reply to this email.
Thank you,
Andreea
Hello all,
I've created an "App Within Minutes" application we are using for some reporting and issue tracking which is pretty much done now, but I need a way to create a page in the application with an API call. I've seen tons of information on creating pages or modifying pages and I can get that to work pretty well, but when I create a page in the application space I don't know how to make the controls appear and the page doesn't show up I'm the application home page (grid).
I'm sure I'm approaching this the wrong way as I'm creating a page from scratch where I'm pretty sure I should be creating an instance of the page class, but I'm not sure where to start with that.
Does anyone have any links or tips or leads on where I would start looking for something like that?
All help is greatly appreciated,
Thanks in advance
Hello,
I need some help with my velocity script.
I try to remove history of pages on a space.
This code work well for a page:
{{velocity}}
$xwiki.getDocument('BacASable.TestPage3').getDocument().resetArchive($context.context)
{{/velocity}}
but my script fail when I launch this one to remove history of all BacASable space Page
{{velocity}}
#foreach ($docName in $xwiki.getSpaceDocsName("BacASable"))
$xwiki.getDocument("BacASable.$docName").getDocument().resetArchive($context.context)
* history of "BacASable.$docName" removed
#end
{{/velocity}}
I obtain this error:
Caused by: org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [com.xpn.xwiki.doc.rcs.XWikiRCSNodeInfo#com.xpn.xwiki.doc.rcs.XWikiRCSNodeId(a)2ff3ff58[docId=9026427162423984573,version=4.1]]
Any ideas what's I'm doing wrong? Thxs
Note: deletion of WebHome history doessn't work:
$xwiki.getDocument('BacASable.WebHome').getDocument().resetArchive($context.context)
Pascal B (on Xwiki 6.0)
Hi Leonardo,
On 15 Jul 2014 at 20:10:26, Leonardo Kodato (leonardokodato@gmail.com(mailto:leonardokodato@gmail.com)) wrote:
> Hi Marius and Vicent.
> Thank you for the reply.
>
> After disabling the JS, it loaded correctly.
> Then I rolled back the instalation and restored the last change I've made. The problem ocurred due to a jquery-prototype compatibility.
> I tried to put Jquery in no-conflict mode, as documented in jquery.com(http://jquery.com). It was inside a Xwiki object, as well as the Jquery plugin that I'm using. Now I will try to figure out how do I get it to work without conflict with prototype.
>
> Vicent, here is the documentation I read. It says that:
> "The general strategy is to download the WAR distribution and to replace your current installed WAR. Make sure you don't copy on top since this could leave some old files around which would make XWiki fail (like if old JARs are lying around in WEB-INF/lib). "
> Link: http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade
Actually I thought you mean the xwiki data directory and this directory must absolutely not be removed. It needs to be kept so that the upgrade can happen. BTW where did you put the xwiki data directory (it’s configured in xwiki.properties)?
> Even so, I will try to update it to 6.1 and test it, as it features a new bootstrap skin.
Cool, let us know how it goes!
Thanks
-Vincent
> Thank you for your support.
> =).
>
>
> 2014-07-12 10:26 GMT-03:00 vincent@massol.net(mailto:vincent@massol.net) :
> > Hi,
> >
> > On 8 Jul 2014 at 20:12:22, Leonardo Kodato (leonardokodato@gmail.com(mailto:leonardokodato@gmail.com)(mailto:leonardokodato@gmail.com)) wrote:
> >
> > > UPDATE:
> > >
> > > I tried to update Xwiki to the last super stable version, but the problem
> > > persists. It loads the new version and tries to display the Distribution
> > > Wizard to start the upgrade proccess, but then the gray background shows up
> > > and there is nothing I can do.
> > >
> > > One thing to note is that some users can see their spaces, but the Admin
> > > and the others can not. The guest visitor also can see the register and
> > > logon page. So, I suspect that is something related to just one space.
> > >
> > > Another thing I've noticed is that I've deleted the xwiki folder to start
> > > the update proccess as recommended in the documentation.
> >
> > Could you show me where this is mentioned in the documentation? I’d like to make sure you’re doing it correctly.
> >
> > Thanks
> > -Vincent
> >
> > > So, It's not a
> > > extension problem or a file problem, I think. It seems to be something with
> > > the Database and javascript.
> > >
> > > Should I start a bug report on Jira?
> > >
> > > Thank you very much.
>
Hi.
Is there a document describing prefetred settings to have xwiki and solr-based
search working well for non-multilingual, non-en documents?
I have a problem with solr search (xwiki 5.3). My language settings are:
multilingual: no
supported languages: pl,en
default language: - I'm testing with different values here
and in xwiki.cfg:
xwiki.language.preferDefault=1
xwiki.language.forceSupported=1
Test no 1:
default language: pl
When I create new document, it has (in database) xwd_language = '' and
xwd_default_language = 'pl' - so it looks ok:
xwd_fullname | xwd_language | xwd_default_language
---------------------------------+--------------+----------------------
Sandbox.SzukajWNazwieStronyTest | | pl
I try to search on 'SzukajWNazwie' - solr suggest does suggest this page, but
entering search result the result list is empty.
If i try searching by document content - both search suggest and search result
list are empty.
When I change
default language: en
and create a document, it has properties:
xwd_fullname | xwd_language | xwd_default_language
------------------------------+--------------+----------------------
Sandbox.SearchInPageNameTest | | en
Then:
1. Suggest does find the document by its name, search does too
2. Suggest does not find the document by its content, but search does.
Searching of polish document works as before the change
I'm a little bit confused, I cannot see any consistent rule in the behavior.
Thanks in advance for any tips.
Best Regards,
R.
Hello Community,
I am trying to add a column that reference the doc parent but I am facing
some difficult.
I have tried to input the doc.space but It not worked:
{{velocity}}
{{box}}
#set ($discard = $services.localization.use('document',
'FileManager.FileManagerTranslations'))
#set ($columnsProperties = {
'doc.space': {"type":"list"},
'category': {"type":"text","size":10,"link":"view"},
'doc.name': {"type":"text","size":10,"link":"view"},
'_attachments': {"sortable":false,"filterable":false,"html":true},
'_actions':
{"sortable":false,"filterable":false,"html":true,"actions":["edit","delete"]
}
})
#set ($options = {
'className': 'FileManager.FileManagerClass',
'resultPage': 'FileManager.FileManagerLiveTableResults',
'translationPrefix': 'filemanager.livetable.',
'tagCloud': true,
'rowCount': 15,
'maxPages': 10,
'selectedColumn': 'category',
'defaultOrder': 'asc'
})
## Add the filter by selected tags
#if($request.tag)
#set ($discard = $options.put('selectedTags',["${request.tag}"]))
#end
##
#set ($columns = ['doc.space','category','doc.name', '_attachments',
'_actions'])
#livetable('filemanager' $columns $columnsProperties $options)
{{/box}}
{{/velocity}}
Any tip?
thanks
Grupo Energisa
Danilo Oliveira
Analista Suporte Aplicacao TI - DPTO CORP. DE INFRAESTR. TI
e-mail: danilo.oliveira(a)energisa.com.br | tel: (32) 3429-6342 | cel: (32) 8452-9478
Esta mensagem contém informação confidencial. Se você a recebeu por engano, não divulgue ou copie seu conteúdo. Por favor, avise ao remetente imediatamente e apague-a do computador.
Privileged and confidential. If this message has been received by mistake, do not disclose or copy its contents. Please notify sender and delete immediately.
Hello all,
After migration 3.4 > 6.1, i got just a small bug, in the menu "Home" , the < wiki index > label doesn't appear but I got "platform.wiki.menu.wikiindex"
In the wiki index module, same, all label are "plateform.wiki.browse", "plateform.wiki.browse.wikiprettyname, " plateform.wiki.browse.decription",....
Do you know how I can correct this?
BR
Patrick