Separately from my client’s login issue, I’m having the same problem as KingNisha had - however for me it’s intermittent, so I suspect it’s not related to my Chrome settings (?)
I am unable to login directly to the editor view using ?edit and the Editor login. That appears to be by design. But if I invoke the Editor from the Dashboard or Design mode, I’m sometimes asked to login as an Editor, and other times the Editor is invoked successfully.
My best guess is the way you have cookie expiration set for the authentication tokens. If the Editor-mode authentication tokens expire sooner than the Designer-model authentication tokens, then it can happen that I’m successfully working in the Designer, but the Editor has terminated my authentication.
I’ve notice that if I re-publish the site from the Designer, and then try to invoke the Editor, the Editor’s authentication tokens seem to be re-generated and I’m usually allowed in.
Unfortunately, that’s often not an option - I can’t always re-publish a full site when small corrections are needed.
It’s also lot of steps to go through to fix a typo.
Is there a workaround to the Administrator login-as-Editor problem? What I’m finding is that when I want to work on content, Editor mode is often the most practical way to do that.
Currently if I’m looking at a published website, and see something I want to change, I have to-
- Go to Webflow.com
- Click Dashboard
- Find the right website in the Projects list
- Click the drop down menu to access the Editor mode
- Wait for the homepage to load in Editor mode
- Then navigate my way to the page I was just looking at
- Make the correction
- And publish
It feels like the Administrators-can’t-login-as-Editors restriction handicaps a lot of the advantage that the Webflow Editor gives.