Comparison · generated on request
Disable XML-RPC vs Content XLerator WP Public Plugin
Both plugins as this registry currently observes them. Figures come from the same daily snapshot, so they are directly comparable, which two separate wordpress.org pages, read minutes apart, are not.
| Disable XML-RPC | Content XLerator WP Public Plugin | |
|---|---|---|
| What it does | Disables the XML-RPC API in WordPress 3.5+, which is enabled by default. | Custom integration with cxl1.net Manage notification and display settings for posts received via xmlrpc. Custom forms for submitting content to the wp … |
| Active installs | 200,000+ | fewer than 10 |
| Rating | 4.2★ (33) | — |
| Last release | 3 months ago | 10 years ago |
| Current owner | Phil Erb | yipeecaiey |
| Added to directory | 28 Sep 2012 | 12 Jan 2011 |
| Tested up to | WP 7.0.4 | WP 4.3.34 |
| Requires PHP | false | false |
Install figures are rounded by WordPress.org to one significant digit, so a gap smaller than a band step is not a difference. Nothing here ranks the two plugins or recommends either, and no link on this page earns anything.
Why this page is not in search results
There are roughly 1.8 billion possible pairs of WordPress plugins. Generating them would be scaled content abuse, so this registry does not: a comparison renders for anyone who asks for it, and is offered to search engines only once 25 different people have asked for that same pair within 60 days. This one has been requested by 0. Until it crosses, the page works normally but stays out of the index.
Records: Disable XML-RPC · Content XLerator WP Public Plugin