[MAGNOLIA-3571] AdminCentral button - JS error Created: 28/Feb/11  Updated: 09/Jul/12  Resolved: 25/May/12

Status: Closed
Project: Magnolia
Component/s: admininterface, gui
Affects Version/s: 4.3.8, 4.4.2, 4.5.2
Fix Version/s: 4.4.9, 4.5.3

Type: Bug Priority: Neutral
Reporter: Matteo Pelucco Assignee: Milan Divilek
Resolution: Fixed Votes: 1
Labels: AdminCentral, MainBar, greenbar, javascript, js
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File screenshot.628.jpg    
Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

A customer noticed that the "AdminCentral" button in the Main Bar sometimes stops to work, giving a JS error.
These are the steps to reproduce it:

1) Open a IE8/FF browser in a new browser window (A)
2) Clean all browser history / data
3) Point directly to this url: http://demo.magnolia-cms.com
4) Provide username / password
5) Open (double-click) the demo-project page. It opens a new browser window, (B)
6) Now close the (A) window
7) Click on the AdminCentral button.

– JS error (javascript.js)

In Firefox, you obtain the same behaviour opening (drag&drop outside browser app) the B window in a new browser window.



 Comments   
Comment by Federico Grilli [ 18/Mar/11 ]

Hi Matteo, I tried to reproduce the bug with FF 3.6.15 but it worked fine. I'll try with IE8 too. Can you please tell me if the problem occurs on a CE or EE instance? In the latter case, is the soft-locking module by chance enabled?

Comment by Federico Grilli [ 18/Mar/11 ]

Ok, I can partially answer myself. I've seen that the problem also concerns Magnolia versions prior to 4.4.2, then the soft-locking module can be ruled out as a culprit.

Comment by Matteo Pelucco [ 21/Mar/11 ]

Hi Federico,
it has been tested over demo.magnolia-cms.com few weeks on 28 of Feb (2011). I think it was over a 4.4.1 version, the one installed on your demo servers.

I don't think the soft-locking can solve this, because it is a javascript issue (window.parent is null at certain time).
I'm able to reproduce now it over Win 7 (64bit), IE8 8.0.7600.16385, demo.magnolia-cms.com.

Really strange..
M.

Comment by Philipp Bärfuss [ 22/Mar/11 ]

I have a suspicion:

In AdminCentral.js line 200. MgnlAdminCentral.showContent calls DHTMLUtil.findVariable("mgnlAdminCentral") which fails for what ever reason.

Comment by Hay Kranen [ 24/Aug/11 ]

I can confirm this problem in both IE8 / XP and IE9 / Windows 7. When clicking the Admincentral button nothing happens and you get a Javascript error with debugging turned on.

Comment by Hay Kranen [ 24/Aug/11 ]

We're running 4.4.4 by the way.

Comment by Federico Grilli [ 24/Aug/11 ]

That's weird. I just tried to reproduce it on FF latest version and our demo author (Magnolia EE 4.4.4). What actually produced a js error was following the 2nd step suggested by Matteo (drag&drop B window + closing the adminCentral window/tab). At that point, the following error sometimes (not always) occurs

MgnlDHTMLUtil is not defined
[Break On This Error] MgnlDHTMLUtil.hide(this.divContent);
javascript.js (line 3603)

and nothing happens, namely no adminCentral page is open.

Comment by Ondrej Chytil [ 21/May/12 ]

Also confirmed on current demo (4.5.2).

Comment by Richard Unger [ 21/May/12 ]

We had the same problem (Magnolia EE 4.4.2, 4.4.6).

The problem occurs when the user closes the AdminCentral Browser Tab, and then chooses "AdminCentral" in an Editor Browser Tab.
This problem only really occurs with editors who do not have strong computer skills, and therefore get confused working with multiple browser tabs.

We "fixed" the problem by replacing the call to MgnlAdminCentral with some javascript to explicitly open a new AdminCentral Browser Tab each time.

This has been working much better for us - it would seem that the users who were confused by this error get less confused if a new browser tab opens each time. I think this is also because the new browser tab normally gets focus, whereas the previous solution, depending on the browser, left the admin-cetral tab in the background.

Comment by Jan Haderka [ 23/May/12 ]

Setting priority to critical to make sure we do not release w/o fix. Reset to neutral once done.

Generated at Mon Feb 12 03:47:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.