Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a more friendly way of unlocking zones #44

Open
pkevan opened this issue Mar 8, 2016 · 10 comments
Open

Creating a more friendly way of unlocking zones #44

pkevan opened this issue Mar 8, 2016 · 10 comments

Comments

@pkevan
Copy link
Contributor

pkevan commented Mar 8, 2016

Currently when the zone lock times out the user is forced back to the tab/window where they were locked into a zone.

This is pretty bad UX and it would be nicer if it just silently took them out of the zone.

Reporting in Chrome (latest version) on Windows/Mac

@sboisvert
Copy link
Contributor

@brettshumaker Can you have a look?

@brettshumaker
Copy link
Contributor

@sboisvert While testing on the latest Chrome in Mac, if the user is still on the zone edit screen when the lock times out, an alert pops up that notifies them of the lock timeout. Once the user closes the notification or leaves the tab, the redirect occurs.

If the user is on another tab/window in Chrome when the lock times out, the redirect just happens without any notification but the user isn't forced back into the tab/window containing the zone edit screen. So it looks like this behavior may have been changed in Chrome since this issue was reported.

That being said, I can see how it could be jarring for a user who navigates back to edit a zone only to find themselves on the WordPress dashboard. I'd suggest keeping the JS alert with the redirect, but maybe just back to /wp-admin/admin.php?page=zoninator with an admin notice saying that their zone lock had expired.

Thoughts on that approach?

@sboisvert
Copy link
Contributor

I'd suggest keeping the JS alert with the redirect, but maybe just back to /wp-admin/admin.php?page=zoninator with an admin notice saying that their zone lock had expired.

I like this idea. let's go with that.

@brettshumaker
Copy link
Contributor

Currently when the zone lock times out the user is forced back to the tab/window where they were locked into a zone.

@pkevan Are you still seeing this behavior in the latest version of Chrome?

@sboisvert
Copy link
Contributor

Even if the tab doesn't steal the focus anymore I think we can go forward with this change.

@pkevan
Copy link
Contributor Author

pkevan commented May 3, 2018

@pkevan Are you still seeing this behavior in the latest version of Chrome?

Sorry, meant to reply earlier (but forgot), I had the tab still open but it didn't force me to that tab (or I would have replied sooner :) )

I agree that having some message to indicate it's been moved would be useful.

brettshumaker added a commit to brettshumaker/zoninator that referenced this issue May 3, 2018
Zoninator Automattic#44

Changed the `error-zone-lock-max` message to reflect the updated redirect url.
brettshumaker added a commit to brettshumaker/zoninator that referenced this issue May 3, 2018
Zoninator Automattic#44

Added an admin notice when a user's zone lock expires and they get redirected to the top level zones page.
@brettshumaker
Copy link
Contributor

@pkevan Thanks for the follow up! 👍

@brettshumaker
Copy link
Contributor

@sboisvert See this commit for the admin notice addition: 6cc0194

@pkevan
Copy link
Contributor Author

pkevan commented May 5, 2018

@brettshumaker can you make this a PR?

@brettshumaker
Copy link
Contributor

@pkevan Done. 👍 #74

brettshumaker added a commit to brettshumaker/zoninator that referenced this issue May 9, 2018
Zoninator Automattic#44

We needed to check and make sure that `$zone` is not `false` coming back from `$this->get_zone()` otherwise a PHP Warning is thrown.
brettshumaker added a commit to brettshumaker/zoninator that referenced this issue May 9, 2018
Zoninator Automattic#44

Fixed a whitespace issue in new code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants