Last modified: 2012-04-14 12:51:12 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 T26169, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24169 - Create an __NOINDEX__ equivalent to prevent indexing by internal search engine
Create an __NOINDEX__ equivalent to prevent indexing by internal search engine
Status: RESOLVED DUPLICATE of bug 22251
Product: MediaWiki
Classification: Unclassified
Search (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-28 21:13 UTC by Stig Meireles Johansen
Modified: 2012-04-14 12:51 UTC (History)
5 users (show)

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


Attachments

Description Stig Meireles Johansen 2010-06-28 21:13:38 UTC
Shouldn't Lucene-search also respect the __NOINDEX__ tag? If not, there should exist another magic word to stop certain pages from being indexed and searchable. Alternatively a "robots.txt" file (maybe a better solution to be able to restrict this exclusion-feature to admins only) in the MediaWiki-namespace should be consulted.
Comment 1 Stig Meireles Johansen 2010-12-04 12:36:23 UTC
Bump
Comment 2 Helder 2011-03-26 00:28:40 UTC
Bump[2]
Comment 3 Bawolff (Brian Wolff) 2011-03-26 00:33:03 UTC
__NOINDEX__ is primarily to stop google et al. from finding it. If this was to be implemented, I would say it should have a different magic word (or at the very least a config option).

Changing component to search, because if this was to be implemented, it should prevent indexing on any of mediawiki's internal search backends, not just lucene. (not 100% sure compoenent change is right. please revert if not)
Comment 4 Robert Stojnic 2011-03-26 00:34:36 UTC
What is a rationale for a change like this? Why should we have content that cannot be found in any way except from direct link?
Comment 5 Stig Meireles Johansen 2011-03-26 07:33:07 UTC
Well, one use-case would be in situations like this:
http://no.wikipedia.org/wiki/Wikipedia:Statistikk/1000_mest_bes%C3%B8kte
where we have a large collection of pages with potential searchwords and we don't want to create a new ns...
Comment 6 Rd232 2012-03-17 10:48:30 UTC

*** This bug has been marked as a duplicate of bug 22251 ***
Comment 7 Bachsau 2012-04-14 12:51:12 UTC
I wouldn't want a new magic word. May a config option, if __NOINDEX__ should also apply to internal search would do.

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


Navigation
Links