Make WordPress Core

Opened 4 years ago

Last modified 19 months ago

#50823 accepted feature request

Miss button add new post on page edit post (editor guttenberg)

Reported by: welitonmartins's profile welitonmartins Owned by: audrasjb's profile audrasjb
Milestone: Future Release Priority: normal
Severity: major Version: 5.4.2
Component: Editor Keywords: 2nd-opinion
Focuses: ui, accessibility, administration Cc:

Description

Hey guys,
In the classic Editor when you were adding a post, you already had the button to add another one on the same screen and it speeds up the process a lot, please bring it back! (in red: add new)https://prnt.sc/tpkyp8

Attachments (1)

download.png (127.1 KB) - added by welitonmartins 4 years ago.

Download all attachments as: .zip

Change History (12)

#1 @SergeyBiryukov
4 years ago

  • Component changed from Posts, Post Types to Editor
  • Focuses performance removed
  • Keywords needs-dev-note removed

#2 @afercia
4 years ago

Noting that there is a "New" button in the WordPress admin bar but now the block editor default mode is "full screen" so the admin bar is hidden by default. See:

Fullscreen mode enabled by default in the editor
https://make.wordpress.org/core/2020/03/03/fullscreen-mode-enabled-by-default-in-the-editor/

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


4 years ago

This ticket was mentioned in Slack in #accessibility by audrasjb. View the logs.


4 years ago

#5 @audrasjb
4 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to 5.6
  • Owner set to audrasjb
  • Status changed from new to accepted
  • Type changed from feature request to defect (bug)

Hello, welcome to WordPress Core Trac and thanks for the ticket,

As per today's accessibility bugs scrub, we agreed to milestone this to WP 5.6 as it is clearly a regression.

"Add new" button is necessary for various context like:

  • bulk publish posts
  • open a draft or an already published post, then create a new one
  • create a new post (in a new tab) while already editing one post
  • etc…

Self assigning the ticket to ensure it is fixed upstream in the editor GitHub repository.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


4 years ago

#7 @hellofromTonya
4 years ago

Capturing notes from today's Accessibility meeting.

Next steps:

@audrasjb will:

  • open an upstream ticket in the Gutenberg GitHub repo
  • then close this ticket as "reported upstream"

This ticket was mentioned in Slack in #accessibility by audrasjb. View the logs.


4 years ago

#9 @audrasjb
4 years ago

  • Keywords needs-patch removed
  • Milestone changed from 5.6 to Future Release

Moving this one to next release(s) as it still needs to be fixed upstream.

#10 @welitonmartins
3 years ago

  • Keywords 2nd-opinion added; needs-design removed
  • Type changed from defect (bug) to feature request

Hey, how are u guys?
have some news about that? 🥺

is there any hook to add buttons on that part of the page?

#11 @sabernhardt
19 months ago

The Gutenberg repository has a few related issues:

  • GB32099 added a button at the end of the Pre-Publish Check panel.
  • GB25368 requested guidance to add a button on the opposite side.
Note: See TracTickets for help on using tickets.