WordPress.org

Make WordPress Core

Opened 8 months ago

Closed 8 months ago

Last modified 5 months ago

#46724 closed enhancement (wontfix)

Site Health: Copy site info to clipboard should include siteurl and home

Reported by: knutsp Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.2
Component: Site Health Keywords: site-health
Focuses: Cc:
PR Number:

Description

When viewing this info at the site, it's unnecessary, but when posting/pasting this outside of the site context it's missing, but relevant.

Include these options, Site URL and Home URL at the top.

Change History (9)

#1 @Clorith
8 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

This information has intentionally been marked as private because any posting on public forums leads to extra work when users return later for reasons such as "If I google my website it shows this page" and similar.

Places such as the WordPress.org support forums have a separate input field for site URLs, and most support contact forms i have seen to date also do it that way, so we'll make the educated guess that this is not information we need to include.

Because of the above, this is not something we will be changing.

#2 @knutsp
8 months ago

  • Keywords 2nd-opinion added
  • Resolution wontfix deleted
  • Status changed from closed to reopened

This should not just be intended for pasting to public support forums. If this information is not wanted the user may cut it out after pasting.

This is needed for general support requests, to avoid misunderstandings and confusion.

Reopening for 2nd opinions.

#3 @SergeyBiryukov
8 months ago

  • Milestone set to Awaiting Review

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


8 months ago

#5 @audrasjb
8 months ago

  • Keywords close added; 2nd-opinion removed

I agree with @Clorith this information should remain private by default.

It's better to ask directly for this information if really needed than to ask users to remember to cut it out before pasting the text on forums :-)

#6 @xkon
8 months ago

Coming from a support team perspective myself there's always an extra field for marking a website (if not already in the members details) that is private/optinal. So usually that's taken care of from the get-go of a report.

I'm leaning towards leaving this as is and not including the addresses on the report itself, that aspect can be handled by other means (that are usually meant to stay private or optional) or even by the users themselves if they feel like adding their site openly on a post.

#7 @JarretC
8 months ago

Maybe not have it by default but have an option they can select to include that information in the report? As the Site URL and Home URL can both have different settings which may explain an issue a user is having, offering the option to have them provide that information initially and potentially resolving their issue quicker is better than asking them to go back and get more information.

I would still vote for @knutsp idea though and have it added initially. The report results are indeed not specific to the .org support forums and this information could be provided to anybody attempting to provide support for a user.

#8 @Clorith
8 months ago

  • Keywords close removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

I've yet to see a support form for a plugin/theme that doesn't have a site url field separate from all other fields, so this feels like a non-issue.

There's no harm in asking for more information if cases where it's needed, it even gives the users a feeling of doing something and being a part of working out the solution. This is a positive experience to many.

With both a 2nd and 3rd opinion also favoring keeping this private, I'm re-closing. If, post-release, we get feedback to the contrary, this is something that can be revisited at that time.

#9 @spacedmonkey
5 months ago

  • Component changed from Administration to Site Health
Note: See TracTickets for help on using tickets.