![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 15 years ago
Closed 14 years ago
#17132 closed task (blessed) (fixed)
Add template/active_plugins to wp.getOptions
| Reported by: | koke | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.4 |
| Component: | XML-RPC | Version: | |
| Severity: | normal | Keywords: | has-patch mobile commit |
| Cc: | Focuses: |
Description
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
Attachments (2)
Change History (11)
#5
follow-up:
↓ 6
@
14 years ago
If you would like to know template, you should probably also receive stylesheet.
#6
in reply to: ↑ 5
@
14 years ago
- Keywords commit added
Replying to nacin:
If you would like to know
template, you should probably also receivestylesheet.
Agreed.
#7
follow-up:
↓ 9
@
14 years ago
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.
#9
in reply to: ↑ 7
@
14 years ago
- Resolution → fixed
- Status new → closed
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.
Looks good, I'd be fine with committing this.