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

[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 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] 
 https://issues.jenkins-ci.org/**browse/JENKINS-15494https://issues.jenkins-ci.org/browse/JENKINS-15494




-- 
*Uri Scheiner*
Functional Architect | *Nolio*

*O*:972 (9) 9597307
*E:*:u...@noliosoft.com

Find out more about Nolio:
Website http://www.noliosoft.com/ | Twitterhttp://twitter.com/#!/noliosoft
 | Youtube http://www.youtube.com/user/NolioSoft |
LinkedInhttp://www.linkedin.com/groups/Application-Release-Management-Automation-1963650?mostPopular=gid=1963650

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

[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] https://issues.jenkins-ci.org/browse/JENKINS-15494

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

[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 u...@noliosoft.com wrote:

 Hi Guys,

 Any of you have any idea about this? I'm trying to find a way to control
 the CSS of my plugin, but finds nothing..

 Any hint will be appreciated..

 Uri


 On Wed, Oct 3, 2012 at 12:34 PM, Uri Scheiner u...@noliosoft.com wrote:

 Hi all,

 I've noticed that when adding a post-build plugin that I developed it
 results in  *Uncaught TypeError: Cannot read property 'firstChild' of
 null* .

 I debugged the javaScript that runs when adding the plugin and I've
 noticed the following behavior:

 In general, the element that represents the plugin UI should have one
 child - a table element that contains the attributes that should be
 displayed to the user. However, I've noticed that my plugin has two childs:

 1. A link element: * link rel = stylesheet href=
 /jenkins/adjuncts/d3d844aa/lib/form/section_.css type=text/css*
 2. A table element.

 When I changed the JavaScript, my plugin worked fine.
 My question is - how do I get rid from the 'link' element? I tried to
 modify the config.jelly file but no luck. Any ideas? I've debugged other
 plugins and none of them had this 'link' element so I wonder what made it
 appear.

 Thanks,
  Uri