| 2009-03-03 13:41:33 |
Abel Deuring |
bug |
|
|
added bug |
| 2009-03-09 21:42:20 |
Diogo Matsubara |
launchpad: bugtargetdisplayname |
Launchpad itself |
Launchpad Registry |
|
| 2009-03-09 21:42:20 |
Diogo Matsubara |
launchpad: bugtargetname |
launchpad |
launchpad-registry |
|
| 2009-03-09 21:42:20 |
Diogo Matsubara |
launchpad: statusexplanation |
|
|
|
| 2009-03-09 21:42:20 |
Diogo Matsubara |
launchpad: title |
Bug #337216 in Launchpad itself: "full text searches include result pages from deactivated projects" |
Bug #337216 in Launchpad Registry: "full text searches include result pages from deactivated projects" |
|
| 2009-03-10 17:07:54 |
Curtis Hovey |
launchpad-registry: status |
New |
Triaged |
|
| 2009-03-10 17:07:54 |
Curtis Hovey |
launchpad-registry: importance |
Undecided |
Low |
|
| 2009-03-10 17:07:54 |
Curtis Hovey |
launchpad-registry: statusexplanation |
|
As I stated before this bug was reported, the problem is really upstream. Google's catalog can take a few weeks to update. The data will correct itself.
We can consider reparsing Google's data to attempt to locate the pillar or person and purge the items if the entity is deactivated. That can be costly to lookup, and break batching. Unless there is a better solution I'm not inclined to address this. |
|
| 2009-06-15 19:22:15 |
Curtis Hovey |
summary |
full text searches include result pages from deactivated projects |
full text searches include result pages that are broken links |
|
| 2010-11-12 04:45:24 |
Curtis Hovey |
tags |
registry-projects search |
search |
|
