Home » forums » Luminis Platform / System

Javascript error in Lum 4.0.2.41 and higher

Submitted by wjdennen on Tue, 2008-08-12 11:42

Hi, We're testing 4.0.2.41 on our test server - it's a clean environment, with no customizations made to nested-tables. We're seeing a Javascript error when accessing Banner Self Service channels. Specifically, Firefox complains: Permission denied to get property Window.document [Break on this error] var ohead =top.document.getElementsBy...Name('frame')[1].contentWindow.document; The javascript appears in nested-tables.xsl on line 523. The line reads: var ohead =top.document.getElementsByTagName('frame')[1].contentWindow.document; It is within the function: function initAlert() It appears this code was added in the recent hotfixes, since we do not see it in our 4.0.2 (no hotfixes) install. Has anyone else seen this? We filed a support ticket with SunGard but they can not replicate it. -Bill

‹ Weather Channel through XML transformation II Site Map Questions? ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

more info

Submitted by wjdennen on Tue, 2008-08-12 13:45.

I have a bit more info. I turned on javascript debugging in Safari and it displayed a better explanation:

Unsafe JavaScript attempt to access frame with URL http://ssbserver.school.edu:9024/pls/BLMD/bwpkebst.P_DispIDSelect from frame with URL http://luminisserver.school.edu/render.UserLayoutRootNode.uP?uP_tparam=utf&utf=%2fcp%2fip%2flogin%3fsys%3dsctssb%26url%3dhttp://ssbserver.school.edu:9024/pls/BLMD/bwpkebst.P_DispIDSelect. Domains, protocols and ports must match.

The important line is: Domains, protocols and ports must match.

So, this particular error seems to be generated because our Luminis server is running on port 80 and the SSB server is running on port 9024 (on a different machine). Ok...

But, I imagine we'd also get this error in our PROD environment, where Luminis is running on port 80 and SSB is running on 443 and the protocols are different.

Has anyone else seen this? It's new in the IV.0.2 hotfixes. Thanks.

Defect

Submitted by wjdennen on Tue, 2008-08-12 16:25.

Sungard has acknowledged the problem and is filing this as a defect.

anyone else?

Submitted by wjdennen on Wed, 2008-09-17 16:20.

has anyone else run into this error? I'm looking for a workaround while we wait for SunGard to address it. Thanks.

 The defect is now fixed and

Submitted by jempey on Fri, 2009-06-26 16:37.

 The defect is now fixed and will be released with 4.2.2.

thanks

Submitted by wjdennen on Sat, 2009-06-27 01:18.

 thanks, do you know if there is any chance of this fix being applied to 4.1.1x?

Seeing it too

Submitted by gprellwitz on Tue, 2008-11-04 19:46.

We're seeing this too in Lum 4.1.0.22 build 22. Though we haven't tracked it down to the xsl yet.

Grant Prellwitz, Lead App Developer
Harper College, Palatine, IL

Defect

Submitted by dmmcinto on Wed, 2009-03-04 12:24.

Do you know what defect number it is? I have been looking for it.

David

Unfortunately, no

Submitted by wjdennen on Wed, 2009-03-04 13:16.

Unfortunately, no I don't have the number. I was told it was on an "internal list" or something like that.

1-235797229

Submitted by wjdennen on Wed, 2009-03-04 14:34.

Can you see SR # 1-235797229?

On 2/5/2009, I wrote:
I've not seen any mention of this bug in the docs for 4.1.1.x or 4.2. Could you tell me if it's been fixed? Thanks.

On 2/6/2009, SunGard responded:
Looks like the defect is still in coding right now. There has not been a fix yet.

Defect

Submitted by wjdennen on Wed, 2009-03-04 16:11.

SunGard responded with the defect number:

Defect #: 1-3WIZZ2

It says:

Targeted Version: 4.2.1

Sadly...

Submitted by wjdennen on Wed, 2009-05-27 22:46.

Sadly, this is now slated for 4.2.2.

Workaround?

Submitted by wjdennen on Sun, 2009-06-21 18:18.

Has anyone found a workaround for this javascript error? Thanks.

Syndicate content