Module Positions vs REST API Enabler — WordPress

Module Positions vs REST API Enabler

Name: Module Positions
Rating: 5 (5 reviews)

Side-by-side comparison · 24 data points

Module Positions

5.0·5reviews·90+installs

wordpress

Change

1. Listing metadata

Field-level data

	Module Positions	REST API Enabler
Tagline	—	—
Description	2016 / 5000 chars40% used	1803 / 5000 chars36% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer		Mickey Kay
Listed	—	—
Last updated	—	—

2. Categories & rankings

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

Module Positions

REST API Enabler

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Module Positions and REST API Enabler
Metric	Module Positions	REST API Enabler
Rating	5.0 ★	5.0 ★
Total reviews	★ 5	3
Active installs	90+	200+
Free plan	—	—

3. App details

Long-form description · keyword frequency

Module Positions

What does it do? If you have a site with multiple subpages, you might have some positions in your template where you probably want to manage individual content (like a sidebar, a footer, a banner or whatever). The WordPress widgets can display content in specific widget-positions, but you can’t tell WordPress to only display your content on a certain page – That’s where my plugin comes in. You can create different module positions, assign content and choose on which pages it will be shown. If you use WordPress as a CMS, this will be very helpful. Create Module Positions First, you can create different module positions. Rename these as you want. To put a module position in your template you can easily copy & paste the shortcode right next to the positions’s name. if you have already created content, you can drag and drop these around to change their order. Create Content Now, you can create content for your module positions. You can choose on which pages, categories or posts your content will be displayed. For this information your custom menus will be loaded (which are defined in your template). If there are categories with posts in your custom menu, click the “+”-button to show them. You also can choose on which posts your content will be displayed here. Define your HTML-markup In the little metabox on the right side, you can simply define your HTML-markup. Try writing {{post_content}} for your content and {{post_title}} for your title – A list of all values can be found here. To reset your markup just click on “Reset”, that will load the standard markup (which can be changed on the settings page). Settings Change your standard HTML-markup. If you click on “Reset” in your moduleposition-posts, this will be loaded. Change the order of posts in the drop-down menus of your categories. That may be useful if you have a lot of posts in a category and you want to find a special post. Missing something? Send me an e-mail! I’m open to new ideas! Write me: [email protected]

Top keywords

content11×3.15%
positions6×1.72%
module5×1.43%
posts5×1.43%
module positions4×1.15%
categories3×0.86%
change3×0.86%
choose3×0.86%
click3×0.86%
html-markup3×0.86%
post3×0.86%
reset3×0.86%

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%

Frequently asked

Common questions about this comparison

Which has better reviews, Module Positions or REST API Enabler?

Module Positions (5.0★, 5 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 Module Positions or REST API Enabler?

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

Which is faster to set up, Module Positions or REST API Enabler?

Both apps are one-click installs from the WordPress Plugin Directory. Module Positions has the deeper published review base (5 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?

Module Positions typically suits early-stage and growth-mode teams based on its published review base (5 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 Module Positions and REST API Enabler?

Migration support varies by app and category. Module Positions 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.

Module Positions vs REST API Enabler

Module Positions

1. Listing metadata

2. Categories & rankings

REST API Enabler

At a glance

AppRanks verdict

3. App details

Frequently asked

Which has better reviews, Module Positions or REST API Enabler?

Should I choose Module Positions or REST API Enabler?

Which is faster to set up, Module Positions or REST API Enabler?

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

Can I migrate data between Module Positions and REST API Enabler?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons