Add template/active_plugins to wp.getOptions

[koke]

active_plugins could be very useful to warn users about known compatibility issues between specific plugins and the apps using XML-RPC

template is not as useful, but could be interesting to know, for instance, which blogs are P2s and which are "regular" blogs

[josephscott]

Looks good, I'd be fine with committing this.

[nacin]

If you would like to know template, you should probably also receive stylesheet.

[ericmann]

Refresh patch to match latest version of trunk.

[ericmann]

Replying to nacin:

If you would like to know template, you should probably also receive stylesheet.

Agreed.

[nacin]

I wonder how useful active_plugins will actually be — a serialized array of filenames doesn't really lend to which plugins are necessarily active on a blog. I'd almost rather provide plugin names, so you're matching against "Akismet" rather than "akismet/akismet.php". Perhaps not. Just thinking aloud.

[nacin]

In [20073]:

Add template and stylesheet to readonly options that can be pulled from XML-RPC. props koke, ericmann. see #17132.

[westi]

Replying to nacin:

I wonder how useful active_plugins will actually be — a serialized array of filenames doesn't really lend to which plugins are necessarily active on a blog. I'd almost rather provide plugin names, so you're matching against "Akismet" rather than "akismet/akismet.php". Perhaps not. Just thinking aloud.

I think we need to provide something normalised for this to be useful rather than exposing raw data.

@koke please can you open a new ticket for exposing plugin info.

Closing this as fixed in 3.4 - for the template/stylesheet info.