Gary D.
New Member Posts:4
|
10/06/2007 7:20 AM |
|
I managed to have the installation of the trial version done on a clean DNN 4.5.5. After adding the module onto the page, it appears to have some javascript error at the left bottom of the page.
"Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus"
Any idea?
|
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
10/07/2007 9:44 PM |
|
Compression on pages? Whitespace filtering? I've not seen this error before in any case. |
|
|
|
|
Gary D.
New Member Posts:4
|
10/08/2007 4:33 AM |
|
I do not think so. the related Host settings are shown below:
Performance Settings
Compression Settings
Enter a list of excluded Paths.
|
|
Enter a Regular Expression filter for removing whitespace.
|
|
Update |
Other Settings
|
|
|
|
|
Gary D.
New Member Posts:4
|
10/08/2007 4:51 AM |
|
I tried in FireFox, it looks OKay. The javascript error only appears in IE 6.0. Thanks. |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
10/09/2007 9:27 AM |
|
It should work just fine in IE (6 or 7). I'll keep an eye out for this error. For now I can't do anything as I can't replicate this. |
|
|
|
|
cmorton
New Member Posts:1
|
11/13/2007 1:03 PM |
|
I have the same error - isolated to when DMX4 is loaded onto a page ie 7.0.5730.11 An error has occurred in the script on this page. Line: 2 Char: 40970 Error: Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus. Code: 0 URL: http://...../default.aspxI can't be sure, but I believe it appeared after running one of the embedded scripts in DMS - insert base folder, prepare portal |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
11/13/2007 4:26 PM |
|
Hi Craig, Did it have any effect on the functionality? I'm trying to track this one down, but I'm not sure where it's hiding. Thanks for the hint by the way. Peter |
|
|
|
|
pwegrzy
New Member Posts:2
|
11/16/2007 3:49 PM |
|
Peter, I believe Chhavi has contacted you on this as well (we're about to roll back from DMX4 to DMX3 because the javascript error renders DMX powerless, but it has to do (at least in our case), with child portals. It wasn't like this before we were on DMX4.0.1, but when we went to DMX 4.0.6 patch that we ran into all this. Its causing DMX not to properly load on our child portals, which makes the product useless on those portals. fyi..we're running DNN4.5.5 as well. |
|
|
|
|
pwegrzy
New Member Posts:2
|
11/16/2007 3:58 PM |
|
Sorry, my previous post might be unclear, let me try again. We didn't seem to have any problem with DMX4.0.1 (although I don't think we tried it on child portals). We upgraded our live environment (which unfortunately is an intranet so we can't get you access), and applied 4.0.6. Now, DMX does not work properly in our child portals, so we are looking at rolling back to DMX3.
WhenDMX tries to load in our child portals, we get the above javascript message, the stylesheet isn't applied, and therefore the UI is a mess (ex. the dropdown menus are behind the folder names, etc...) and unacceptable for usage.
The error may not be the root cause, I'm not sure.
|
|
|
|
|
Rob Ralston
Basic Member Posts:164
|
12/08/2007 5:18 PM |
|
Hi Peter,
This error is still present even with 4.01 RC4. Whitespace filter OFF. I had GZip Compression, but turned that off to test. Same result. However, I am not seeing any obvious side effects as the above users have seen.
Rob Ralston |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
12/10/2007 7:19 PM |
|
I haven't been able to determine how to produce this reliably. If I refresh a page it goes away. If anyone knows how to do this, please let me know. @Phil: I cannot imagine css loading depends on this. It sounds like another issue to me. Let me know how things go.
Peter |
|
|
|
|
Stuart Hilbert
New Member Posts:39
|
02/06/2008 3:08 PM |
|
I am also getting a Javascript error everytime I add the DMX module to the page.
In IE 7 the error is being reported as, "Sys.UI.DomEvent is null or not an object".
In IE 6 the error is being reported as "Sys.Application is null or not an object".
Haven't updated to the latest patch but I hope today.
Thanks,
Stuart |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
02/06/2008 10:23 PM |
|
This is caused by the 'old' ComponentArt controls suite on an Ajax enabled installation. Recent versions of DMX carry a newer version of this.
Peter |
|
|
|
|
Rob Ralston
Basic Member Posts:164
|
03/08/2008 6:53 PM |
|
Hi Peter,
Some further info on this. Aside from the persistent error listed above, I have also found that clicking around on various folders can cause another, more intrusive error.
The right side grid area goes into an endless loop attempting to refresh (the rotating arrows just keeps rotating). When this happens, another page error occurs which says:
Error: 'Grid1' is null or not an object"
Code: 0
Also, it seems this occurs most often (maybe exclusively) to non-admin users. The only way to clear it is to refresh the page (or leave page and come back).
If I can gather any addtional information to help you, please let me know.
Rob Ralston |
|
|
|
|
Guido Kuehler
Basic Member Posts:149
|
03/27/2008 12:57 PM |
|
The Focus-Javascript Error is also exist by DMX 04.02.01 and when used IE 6 An error has occurred in the script on this page. Line: 2 Char: 40970 Error: Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus. Code: 0 URL: http://...../default.aspx |
|
|
|
|
Solyad
New Member Posts:9
|
|
Peter Donker
Veteran Member Posts:4536
|
04/23/2008 7:40 PM |
|
Regarding the 'eternal refresh' I can't see an easy solution. Ajax means the browser goes back to the server to get data. If something goes wrong there are not that many fallbacks. I have noticed that timing is an issue. When the callback has not completed and you do something else, it can go all screwy. And timing depends on you connection speed. So there is no one single solution that'll fit all. If something goes weird I refresh the page and normally all is good after that.
About the 'focus' error: I can't give that a high priority. Again it's most likely an Ajax timing issue. I can't properly debug it because the faulty code is somewhere deep in obfuscated code by the UI component manufacturer. There is also no fixed replicable set of actions to see it. So as long as this does not impede functionality I will leave it at that and hope the manufacturer fixes it one day.
Peter |
|
|
|
|
Benjamin Hermann
New Member Posts:3
|
06/19/2008 9:40 PM |
|
hi guys,
I have the same two erros in on of my DMX4 installations too. Any news about ths issues? |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
06/23/2008 1:53 PM |
|
Hi Benjamin, The focus error: nothing yet. The Sys.UI.DomEvent error: that was done a while back and should not appear in recent DMX installations. Peter |
|
|
|
|