Hello!
I'm having difficulties setting up a tree for my wiki. I'm using
DocumntTree. The tree starts off with the only space (Revit Mechanical) and
not open node to show the pages. I believe I have syntax errors but can't
quite fix it
Code:
{{documentTree showWikis="true" showSpaces="true" showTranslations="false"
showAttachments="false" showChildDocuments="true"
root="space:xwiki:Revit Mechanical" openTo="space:xwiki:Revit Mechanical"/}}
Here is a screenshot of how it opens up:
<http://xwiki.475771.n2.nabble.com/file/n7594472/DocumentTree.png>
Here is how I want it to open up:
<http://xwiki.475771.n2.nabble.com/file/n7594472/TreeCorrect.png>
Sorry for asking so many questions, I'm not good at this.
Regards,
Michael
--
View this message in context: http://xwiki.475771.n2.nabble.com/DocumentTree-doesn-t-open-to-a-node-tp759…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello!
I'm using xwiki 6.3 version and I can't update it. I created a panel display
tree (using documentTree) on the left of my wiki pages to display the
content with opening/closing branches and links to the pages on click.
However the order of the tree is messed up because it uses some kind of
sorting. I would like to change the order to my liking.
Some things that I already did:
-I've tried using File Manager and few other extensions but it doesn't
display anything or doesn't have some dependencies. I'm guessing it is
because of the old version I have.
-Also tried Hierarchy Macro with editing option but it seems to not move
anything.
-Lastly I've tried to edit some of the macros, ended up screwing all of the
macros and had to restore the wiki with backup.
I'm guessing there is a way to hard code all of this but that's the last
option I want to take because every time a new page is added I would have to
edit the tree.
Regards,
Michael
--
View this message in context: http://xwiki.475771.n2.nabble.com/Editing-pages-and-index-view-tp7594388.ht…
Sent from the XWiki- Users mailing list archive at Nabble.com.
The XWiki development team is proud to announce the availability of XWiki
7.0.
This is the first release of the 7.x cycle. It features many improvements
for extensions, a simplified Wiki Creation Wizard, improved differences
view, integration of a new Tree Widget with the WYSIWYG editor and Index
Application, etc.
Regarding extensions, we now have the ability to organize and filter
extensions by category in the Extension Repository, the install date and
the user that performed the install are now available in the extension
details, the extensions that were installed explicitly are now displayed
distinctly, etc.
We improved the difference views for document history and extension upgrade
process, by showing a difference summary between the two versions, detailed
changes to objects definitions, etc.
Developers may enjoy a new application to edit wiki Skins, a new Finder
Plugin for the Tree Widget and API improvements to the Mail Sender and
Extension Manager modules.
The Watchlist module has a new component based implementation and also
there is an experimental Realtime Watchlist Notification feature.
XWiki also moved to Servlet 3.0.1 which means various old application
servers versions are not supported anymore and the old Lucene search module
was finally retired to Contrib.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki70
Thanks
-The XWiki dev team
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.).
with an HQL query like this one (for 2 class: FormSMQ.EAClass and FormSMQ.PiacJ2Class ):
#set($hqlstatement=", BaseObject as obj where (doc.fullName = obj.name and obj.className = 'FormSMQ.EAClass') or (doc.fullName = obj.name and obj.className = 'FormSMQ.PiacJ2Class')")
$services.query.hql($hqlstatement).execute()
(http://extensions.xwiki.org/xwiki/bin/view/Extension/Query+Module)
My query list all documents with my 2 Class. To provide JSON source of LiveTable, I must displayed all my column.
Can I do it with query in one (or two) shots or I must use a foreach loop to rendering my JSON data?
Thxs
--------------------------------------------
En date de : Mer 25.2.15, Pascal BASTIEN <pbasnews-xwiki(a)yahoo.fr> a écrit :
Objet: [xwiki-users] livetable with multiple class?
À: "XWiki Users" <users(a)xwiki.org>
Date: Mercredi 25 février 2015, 16h20
Hello,
Livetable is somehow magic but ... (there are always a
'but') is it possible to use multiple Class?
I read XWiki.LiveTableResultsMacros
"#macro(gridresultwithfilter_buildQuery $className ...
#set($class =
$xwiki.getDocument($className).getxWikiClass())"
=> livetable use getxWikiClass method (and not
getxWikiClasses :-( )
Here my problem in my nice xwiki 6.4.0 application:
I created some Class/Sheet/Template with 2 common
properties/field: I mean on each document Class I created
this common property (same name, same source): this one by
example
- Name:P1_DgMoa_req Type: Database List
- XWiki Class Name: FormSMQ.ListeDGClass
- Id Field: Name DGId
- Value Field: Name DGLib
On my WebHome I paste this livetable:
#set ($columnsProperties = {
'TypeFiche_RO': {"type":"list","size":10},
'P1_DgMoa_req': {"type":"list","size":10},
'doc.name': {"type":"text","size":10,"link":"view"},
'doc.date': {"type":"text","size":10},
'doc.creator':
{"type":"text","size":10,"link":"creator"},
'_actions':
{"sortable":false,"filterable":false,"html":true,"actions":["edit"]}
})
#set ($options = {
'className': 'MySpace.MyClass',
'translationPrefix' : 'FormSMQ.livetable.',
'tagCloud': true,
'rowCount': 15,
'maxPages': 10,
'selectedColumn': 'doc.name',
'defaultOrder': 'asc',
'extraParams': "&space=${doc.space}"
})
With one class ( 'className': 'MySpace.MyClass',) my
livetable work perfectly but display only documents 'linked'
with this class (doc with 'MySpace.MyClass' object)
If I use 'className': '' (empty), livetable show all
document on the space but my select list are not filled.
I tried 'TypeFiche_RO':
{"type":"list","size":10,'class': 'MySpace.MyClass' } with
empty 'classname', but if I select a value in my select
list, only document 'linked' with this class are
displayed.
I tried topFilters options (HTML fragment
that will be placed in a "top filter" area in the same
fashion as the Tag Cloud filter) 'topFilters': '<input
type="text" size="15" name="doc.name" value="">', but no
document will displayed. I didn't managed either (I don't
know how to choose the field who is filtered by the new
input tag)
I don't know if someone understand my problem ( livetable
with multiple class source), but every magics tricks are
welcome to help me.
Thxs.
Pascal B
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
I have just upgraded our xWiki from 6.4.2 to 6.4.3 and noticed a change in
how group rights are handled. We have a main wiki with 6 subwikis. All
users are members of the main wiki. In order to allow users rights to a
subwiki, we add them into a group in the main wiki and then give that group
access on the subwiki. This worked great in 6.4.2, however with the upgrade
to 6.4.3, we get the following error when a user logs into a subwiki, even
though the user is in a group that has access to the subwiki.
(I have truncated the error message since it is long, but if you need more
of it I can include it)
Failed to execute the [include] macro. Click on this message for details.
org.xwiki.rendering.macro.MacroExecutionException: Current user
[xwiki:XWiki.TestUser] doesn't have view rights on document
[test:WikiManager.Dashboard]
at
org.xwiki.rendering.internal.macro.include.IncludeMacro.execute(IncludeMacro
.java:151)
at
org.xwiki.rendering.internal.macro.include.IncludeMacro.execute(IncludeMacro
.java:55)
at
org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transf
orm(MacroTransformation.java:252)
at
org.xwiki.rendering.internal.transformation.DefaultRenderingContext.transfor
mInContext(DefaultRenderingContext.java:183)
at
org.xwiki.rendering.internal.transformation.DefaultTransformationManager.per
formTransformations(DefaultTransformationManager.java:94)
at
org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentD
isplayer.java:252)
at
org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentD
isplayer.java:125)
at
org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentD
isplayer.java:55)
at
org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentD
isplayer.java:96)
at
org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentD
isplayer.java:39)
at
org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplay
er.java:113).
Attempting to access a page within the subwiki gives this error:
Error
You are not allowed to view this document or perform this action.
Is the use of groups to give access to subwikis no longer allowed, or is
this an issue with 6.4.3? In our test environment, I took our 6.4.3 XWiki
and switched back to the 6.4.2 deployment and things worked as expected,
however that really isn't an option as all of the extensions have been
upgraded to 6.4.3.
If this isn't an issue with 6.4.3, then what is the best way to handle
delegating rights for users in our setup?
Thanks!
Charlie
---------- Forwarded message ----------
From: Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com>
Date: Wed, Mar 25, 2015 at 10:49 AM
Subject: Re: Fw : [xwiki-users] Fw : Re: ajax example
To: Pascal BASTIEN <pbasnews-xwiki(a)yahoo.fr>
On Tue, Mar 24, 2015 at 7:34 PM, Pascal BASTIEN <pbasnews-xwiki(a)yahoo.fr> wrote:
>
>> > For step 1: Don't print
>> > the JSON directly. You'll have escaping
>> > issues. In order to ensure the generated JSON
>> > is valid you should
>> > build the JSON in memory
>> > (using Velocity/Java maps, arrays and basic
>> > types) and then serialize it:
>> >
>> > $jsontool.serialize({
>> > "greeting": "Hello",
>> > "location": "World"
>> > })
>>
>> I agree but one* purpose was to use Vincent example on
>> this page: http://extensions.xwiki.org/xwiki/bin/view/Extension/Output+JSON
>> Perhaps we (who?) need to modify both pages?
>
> Anyway, do you prefer this code?
>
> {{velocity wiki="false"}}
> ## If AJAX call
> #if("$!request.outputSyntax" != '')
> $response.setContentType('application/json')
> #end
> #set($MyJsonData = {'greeting': 'Hello', 'location': 'World'})
> $jsontool.serialize($MyJsonData)
>
> {{/velocity}}
Definitely.
Thanks,
Marius
>
>
>>
>>
>> >
>> > For step 4:
>> > Don't hard-code the page URL and use the 'get'
>> > action
>> > instead of 'view' to avoid
>> > adding view statistics entries.
>> >
>> > var url = new
>> > XWiki.Document('JsonHello',
>> > 'Sandbox').getURL('get');
>>
>> Thxs I was too lazy to take too long time to find JS
>> function. :-)
>>
>> >
>> > Also, to avoid the need to
>> > URL-encode the request parameters you
>> > should
>> > pass them using an object not a string.
>> >
>> > var params = {
>> >
>> > 'xpage': 'plain',
>> >
>> > 'outputSyntax': 'plain'
>> > };
>> > $.get(url, params,
>> > function(data) {
>> > ...
>> > });
>>
>> Yes thxs you
>> => I uploaded/update my page
>>
>> (The worst is that I hate JS) :-)
>>
>>
>>
>> Pascal B
>>
>> >
>> > Hope this
>> > helps,
>> > Marius
>> >
>> >
>> > On Fri, Mar 20, 2015 at 8:26 PM, Pascal BASTIEN
>> > <pbasnews-xwiki(a)yahoo.fr>
>> > wrote:
>> > > Hello,
>> > >
>> > > Here, I provided an simple Ajax example to
>> > use in xwiki application:
>> > > http://extensions.xwiki.org/xwiki/bin/view/Extension/AJAX+example#Attachmen…
>> > > This mail on this list to validate that
>> > what I wrote is the best way (like suggest Vincent)
>> > >
>> > > Thxs.
>> > >
>> > > Pascal
>> > BASTIEN
>> > >
>> > >
>> > _______________________________________________
>> > > 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
> > Do you mean $xwiki.activitystream. API is
> broken?
>
> I don't
> remember talking about the activity stream API :) I
probably because you didn't talk about it :-))
> don't
> really know it well enough to give
> advices on it.
Finally, I used another method who's working like I want:
{{velocity}}
#set ($MonStream=$xwiki.activitystream.getStreamName("Sandbox"))
##foreach ($MonEvent in $xwiki.activitystream.getEventsForUser("XWiki.Admin", false, 1500, 0))
#foreach ($MonEvent in $xwiki.activitystream.getEvents($MonStream, false, 1500, 0))
1. $MonEvent.getPage() - $MonEvent.getDisplayDate() - $MonEvent.getDate() - $MonEvent.getType() - $MonEvent.getPriority()
#if ($MonEvent.getPage() == "Sandbox.test3")
* Je supprime l'event
$xwiki.activitystream.deleteActivityEvent($MonEvent)
#end
#end
{{/velocity}}
Like I chatted with Vincent I know groovy is powerfull (except the fact that "With great power comes great responsibility" ;-) ), full example application in groovy missing (because required PR) and templates contains tons of nice velocity code. :-)
Thxs for your help / works :-)
> > For step 1: Don't print
> > the JSON directly. You'll have escaping
> > issues. In order to ensure the generated JSON
> > is valid you should
> > build the JSON in memory
> > (using Velocity/Java maps, arrays and basic
> > types) and then serialize it:
> >
> > $jsontool.serialize({
> > "greeting": "Hello",
> > "location": "World"
> > })
>
> I agree but one* purpose was to use Vincent example on
> this page: http://extensions.xwiki.org/xwiki/bin/view/Extension/Output+JSON
> Perhaps we (who?) need to modify both pages?
Anyway, do you prefer this code?
{{velocity wiki="false"}}
## If AJAX call
#if("$!request.outputSyntax" != '')
$response.setContentType('application/json')
#end
#set($MyJsonData = {'greeting': 'Hello', 'location': 'World'})
$jsontool.serialize($MyJsonData)
{{/velocity}}
>
>
> >
> > For step 4:
> > Don't hard-code the page URL and use the 'get'
> > action
> > instead of 'view' to avoid
> > adding view statistics entries.
> >
> > var url = new
> > XWiki.Document('JsonHello',
> > 'Sandbox').getURL('get');
>
> Thxs I was too lazy to take too long time to find JS
> function. :-)
>
> >
> > Also, to avoid the need to
> > URL-encode the request parameters you
> > should
> > pass them using an object not a string.
> >
> > var params = {
> >
> > 'xpage': 'plain',
> >
> > 'outputSyntax': 'plain'
> > };
> > $.get(url, params,
> > function(data) {
> > ...
> > });
>
> Yes thxs you
> => I uploaded/update my page
>
> (The worst is that I hate JS) :-)
>
>
>
> Pascal B
>
> >
> > Hope this
> > helps,
> > Marius
> >
> >
> > On Fri, Mar 20, 2015 at 8:26 PM, Pascal BASTIEN
> > <pbasnews-xwiki(a)yahoo.fr>
> > wrote:
> > > Hello,
> > >
> > > Here, I provided an simple Ajax example to
> > use in xwiki application:
> > > http://extensions.xwiki.org/xwiki/bin/view/Extension/AJAX+example#Attachmen…
> > > This mail on this list to validate that
> > what I wrote is the best way (like suggest Vincent)
> > >
> > > Thxs.
> > >
> > > Pascal
> > BASTIEN
> > >
> > >
> > _______________________________________________
> > > 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
> Some comments:
Thxs
>
> For step 1: Don't print
> the JSON directly. You'll have escaping
> issues. In order to ensure the generated JSON
> is valid you should
> build the JSON in memory
> (using Velocity/Java maps, arrays and basic
> types) and then serialize it:
>
> $jsontool.serialize({
> "greeting": "Hello",
> "location": "World"
> })
I agree but the purpose was to use Vincent example on this page: http://extensions.xwiki.org/xwiki/bin/view/Extension/Output+JSON
Perhaps we (who?) need to modify both pages?
>
> For step 4:
> Don't hard-code the page URL and use the 'get'
> action
> instead of 'view' to avoid
> adding view statistics entries.
>
> var url = new
> XWiki.Document('JsonHello',
> 'Sandbox').getURL('get');
Thxs I was too lazy to take too long time to find JS function. :-)
>
> Also, to avoid the need to
> URL-encode the request parameters you
> should
> pass them using an object not a string.
>
> var params = {
>
> 'xpage': 'plain',
>
> 'outputSyntax': 'plain'
> };
> $.get(url, params,
> function(data) {
> ...
> });
Yes thxs you
=> I uploaded/update my page
(The worst is that I hate JS) :-)
Pascal B
>
> Hope this
> helps,
> Marius
>
>
> On Fri, Mar 20, 2015 at 8:26 PM, Pascal BASTIEN
> <pbasnews-xwiki(a)yahoo.fr>
> wrote:
> > Hello,
> >
> > Here, I provided an simple Ajax example to
> use in xwiki application:
> > http://extensions.xwiki.org/xwiki/bin/view/Extension/AJAX+example#Attachmen…
> > This mail on this list to validate that
> what I wrote is the best way (like suggest Vincent)
> >
> > Thxs.
> >
> > Pascal
> BASTIEN
> >
> >
> _______________________________________________
> > users mailing list
> > users(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
>
