Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: 3.4-milestone-1, 3.3.1
-
Component/s: Web - Templates & Resources
-
Labels:None
-
keywords:livetable
-
Difficulty:Trivial
-
Similar issues:
XWIKI-3987Livetable macro isn't working anymore in XWiki 2.0 syntax XWIKI-8115livetable macro bad javascript row variable usage after livetable results api changes XWIKI-9036msg binding does not exist anymore in groovy macro or any other script other than velocity XWIKI-7543Livetable does not work when page name of current page contains a dot and it is trying to retreive all pages that have current page set as parent XWIKI-3742Converter does not support comma as velocity macro parameters separator XWIKI-1086Add new pagedViewLinks macro XWIKI-7145Livetable does not support column names with special characters and/or Unicode characters XWIKI-3706Provide a velocity macro to automate the creation of live tables XWIKI-3979Callbacks from macros.vm to local page macro is not possible anymore XWIKI-5015 LiveTable doesn't correctly support columns from other classes
Description
In 3.3 the first parameter of a livetable macro. For example:
#livetable("platform.vms" $collist $colprops $options)
{/code}
Is not supported anymore. Removing the dot works. This worked in XE 2.7 without any problems
#livetable("platformvms" $collist $colprops $options)
{/code}There is no meaningfull error message saying that this was the problem. I think this is used for css so is probably not validating. However we should either warn or transform it.
Fixed in 6835891
The problem was that the livetable ID (the first parameter) was also used to form the name of the JS variable holding the livetable JS object. I didn't transform anything, I just used a safe window["$jsName"] way to access the variable.