Dashboard login popup not displaying on the most recent Chrome version

[ghost]

@mrangnekar commented on Oct 18, 2016, 5:31 AM UTC:

http://exist-db.org/exist/apps/dashboard/index.html login popup not displaying on Chrome 54.0
dijitpopup not working.

This issue was moved by duncdrum from eXist-db/exist#1150.

[ghost]

@dizzzz commented on Oct 20, 2016, 8:01 PM UTC:

Please can you share a screenshot? Can you exactly describe how to to reproduce?
macOS/ 54.0.2840.59 beta (64-bit) works just fine for me,

Which exist-db version? What operating systems the browser running?

[ghost]

@joewiz commented on Oct 20, 2016, 8:36 PM UTC:

I'm also unable to reproduce, using same OS & Chrome version as dizzzz.

mrangnekar I assume you mean the URL you provided and not your own eXist installation? In this case, no need to report your eXist-db version.

[ghost]

@mrangnekar commented on Oct 20, 2016, 8:38 PM UTC:

It's the url http://exist-db.org/exist/apps/dashboard/index.html
Behaves same way on Mac and Windows with Chrome recent version

[ghost]

@dizzzz commented on Oct 20, 2016, 8:42 PM UTC:

I actually tested my local version :)

The demo server need to be updated, I think it is RC1 or older? JoernT ljo

[ghost]

@joewiz commented on Oct 20, 2016, 8:43 PM UTC:

Please right-click on the page and select "Inspect" to bring up Chrome's developer window. Select the Console pane and shift-reload the page. Are any errors reported? If not, select the Network pane and shift-reload the page again. Do any of the requests have a status other than 200 or 304?

[ghost]

@mrangnekar commented on Oct 20, 2016, 8:44 PM UTC:

Also my local version doesn't work-Dijitpopup doesn't get displayed

[ghost]

@joewiz commented on Oct 20, 2016, 8:45 PM UTC:

dizzzz So you are able to reproduce? (I am still unable to, in Chrome or Safari.)

mrangnekar Okay, then you need to report your eXist-db version.

[ghost]

@mrangnekar commented on Oct 20, 2016, 8:50 PM UTC:

existdb project version 2.2

[ghost]

@dizzzz commented on Oct 21, 2016, 4:45 AM UTC:

Can't reproduce

Do you have any content / JavaScript blockers running?

[ghost]

@sgmlguru commented on Oct 25, 2016, 5:23 PM UTC:

I have this problem on Chrome 54.0.2840.71 in Linux running eXist 2.2. Interestingly, if I click on Collections instead, the Login popup appears and I can log in.

Oh, and I have no content or JavaScript blockers running.

[ghost]

@mrangnekar commented on Oct 25, 2016, 6:14 PM UTC:

Please see attached- This is on Chrome 54.0

On Thu, Oct 20, 2016 at 3:01 PM, Dannes Wessels notifications@github.com
wrote:

please can you share a screenshot?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1150 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV18kjps24djBlfEBMlDMbHLXnGsJ3y9ks5q18iCgaJpZM4KZZEr
.

[ghost]

@dizzzz commented on Oct 25, 2016, 7:46 PM UTC:

all of the following just work fine (macOs)

53.0.2785.143 (64-bit)
54.0.2840.71 (64-bit)
55.0.2883.21 beta (64-bit)

which exact versions of the browser are involved? what about upgrading the browser?
on existdb nothing has changed....

[ghost]

@sgmlguru commented on Oct 25, 2016, 8:58 PM UTC:

As I said, Chrome 54.0.2840.71, 64-bit, running on Ubuntu Linux and the Cinnamon desktop. I got Chrome directly from Google, so not the upstream Chromium one. Also, the eXist DB install is completely fresh.

I can reproduce this behaviour on Windows and macOS. The difference between my setup and everybody else's, of course, is that I am syncing my Chrome setting on all of my computers, so I should probably test what happens when running a non-synced Chrome.

[ghost]

@sgmlguru commented on Oct 25, 2016, 9:52 PM UTC:

So I just tried the following on my Linux install:

Removed the addon (Adblock Plus, that was already disabled on localhost where I access eXist). No login popup.

Disconnected the browser from my Google account and deleted cache, cookies, etc. No login popup.

Completely removed Chrome, including everything in ~/.config/google-chrome. Reinstalled version 54.0.2840.71, 64-bit, (Google's .deb package) but without any settings or changes whatsoever, and immediately went to localhost. No login popup.

Also tested installing Chromium, v 53.0.2785.143, 64-bit, from Ubuntu's .deb sources. Vanilla, nothing extra. No login popup.

Then I remembered that I do have one laptop with Chrome and a local eXist instance, never synced with my Google account. This is a client laptop running Win7. When I checked the Chrome version, it was 53 something but started to automatically upload a later one, so I quickly checked eXist. The popup login worked.

After the update, it was on latest 54 something and the login popup still worked.

And finally, I tested using my wife's laptop (Win 10, 64-bit, Chrome 54 something) and opened a remote eXist instance I have running on a VPS. No login popup.

My conclusions? Not that many, but it's fairly obvious that the exact version of Chrome doesn't matter. I'm starting to wonder if there is some weird external dependency of some kind. This is driving me nuts.

[ghost]

@dizzzz commented on Oct 28, 2016, 8:29 PM UTC:

thank you for your extensive investigation and .... patience. Maybe wolfgangmm JoernT or windauer have a similar experience?

[ghost]

@joewiz commented on Oct 28, 2016, 8:56 PM UTC:

To the people who are seeing the problem: following the suggestions at #1150 (comment) and reporting the error info requested may yield helpful troubleshooting information - especially JavaScript errors reported via the Console pane.

[ghost]

@sgmlguru commented on Feb 19, 2017, 7:58 PM UTC:

Sorry for not getting back with more feedback earlier.

Testing this on eXist 3.0 (that I finally got running after resetting my browsers). Chrome v 54.0.2840.71 (64-bit) on Ubuntu Linux and the Cinnamon desktop won't show the login popup. Firefox v 51.0.1 (64-bit) has the same issue. Neither has any plugins or add-ons enabled.

I've followed Joe's debug suggestions in Chrome but no errors are reported. There's just no login popup unless I click on the Collection Browser when logged out.

[ghost]

@mathias-goebel commented on Jun 15, 2017, 7:14 AM UTC:

as it affected my instances / browser combination (Version 59.0.3071.86 (Official Build) (64-bit)) as well, i can recommend using the Monex app to login - it will create a persistent session/cookie and the dashboard will work as expected. it is just a workaround, but ok.

lets have a look on the browsers console when working with 3.2.0 and the chrome named above, Dashboard is Version 0.4.7:

1. loading dashboard app:
   • nothing besides a console.log from dashboard-1.7.js:373 Login: Not logged in
2. when clicking on "Not logged in" - i want the popup:
   • nothing. the button will be highlighted, but nothing else happens.
3. when clicking on one of the apps loading within the dashboard (e.g. collection browser)
   • triggers the popup (YEAH!)
   • login works
   • everything is fine within this app (collection browser, backup, scheduler tested so far)
4. since we have a login (see 3.) we want to manage some packages
   • but why i am asked to login again? ok, at least we see the popup.
   • login doesnt work, JS XHR fires full blast

plugins/packageManager/packageManager.html Failed to load resource: the server responded with a status of 401 (Unauthorized)
dojo.js:182 Error: Unable to load plugins/packageManager/packageManager.html status:401
dojo.js:54 Error: Unable to load plugins/packageManager/packageManager.html status:401
dojo.js:54 Error: Unable to load plugins/packageManager/packageManager.html status:401
dojo.js:54 Error: Unable to load plugins/packageManager/packageManager.html status:401

may be there is another issue i encountered that is related. when i work with eXide, i have to login for every task again and again. when i want to store an object: login. when i want to open the "manage" dialog: login. everytime. :(

[ghost]

@gmella commented on Jan 29, 2018, 7:46 AM UTC:

Just a small feedback because I noticed that login in the dashboard as admin with "Remember me" checked changed a lot the behaviour of the package manager after that.

[joewiz]

@mrangnekar @mathias-goebel @sgmlguru We have not had any recent reports or experience of this since #64. We'll soon be replacing this dashboard with a new one, https://github.com/eXist-db/existdb-dashboard, so we'd appreciate your testing of login on the new app with the systems in question.