Hi,

 

• When you looked at the source of the page: did you only look at the link-tag (<a href=) ? It's normal that you don't see any events attached there: all events are attached at the end of the XPage using (XSP.attachEvent) calls.
• Regarding the duplicate scripts: I've experienced that myself a couple of times too. It occurred by me to when copy-pasting code. Only fix I know of is to manually delete the duplicates.

Mark

 

PS: if you want to make your code a little more compact, you can use a shorthand JS expression for IF-statements:

( <if statement> ? <true result> : <false statement> )

Your function would then look like this:

sessionScope.put("docToCollapse", (sessionScope.get("docToCollapse")=="Expand" ? "Collapse : "Expand") );

Mark, Thank you for the advise on the syntax, I will use that!

 

Regarding the  script itself, I also looked at xsp.attachEvent, and I saw the following:

 

 XSP.addOnLoad(function() {

XSP.attachEvent("view:_id1:_id2:_id4", "view:_id1:_id2:image1", "onclick", null, true, false);
XSP.attachEvent("view:_id1:_id11", "view:_id1:_id10", "onclick", null, true, false);
XSP.attachEvent("view:_id1:_id12", "view:_id1:link11", "onclick", view__id1__id12_clientSide_onclick, true, false);
XSP.attachPartial("view:_id1:_id13", "view:_id1:link12", null, "onclick", function(){}, false, "view:_id1");
XSP.attachEvent("view:_id1:_id14", "view:_id1:link13", "onclick", null, true, false);
XSP.attachEvent("view:_id1:_id15", "view:_id1:DealsLink", "onclick", null, true, false);}

Maybe I do not understand smth, but it looks like, as if there were no code written in designer, which is not true.

 Thank you, Paul! I will also use that feature.

But the issue with the vanishing script bothers me more, since I cannot use any script at all. 

Check to ensure the event handler is in the right place, i.e. a child of the correct XPages control. I've had that problem before, where my event wouldn't trigger because it was attached to the wrong control. I eventually worked it out by using Compare With\Local History from the right-click menu in the Source pane and rolling back to a previous version. 

 

I've seen something like that with client-side javascript script not getting rendered to the browser at all though. The strange thing was it was a basic error page I'd copied across. In one database the section expanded, in another it didn't. The code was identical. I think I ended up deleting the XPage and pasting the code into a new version. It may be that something gets broken in the underlying conversion to Java (in the case it never gets rendered to the browser at all). In that case I'd probably try copying and pasting the code into something like NotePad from the Source pane, then copying and pasting it back into a new XPage, just to ensure it's definitely just plain text you're pasting in. One of the beauties of XPages is we can do something like that, which was not possible in forms-based design.

 In fact it was the second time I encountered this problem and I tried to solve it with copy-pasting into a new XPage.

Actually I resolved the issue - I also have a dojox widjet on the page (graphs) and the "compressed" file (i.e. the one where the code is compressed into single line) was loaded with an error. But when I totally deleted the widjet and the source link to dojox, everything went just fine. 

It seems that this error just blocked all the other scripts. 

 

Anyway, thanks for help!