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

Publish confirmation panel doesn't close after publishing #4560

Closed
maddisondesigns opened this issue Jan 18, 2018 · 8 comments
Closed

Publish confirmation panel doesn't close after publishing #4560

maddisondesigns opened this issue Jan 18, 2018 · 8 comments
Labels
[Type] Question Questions about the design or development of the editor.

Comments

@maddisondesigns
Copy link

Issue Overview

After publishing a page, the Publish sidebar panel remains open. This is really confusing as it's showing the following text;

Are you ready to publish?
Here, you can do a last-minute check up of your settings below, before you publish.

gutenberg-publishpanel

This panel should close as soon as the page is published.

Steps to Reproduce (for bugs)

  1. Create new page
  2. Insert content
  3. Click Publish
  4. Click Publish
  5. Verify that the publish panel remains open

Expected Behavior

The publish panel should close as soon as the page is published. Asking if I'm ready to publish, after I've just published, is wrong and confusing

Current Behavior

Publish panel remains open with confusing message

Related Issues and/or PRs

Please note that this is a different issue to the one mentioned in #4470. That is an issue with the panel remaining after creating a new page. This is an issue with the panel remaining open after publishing the current page.

Firefox Quantum 57.0.4 (64-bit)
Gutenberg 2.0.0
WordPress 4.9.2

@youknowriad
Copy link
Contributor

This area is meant for post-publish information like "preview link", "social media" sharing options etc... I think that's intended.

@youknowriad youknowriad added the [Type] Question Questions about the design or development of the editor. label Jan 18, 2018
@maddisondesigns
Copy link
Author

maddisondesigns commented Jan 18, 2018

Eww I hope not. That'll be really annoying if we have to constantly close this every single time. Gutenberg is already making the Publishing process more difficult by insisting on having that two-step publishing process. Adding this in as yet another step, would be really, really annoying and frustrating. At the very least if you don't remove it, that message needs to be changed/removed, because that's extremely confusing. Gutenberg is supposed to be making things easier for end users, not more cumbersome and time consuming.

Also, there's already a Preview link in the panel/header below this panel, so having one in this new panel as well, is kinda pointless.

@youknowriad
Copy link
Contributor

After long discussions, the design of this panel has been discussed and agreed on in #3496. I understand that it may pointless for you but the majority thinks the post publish panel is something important to have. That doesn't mean this can't be iterated in the future if there's further evidence on this being an issue.

Closing for now

@maddisondesigns
Copy link
Author

@youknowriad So, you're seriously going to leave that message "Are you ready to publish?
Here, you can do a last-minute check up of your settings below, before you publish.", after the page is already published??

@youknowriad
Copy link
Contributor

@maddisondesigns If you still see this message after the page has been published, then it's a bug. Can't see it myself

@maddisondesigns
Copy link
Author

@youknowriad I provided a screenshot when I raised the issue, that shows exactly this!

@youknowriad
Copy link
Contributor

@maddisondesigns but I can't fix the bug if I can't reproduce. If you would provide more information, that would be great. Do you see JS errors?

@maddisondesigns
Copy link
Author

I've just tried publishing a few more pages and it's not showing that message now. If you want to close this, that's fine. People are going to constantly experience these random issues though and they're going to be ignored because they can't be reproduced consistently. This thing is so horribly inconsistent and unstable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Question Questions about the design or development of the editor.
Projects
None yet
Development

No branches or pull requests

2 participants