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

[BUG][UX] back-end publish process quirks #5085

Closed
jadwigo opened this issue Mar 25, 2016 · 2 comments
Closed

[BUG][UX] back-end publish process quirks #5085

jadwigo opened this issue Mar 25, 2016 · 2 comments
Labels
open PR A pull request exists to match the needs in this issue UX/UI

Comments

@jadwigo
Copy link
Contributor

jadwigo commented Mar 25, 2016

The process of publishing from the content listing has some weird quirks.

The first two steps are normal
image

image

But the third step tells me "there is no undo" which is just FUD for this action.
image

The real quirk comes after I confirm - only the published records are displayed and I have to refresh the page to get the other records back. The pager is hidden too.

image

Details

  • Relevant Bolt Version: 3.0 / master
  • Install type: Composer install
  • PHP version: 5.6
  • Used webserver: Apache
  • For UX/UI issues: Chrome Version 49.0.2623.87 (64-bit) Linux
@ankedsgn
Copy link

Are you sure you want to publish? THERE IS NO UNDO! :')

@SvanteRichter
Copy link
Contributor

Seems like the "only the published records are displayed" after publish is fixed, but the FUD remains...

SvanteRichter added a commit that referenced this issue Jul 31, 2016
This does two things:
1. check if the request is safe (just status change) or unsafe (delete)
and only ask the user to confirm if it is unsafe.
2. Allow unpublished records in the async zone, since all async routes
are on the backend and should therefore show unpublished too.
@SvanteRichter SvanteRichter added open PR A pull request exists to match the needs in this issue and removed needs verification labels Jul 31, 2016
bobdenotter added a commit that referenced this issue Aug 3, 2016
Fix backend publish process quirks (#5085)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open PR A pull request exists to match the needs in this issue UX/UI
Projects
None yet
Development

No branches or pull requests

3 participants