answered
2014-10-21 01:33:55 +0800
cor3000 6280 ● 2 ● 7 first: you could try upgrading to a new ZK 5 version e.g. 5.0.11 (CE) or 5.0.13 (PE/EE) and check if the problem persists, it is likely that severe bugs are fixed in higher versions.
(http://www.zkoss.org/download/zk click maintenance downloads)
second: the stackoverflow link you found gives you some basic ideas how to get started debugging a JS error, most important here is to enable debug-js in your zk.xml:
<client-config>
<debug-js>true</debug-js>
</client-config>
that will turn difficult to identify error locations like (char 11000 in line 23)
Line: 23 Char: 11118
into something like
Line: 5678 Char: 32 (just made up)
e.g. in chrome if you enable the developer tools (F12) before reproducing the error you'll get the JS call stack with all the method calls and positions that cause the issue.
You can even click the line number and directly see the code that's causing it.
Also check the last ajax response (/zkau request) and see which component was added, or changed last, this will help reducing the code to have an isolated example only focussing on the atomic operation causing the trouble.
Usually by removing anything that's not required to reproduce the issue, a case can be simplified down to something like that (http://tracker.zkoss.org/browse/ZK-2448)
Regards,
Robert
Tags
People
Badges
Help
do you have a simple reproducing sample you can post on zkfiddle.org?
cor3000 ( 2014-10-20 07:34:53 +0800 )editUnfortunately it's quite complicated to isolate to "buggy treeitem", because all Composer to the corresponding zul-Pages use the same Composer and some work and some don't. Maybe I found a hint, but I don't know what to do with this:
salbader ( 2014-10-20 15:28:57 +0800 )editthe missing url: http://stackoverflow.com/questions/14113196/zkoss-failed-to-process-setattr-cannot-call-method-set-of-null-typeerror
salbader ( 2014-10-20 15:30:09 +0800 )edit