Last modified: 2011-04-14 20:19:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T28118, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26118 - Shouldn't let any Thread to be indexed when __NOINDEX__ is added to the introduction (header) of a page
Shouldn't let any Thread to be indexed when __NOINDEX__ is added to the intro...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 17004
  Show dependency treegraph
Reported: 2010-11-25 12:39 UTC by Helder
Modified: 2011-04-14 20:19 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Helder 2010-11-25 12:39:56 UTC
Currently, even if a user add __NOINDEX__ to its talkpage, all threads created on it are *still indexed* by search engines, since the extension creates each commont in a different page (where the user can only add the magic word *after* the topic was created). The same happens for other pages (not only user talk pages).

For privacy reasons, this shouldn't happen. Especifically, the users should *not* be requested to add __NOINDEX__ to zillions of comments in order to get all of them not being indexed.
Comment 1 db [inactive,noenotif] 2010-11-27 20:56:17 UTC
__NOINDEX__ is stored in pageprops table, so this is not complex, I think.
Comment 2 Mark A. Hershberger 2011-04-14 20:19:18 UTC
changing priority since LQT is being completely rewritten.

Note You need to log in before you can comment on or make changes to this bug.