Private by Default vs REST API Enabler — WordPress

Private by Default vs REST API Enabler

Name: Private by Default
Rating: 5 (4 reviews)

Side-by-side comparison · 24 data points

Private by Default

5.0·4reviews·50+installs

wordpress

Change

1. Listing metadata

Field-level data

	Private by Default	REST API Enabler
Tagline	—	—
Description	406 / 5000 chars8% used	1803 / 5000 chars36% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	anttti	Mickey Kay
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

Private by Default

REST API Enabler

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Private by Default and REST API Enabler
Metric	Private by Default	REST API Enabler
Rating	5.0 ★	5.0 ★
Total reviews	★ 4	3
Active installs	50+	200+
Free plan	—	—

3. App details

Long-form description · keyword frequency

Private by Default

When creating new posts or pages (of regular WordPress types or custom post types), this plugin makes them private by default. Just activate the plugin, no further configuration is necessary (or even possible). This plugin is a fork of the Private Posts by Default plugin since it didn’t work properly in WordPress 4.3 and wasn’t updated in more than three years. Important URL’s Author’s Blog Twitter

Top keywords

default2×2.82%
posts2×2.82%
private2×2.82%
types2×2.82%
wordpress2×2.82%

REST API Enabler

Like this plugin? Please consider leaving a 5-star review. By default, custom post types and custom fields are not accessible via the WordPress REST API. REST API Enabler allows you to: Enable the WP REST API for custom post types and specify WP REST API custom endpoints. Choose which custom fields to include in WP REST API responses for posts, pages, and custom post types. All enabled custom field data is included in the REST API response, nested under the rest_api_enabler key, like so: [ { "id": 179, "date": "2016-07-03T18:06:50", "title": { "rendered": "Test Job" }, . . . "rest_api_enabler": { "custom_meta_1": "Value 1", "custom_meta_2": "Value 2", "custom_meta_3": [ "Array value 1", "Array value 2" ] } } ] Note: prior to verion 1.1.0, all meta keys were included as top-level keys in the API response. Additionally, all values were returned as arrays, regardless of whether the original value was actually an array. This functionality is now deprecated as it risks key-name collisions. Please reference the rest_api_enabler top-level key instead. Usage Activate the plugin, then go to Settings → REST API Enabler in the admin. Click the Post Types tab to enable/disable post types and customize their endpoints. Click the Post Meta tab to enable/disable post meta (custom fields). NOTE: by default, the plugin does not display settings for protected post meta (post meta that begins with an underscore and is intended for internal use only). If you wish to include protected post meta in the plugin settings, you can use the rae_include_protected_meta filter to do so. The following code can be placed in your theme’s functions.php file, or in a custom plugin (on init priority 10 or earlier): add_filter( 'rae_include_protected_meta', '__return_true' );

Top keywords

custom12×4.03%
api11×3.69%
meta10×3.36%
post10×3.36%
rest10×3.36%
rest api10×3.36%
api enabler5×1.68%
enabler5×1.68%
post meta5×1.68%
post types5×1.68%
rest api enabler5×1.68%
types5×1.68%

Frequently asked

Common questions about this comparison

Which has better reviews, Private by Default or REST API Enabler?

Private by Default (5.0★, 4 reviews) and REST API Enabler (5.0★, 3 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.

Should I choose Private by Default or REST API Enabler?

AppRanks cannot separate these two on rating — both sit at 5.0★. Private by Default does carry the larger published review base (4 vs 3). Read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Private by Default or REST API Enabler?

Both apps are one-click installs from the WordPress Plugin Directory. Private by Default has the deeper published review base (4 vs 3), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

Private by Default typically suits early-stage and growth-mode teams based on its published review base (4 reviews). REST API Enabler typically suits early-stage and growth-mode teams based on its published review base (3 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between Private by Default and REST API Enabler?

Migration support varies by app and category. Private by Default and REST API Enabler both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from REST API Enabler" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

Private by Default vs REST API Enabler

Private by Default

1. Listing metadata

2. Categories & rankings

REST API Enabler

At a glance

AppRanks verdict

3. App details

Frequently asked

Which has better reviews, Private by Default or REST API Enabler?

Should I choose Private by Default or REST API Enabler?

Which is faster to set up, Private by Default or REST API Enabler?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between Private by Default and REST API Enabler?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons