4 Mar
2010
4 Mar
'10
5:54 p.m.
Hi,
I am using xwiki 2.1.1 and i am having problem with livetable and a simple
custom class.
Here is my code:
#set($collist = ["Customer", "Responsible", "TargetDate",
"Activities",
"priority", "_actions"])
#set($colprops = {
"Customer" : { "type" : "text" , "size" : 20,
"link" : "edit"},
"Responsible" : { "type" : "list" , "class":
"XWiki.XWikiUsers"},
"TargetDate": { "type" : "date"
,"sortable":"true",
"displayName":"Target Date"},
"Activities" : { "type" : "text" },
"priority": {"type": "number" },
"_actions" : {"actions":
["copy","delete","rename","inline"]}
})
#set($options = { "className":"Task.TasksClass",
"rowCount": 15 })
#livetable("alldocs" $collist $colprops $options)
It displays three documents, but as soon as I click on one of the other
columns to sort the table, it gets empty.
For the allDocumentsSnippet it works.
I have no carriage returns or quotes in the fields that are to be displayed.
I tried with different options and also only two fields (customer and
priority): the same happens.
Is this a known bug or did I misunderstand the livetable macro?
Thanks,
Hans-Peter
4 Mar
4 Mar
6:58 p.m.
Hi,
I think it's the same issue I encountered (see my other posts "Still issue
in livetable...").
I did investigate a little, and in my understanding the sort query generated
by XWiki.LiveTableResultsMacros is broken when type of field is not text
(StringProperty).
It seems to me that the macro in this case do not properly retrieve the
field type, and so puts the default, StringProperty. Of course the query
returns no answer, and your livetable is empty.
In my case I corrected it in a very ugly way, for my particular use-case on
Dates properties. I did not find, though, exactly why the macro do not find
the correct type, but I think it might be linked to how the resultsmacros
page is called (with parameters like "TargetDate_class=${propClassName}"),
in this case it would more be a bug in the #livetable macro or in the
javascript.
I wanted to create a JIRA on this but I'd like some feedback from the wiki
team before :)
Jeremie
2010/3/4 Hans-Peter Zorn <hpz(a)gmx.org>
Hi,
I am using xwiki 2.1.1 and i am having problem with livetable and a simple
custom class.
Here is my code:
#set($collist = ["Customer", "Responsible", "TargetDate",
"Activities",
"priority", "_actions"])
#set($colprops = {
"Customer" : { "type" : "text" , "size" : 20,
"link" : "edit"},
"Responsible" : { "type" : "list" , "class":
"XWiki.XWikiUsers"},
"TargetDate": { "type" : "date"
,"sortable":"true",
"displayName":"Target Date"},
"Activities" : { "type" : "text" },
"priority": {"type": "number" },
"_actions" : {"actions":
["copy","delete","rename","inline"]}
})
#set($options = { "className":"Task.TasksClass",
"rowCount": 15 })
#livetable("alldocs" $collist $colprops $options)
It displays three documents, but as soon as I click on one of the other
columns to sort the table, it gets empty.
For the allDocumentsSnippet it works.
I have no carriage returns or quotes in the fields that are to be
displayed.
I tried with different options and also only two fields (customer and
priority): the same happens.
Is this a known bug or did I misunderstand the livetable macro?
Thanks,
Hans-Peter
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
7:29 p.m.
Again,
I eventually created a JIRA on this ...
http://jira.xwiki.org/jira/browse/XWIKI-4973
2010/3/4 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>
Hi,
I think it's the same issue I encountered (see my other posts "Still issue
in livetable...").
I did investigate a little, and in my understanding the sort query
generated by XWiki.LiveTableResultsMacros is broken when type of field is
not text (StringProperty).
It seems to me that the macro in this case do not properly retrieve the
field type, and so puts the default, StringProperty. Of course the query
returns no answer, and your livetable is empty.
In my case I corrected it in a very ugly way, for my particular use-case on
Dates properties. I did not find, though, exactly why the macro do not find
the correct type, but I think it might be linked to how the resultsmacros
page is called (with parameters like "TargetDate_class=${propClassName}"),
in this case it would more be a bug in the #livetable macro or in the
javascript.
I wanted to create a JIRA on this but I'd like some feedback from the wiki
team before :)
Jeremie
2010/3/4 Hans-Peter Zorn <hpz(a)gmx.org>
Hi,
I am using xwiki 2.1.1 and i am having problem
with livetable and a simple
custom class.
Here is my code:
#set($collist = ["Customer", "Responsible", "TargetDate",
"Activities",
"priority", "_actions"])
#set($colprops = {
"Customer" : { "type" : "text" , "size" : 20,
"link" : "edit"},
"Responsible" : { "type" : "list" , "class":
"XWiki.XWikiUsers"},
"TargetDate": { "type" : "date"
,"sortable":"true",
"displayName":"Target Date"},
"Activities" : { "type" : "text" },
"priority": {"type": "number" },
"_actions" : {"actions":
["copy","delete","rename","inline"]}
})
#set($options = { "className":"Task.TasksClass",
"rowCount": 15 })
#livetable("alldocs" $collist $colprops $options)
It displays three documents, but as soon as I click on one of the other
columns to sort the table, it gets empty.
For the allDocumentsSnippet it works.
I have no carriage returns or quotes in the fields that are to be
displayed.
I tried with different options and also only two fields (customer and
priority): the same happens.
Is this a known bug or did I misunderstand the livetable macro?
Thanks,
Hans-Peter
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
7 Mar
7 Mar
8:53 a.m.
Hi,
I think I found it, at least a way to have it work in most cases ...
In the "$columnProperties" parameter of the #livetable macro, you should now
add explicitely a parameter "class":"MyClass" for each column, where
"MyClass" is the name of the class of the objects you want to show (the same
as the parameter "$classNames" in "$options" parameter).
In your case, the following might work :
#set($colprops = {
"Customer" : { "type" : "text" , "size" : 20,
"link" : "edit",
"class":"Task.TasksClass"},
"Responsible" : { "type" : "list" , "class":
"XWiki.XWikiUsers"},
"TargetDate": { "type" : "date"
,"sortable":"true", "displayName":"Target
Date", "class":"Task.TasksClass"},
"Activities" : { "type" : "text",
"class":"Task.TasksClass" },
"priority": {"type": "number",
"class":"Task.TasksClass" },
"_actions" : {"actions":
["copy","delete","rename","inline"]}
})
There seems to be something wrong with how the class is detected for each
column if you don't do this.
I will update the JIRA,
BR,
Jeremie
2010/3/4 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>
Again,
I eventually created a JIRA on this ...
http://jira.xwiki.org/jira/browse/XWIKI-4973
2010/3/4 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>
Hi,
I think it's the same issue I encountered (see my other posts "Still issue
in livetable...").
I did investigate a little, and in my understanding the sort query
generated by XWiki.LiveTableResultsMacros is broken when type of field is
not text (StringProperty).
It seems to me that the macro in this case do not properly retrieve the
field type, and so puts the default, StringProperty. Of course the query
returns no answer, and your livetable is empty.
In my case I corrected it in a very ugly way, for my particular use-case
on Dates properties. I did not find, though, exactly why the macro do not
find the correct type, but I think it might be linked to how the
resultsmacros page is called (with parameters like
"TargetDate_class=${propClassName}"), in this case it would more be a bug in
the #livetable macro or in the javascript.
I wanted to create a JIRA on this but I'd like some feedback from the wiki
team before :)
Jeremie
2010/3/4 Hans-Peter Zorn <hpz(a)gmx.org>
Hi,
I am using xwiki 2.1.1 and i am having problem
with livetable and a
simple
custom class.
Here is my code:
#set($collist = ["Customer", "Responsible", "TargetDate",
"Activities",
"priority", "_actions"])
#set($colprops = {
"Customer" : { "type" : "text" , "size" : 20,
"link" : "edit"},
"Responsible" : { "type" : "list" , "class":
"XWiki.XWikiUsers"},
"TargetDate": { "type" : "date"
,"sortable":"true",
"displayName":"Target Date"},
"Activities" : { "type" : "text" },
"priority": {"type": "number" },
"_actions" : {"actions":
["copy","delete","rename","inline"]}
})
#set($options = { "className":"Task.TasksClass",
"rowCount": 15 })
#livetable("alldocs" $collist $colprops $options)
It displays three documents, but as soon as I click on one of the other
columns to sort the table, it gets empty.
For the allDocumentsSnippet it works.
I have no carriage returns or quotes in the fields that are to be
displayed.
I tried with different options and also only two fields (customer and
priority): the same happens.
Is this a known bug or did I misunderstand the livetable macro?
Thanks,
Hans-Peter
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
5360
days inactive
5363
days old
3 comments
2 participants
participants (2)
-
Hans-Peter Zorn -
Jeremie BOUSQUET