#12211 closed feature request (fixed)
Make it obvious when a blog is set to private
Reported by: | markjaquith | Owned by: | |
---|---|---|---|
Milestone: | 3.0 | Priority: | normal |
Severity: | minor | Version: | |
Component: | Administration | Keywords: | has-patch |
Focuses: | Cc: |
Description
I've heard reports of people developing a WordPress theme with privacy mode turned on. When launching it, they can forget to turn the privacy mode back off, with disastrous results in search engines.
We should make some sort of indicator when privacy mode is on. Perhaps a lock icon next to the blog name in the wp-admin h1? Clicking it could lead to the Privacy Options page.
Attachments (7)
Change History (26)
#2
@
15 years ago
I'm +1 on this idea too, But the mouse-over text is going to need to explain that the lock means its Search-engine lockout, not anything else..
#3
@
15 years ago
How about instead of a lock icon that makes people think of SSL, we just do what we do with private posts? In the admin header, next to the site title, add "- Private" in bold letters. Make it clickable to take you to the privacy settings screen, and on hover give tooltip "click to change privacy settings" or some such.
#4
@
15 years ago
I agree the lock could be confused with SSL. On the other hand, private posts require authentication, while privacy mode only deals with search engine access -- the site is very much public. I'm not sure that's any better.
#6
@
15 years ago
I like it. Thanks for adding the title text. The only thing I see is that we'll need to convert site-visit-button from an ID to a class now.
#9
@
15 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Making it a button instead of text is a problem. Buttons are used to indicate potential actions, not current statuses. Yes, there's an action associated with it, but the button breaks the UI convention we're trying to make consistent within WP of only using buttons for actual submit actions, not just for links or displays. Secondly, the contrast of that button is so low that it won't pass accessibility guidelines (same for visit site, we need to fix that too, but that's a separate issue).
Better implementation would be something like:
SiteName - Private [view site button]
or
SiteName (Privacy On) [view site button]
#10
@
15 years ago
Not going to bother with a second commit now then, but we'll want to add another esc_attr there for the other title attribute. Maybe some esc_html too.
Making it a button instead of text is a problem. Buttons are used to indicate potential actions, not current statuses. Yes, there's an action associated with it, but the button breaks the UI convention we're trying to make consistent within WP of only using buttons for actual submit actions, not just for links or displays.
Are you also advocating for View Site to no longer be a button?
#11
@
15 years ago
Wouldn't it be confusing to have SiteName(links to site) - PrivacyNotice(links to privacy options) ViewSiteButton(links to site)?
#14
follow-up:
↓ 15
@
15 years ago
Thanks for the follow-up patch. I touched up the CSS a bit on the way in, and reverted most of [13168] by going back to an id for the Visit Site button.
#15
in reply to:
↑ 14
@
15 years ago
Replying to nacin:
Thanks for the follow-up patch. I touched up the CSS a bit on the way in, and reverted most of [13168] by going back to an id for the Visit Site button.
Oops. Just discovered this open tab with a database locked error, which have been rather prevalent this morning. Figured it was from some recent comment, instead I posted a comment I meant to post two days ago.
#17
@
13 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
- Version set to 3.2
It looks like, with the changes to 3.2 and the header, this got dropped. Can it be put back in?
#18
@
13 years ago
- Resolution set to fixed
- Status changed from reopened to closed
- Version 3.2 deleted
It looks like, with the changes to 3.2 and the header, this got dropped.
Due to screen space I believe it was dropped from the header as it was using valuable space which could otherwise be used better for the majority of users.
It was moved into the Right Now dashboard widget, but doesn't appear to be very obvious there.
As this ticket was closed for 3.0, It'd be better if you could create a new ticket for 3.2 consideration instead, and reference this ticket.
Absolutely +1. Had a client once that managed to turn privacy mode on and then went nuts when the site dropped out of search. I like the lock icon idea.