Re: An extra element in the HTML plugin cause js exception

2012-10-12 Thread Uri Scheiner
Yes, you can workaround it if you strip your config.jelly and leave just one f:section element that wraps the entire form On Thu, Oct 11, 2012 at 8:18 PM, Jesse Glick jgl...@cloudbees.com wrote: On 10/03/2012 06:34 AM, Uri Scheiner wrote: I've noticed that when adding a post-build plugin that

Re: An extra element in the HTML plugin cause js exception

2012-10-11 Thread Jesse Glick
On 10/03/2012 06:34 AM, Uri Scheiner wrote: I've noticed that when adding a post-build plugin that I developed it results in *Uncaught TypeError: Cannot read property 'firstChild' of null* . Ran into the same problem myself. Filed as JENKINS-15494 [1] for tracking. [1]

Re: An extra element in the HTML plugin cause js exception

2012-10-09 Thread Uri Scheiner
Hi, It seems like I found the problem - I had an 'Advanced' element (f:advanced) under a separated f:section. It worked fine with the previous UI. You need to be very careful with the tags you're using in the config.jelly file.. Uri On Tue, Oct 9, 2012 at 8:46 PM, Uri Scheiner