Making WordPress.org

Opened 4 years ago

Closed 20 months ago

#1304 closed enhancement (fixed)

Update plugins_api to accept multiple slugs when querying 'plugin_information'

Reported by: DJPaul Owned by:
Milestone: Priority: normal
Component: API Keywords: needs-patch

Description (last modified by netweb)

Migrated from https://core.trac.wordpress.org/ticket/20002

When querying plugins_api() with 'plugin_information', the second argument takes a parameter 'slug' on which to find the plugin. Please may the API be updated to optionally accept an array of slugs, so that you can query for multiple plugins in the same HTTP request?

Change History (10)

#1 @netweb
4 years ago

  • Description modified (diff)
  • Reporter changed from chriscct7 to DJPaul

Restored original ticket formatting for improved readability.

#3 @SergeyBiryukov
4 years ago

  • Component changed from Plugin Directory to api.wordpress.org

#6 follow-up: @obenland
20 months ago

@dd32 Would this be something for v1.2?

#7 in reply to: ↑ 6 @dd32
20 months ago

Replying to obenland:

@dd32 Would this be something for v1.2?

It'll probably require a few more changes, but I'll have a look into it as it'll be a good performance boost for Core.

#8 @dd32
20 months ago

In 6484:

Theme Directory: API: Allow for querying multiple themes on the theme_information action through the 'slugs' parameter.

Example: https://api.wordpress.org/themes/info/1.2/?action=theme_information&request[slugs][]=twentyten&request[slugs][]=twentyeleven

See #1304

#9 @dd32
20 months ago

In 6485:

Plugin Directory: API: Allow for querying multiple plugins on the plugin_information action through the 'slugs' parameter.

Example: https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slugs][]=hello-dolly&request[slugs][]=wordpress-importer

See #1304

#10 @dd32
20 months ago

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

Turned out core doesn't actually need this functionality anymore, as the problematic calls were removed recently (I missed that).

I'm going to leave this here as-is for now, with a note that it might change in the future.

Note: See TracTickets for help on using tickets.