WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#10621 closed enhancement (fixed)

restore default "checked" behavior of blog_public switch in install.php

Reported by: stevejohnson Owned by: westi
Milestone: 2.8.5 Priority: high
Severity: major Version: 2.8
Component: Upgrade/Install Keywords: needs-patch
Focuses: Cc:

Description

http://core.trac.wordpress.org/changeset/10574/trunk/wp-admin/install.php Rev 10574 of install.php changed the default behavior of the 'Allow my blog to appear in search engines...' checkbox from checked to unchecked.

This has caused a lot of problems as evidenced in forum threads such as this one: http://www.warriorforum.com/main-internet-marketing-discussion-forum/114180-starting-new-selfhosted-wordpress-site-read.html at the Warrior Forum.

Repairing this is an easy fix that should be done in 2.8.5.

Change History (8)

comment:1 stevejohnson5 years ago

  • Cc sj@… added

comment:2 westi5 years ago

  • Keywords needs-patch added
  • Owner changed from dd32 to westi
  • Status changed from new to assigned

comment:3 westi5 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [11832]) Restore the default behaviour on install of blogs appearing in search engines. Fixes #10621 for trunk.

comment:4 westi5 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Re-open for 2.8.x branch

comment:5 westi5 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

[11833] fixes this for 2.8.x branch.

comment:6 follow-up: hakre5 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

New setups should respect the users privacy. It is important that users make an active decision to allow robot access to their data. Just as an info regarding this patch which did the opposite. Reading a book about website basics might be insightfull, and twice-thinking before doing a submit because of a misleading comment.

I'm pretty much for reverting this and re-open it to gather some awareness.

comment:7 stevejohnson5 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

"New setups should respect the users privacy."

What privacy? There is no privacy on the web. You put up a website, WP or otherwise, you're expecting people to visit, to be able to find you. I haven't taken it upon myself to do a survey ( have you? ), but I seriously doubt the percentage of WP users who don't want their site to show up in search engines reaches the double digits.

"It is important that users make an active decision to allow robot access to their data."

Tell that to Google. And MSN. And Yahoo. Or any other search engine. Since the beginning, people have had to make an active decision NOT to allow access to their data.

This patch restored WP to expected/prior behavior. There was no discussion on the original change, nor any notes, leading me to believe it was inadvertent.

"Reading a book about website basics might be insightfull, and twice-thinking before doing a submit because of a misleading comment."

Don't presume to lecture me about website 'basics'. I thought more than twice about opening the ticket in the first place. If hiding an install from robots had been default behavior from the beginning, I would have gone about it in a different way.

I'm pretty much for leaving this as-is, with the original default behavior restored. If you think it ought to be something different, open another ticket that discusses why original behavior should be changed against user expectation, why new installs need a net-nanny, and why you think the discussions on this subject across the web are misleading. Maybe you'll gain some awareness as to what BLOGGERS want - which is, I guess not so obviously, to BLOG.

comment:8 in reply to: ↑ 6 westi5 years ago

Replying to hakre:

New setups should respect the users privacy. It is important that users make an active decision to allow robot access to their data. Just as an info regarding this patch which did the opposite. Reading a book about website basics might be insightfull, and twice-thinking before doing a submit because of a misleading comment.

I'm pretty much for reverting this and re-open it to gather some awareness.

This change fixed a bug which we introduced by accident and put the default back to what it was meant to be.

Note: See TracTickets for help on using tickets.