WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#44670 closed enhancement (maybelater)

Try Gutenberg: Link to the demo site when the current user has no other action they can take

Reported by: pento Owned by: pento
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-patch
Focuses: Cc:

Description

To avoid the situation where the Try Gutenberg callout can show without an action for the user to take, we can fall back to linking to https://wordpress.org/gutenberg/, where they can try a live demo of the block editor.

The meta team are currently building this out on a test page, they're expecting to switch it over tomorrow.

Attachments (1)

44670.diff (549 bytes) - added by pento 2 years ago.

Download all attachments as: .zip

Change History (9)

@pento
2 years ago

#1 @danieltj
2 years ago

  • Keywords 2nd-opinion added

Following on from #41316, the Try Gutenberg callout seriously shouldn't be shown to anyone unless they have either edit_posts capabilities or the install_plugins capability. This hasn't been thought through from an agency point of view where clients will be confused and not understand what Gutenberg really is.

Linking them to a page on WordPress.org with more information will continue the confusion because it won't give them anymore useful information if they're not in a position to actually use it. I understand that generally, the Gutenberg team want more people using it, but this is a forceful decision to show what is basically an advert to users where it's not needed.

Please, don't add the callout to the dashboard for everyone, do a capabilities check and show it only to people who can act upon it. The current way of dealing with this is less than ideal, especially for agencies with lots of active sites to maintain.

I understand there is a plugin with some options to disable, but another plugin on top of the Classic Editor/Gutenberg Ramp is getting ridiculous and shouldn't have to be the case here.

Last edited 2 years ago by danieltj (previous) (diff)

#2 follow-up: @pento
2 years ago

I understand there is a plugin with some options to disable, but another plugin on top of the Classic Editor/Gutenberg Ramp is getting ridiculous and shouldn't have to be the case here.

Classic Editor already removes the callout, and Ramp is looking at adding something similar. You don't need to install additional plugins.

This ticket was mentioned in Slack in #core by pento. View the logs.


2 years ago

#4 in reply to: ↑ 2 @danieltj
2 years ago

Replying to pento:

[...] You don't need to install additional plugins.

You do if you want to remove the callout but haven't got the Classic Editor installed. Either way, having a plugin to remove the callout is extra work where it's not necessary.

I'd be totally fine as is, if the callout only showed to certain admin-esque users, but showing it to everyone in my opinion would create confusion amongst clients who might not ever need/want to use Gutenberg.

Only people with the capability to install/active plugins and create/edit posts can use Gutenberg, so even if a link was provided to see the Gutenberg page, once a person is done with that, they might not have their own site to do anything else on, so providing a fallback here is not the solution.

This ticket was mentioned in Slack in #core by pbiron. View the logs.


2 years ago

This ticket was mentioned in Slack in #core by pbiron. View the logs.


2 years ago

#7 @pento
2 years ago

  • Keywords 2nd-opinion removed
  • Milestone 4.9.8 deleted
  • Resolution set to maybelater
  • Status changed from assigned to closed

Maybe we'll do this later. Maybe we won't. 🙂

This ticket was mentioned in Slack in #core by danieltj. View the logs.


2 years ago

Note: See TracTickets for help on using tickets.