WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 8 months ago

#17607 assigned defect (bug)

Google blog search API shutdown

Reported by: jcnetsys Owned by: westi
Priority: normal Milestone: Future Release
Component: Administration Version: 3.2
Severity: normal Keywords: has-patch
Cc: ocean90, info@…, aaroncampbell, mdhansen@…

Description

I have done a search and can't see that this has already been reported.

On the wordpresss dashboard the 'incoming link search' uses google blog search API. Google has announced that this api is being shutdown as of effect 26 May 2011 (http://code.google.com/apis/blogsearch/). It will continue to work but with limited functionality (due to their deprecation policy). I therefore suggest that this be removed or use a different API.

Attachments (2)

17607.diff (6.1 KB) - added by ryan 18 months ago.
Remove Incoming Links widget
17607.2.diff (7.3 KB) - added by aaroncampbell 16 months ago.

Download all attachments as: .zip

Change History (19)

comment:1 ramoonus2 years ago

  • Component changed from General to External Libraries

comment:2 ocean902 years ago

  • Cc ocean90 added

comment:3 duck_2 years ago

I saw this. However, as far as I understand it, it is the Javascript interface that is deprecated and will be disappearing, but not the blogsearch service as used by WordPress.

comment:4 scribu2 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Yeah, the Blog Search API (JavaScript) is deprecated, not the Blog Search Service (RSS).

comment:5 toscho2 years ago

  • Cc info@… added

We could change the default URI nonetheless. The Google blog search was never really good: very limited results, too much spam, and sometimes the feed is just not available (had this on two blogs in the last four weeks).

I’m using icerocket.com now everywhere which finds usually more blog links than Google.

Example:

http://www.icerocket.com/search?tab=blog&q=link%3Awordpress.org&rss=1

comment:6 scribu2 years ago

Looks nice, but would it be able to serve 14% of the internet? :)

Last edited 2 years ago by scribu (previous) (diff)

comment:7 westi2 years ago

  • Component changed from External Libraries to Administration
  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Version set to 3.2

Re-opening for further investigation.

Although the announcement only mentions the JavaScript API there are quite a few issues being reported with the feeds too.

comment:8 westi2 years ago

  • Owner set to westi
  • Status changed from reopened to assigned

comment:9 westi2 years ago

  • Milestone set to Awaiting Review

comment:10 nacin2 years ago

  • Milestone changed from Awaiting Review to 3.2
  • Priority changed from normal to high

So we don't ship with this.

comment:11 aaroncampbell2 years ago

It looks to me like the JavaScript API is the only thing affected here and we don't use it. I'm all for leaving this as-is in 3.2 and looking to remove all default feeds from the dashboard in 3.3.

comment:12 nacin2 years ago

  • Milestone changed from 3.2 to Future Release

comment:13 seolife20 months ago

Nothing.

Last edited 20 months ago by ocean90 (previous) (diff)

ryan18 months ago

Remove Incoming Links widget

comment:14 edward mindreantre16 months ago

Is there a reason for having an incoming links widget (1) that isn't under Wordpress' control - meaning it can be shut down at will - and (2) at all?

Just takes more time to load up the dashboard completely by having such a widget, I figures.

aaroncampbell16 months ago

comment:15 aaroncampbell16 months ago

  • Cc aaroncampbell added

I'm all for removing this and letting plugins implement similar widgets for other services. As such, 17607.2.diff is just a refresh of Ryan's patch.

comment:16 scribu16 months ago

  • Keywords has-patch added
  • Priority changed from high to normal

comment:17 MikeHansenMe8 months ago

  • Cc mdhansen@… added

+1 for moving this to a plugin.

Note: See TracTickets for help on using tickets.