by Cornel Raiu 1 (0 reviews)

Feature Request System

Name: Feature Request System
Author: Cornel Raiu

Collect feature requests, let people vote, and email everyone who follows a request when its status changes.

Feature Request System ranks #62,299 among WordPress.org plugins with 1+ active installations, is #1,790 of 2,802 in the Contact Forms category, a 1/5 rating from 0 reviews, and was last updated Oct 20, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.0 Current Version v1.0.0

Updated 1 week ago Last Update on 20 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#1,790 of 2,802 in Contact Forms Downloads -74.3% this week Actively maintained

View on WordPress.org

Rank

#62,299

— No change

Active Installs

— No change

KW Avg Position

153

— No change

Downloads

197

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

49,362

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 8 more installs to reach 10+

Rank Changes

Current #62,299

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Oct 20, 2026
Requires WP: 6.6+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: Cornel Raiu

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

feature requests feedback ideas roadmap voting

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

5M+ installs

Jetpack – AI Agents & MCP, Security, Backup & Analytics

3M+ installs

#17

MC4WP: Mailchimp for WordPress

1M+ installs

#35

Hostinger Reach – AI-Powered Email Marketing for WordPress

Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

800K+ installs

#81

Joinchat – Enhanced “click to chat”

700K+ installs

#89

View all Contact-forms plugins

Frequently Asked Questions

Common questions about Feature Request System

The board and the form are built for any theme. Block themes and classic themes are both supported.

Not by default. Each board has a setting for who can suggest features: everyone, logged-in users, or nobody. Change it under Feature Requests → Boards. Visitors without an account can leave their name and email, and those are never shown publicly.

Status emails go out five minutes after the last change, so that a status picked by mistake can be corrected first. They are sent in the background by WordPress's scheduled tasks, which run when someone visits the site. On a site with few visitors that can take a little longer. The user who changes the status gets no email about their own change.

It belongs to Action Scheduler, the library this plugin uses to send emails in the background. WooCommerce and many other plugins use it too. The screen lists the emails that wait to be sent and those that were, under the group feature-request-system.

Each email carries the headers that mail programs such as Gmail use for that button, and using it stops the emails about that request. Mail programs rely on those headers only for mail that is sent through SMTP or a mail service and signed by your domain. With PHP's built-in mail function, which WordPress uses unless you set up something else, the button may not appear. The link at the end of the email works in every case.

Yes. Each site of the network has its own boards, requests, votes and settings. Deleting the plugin removes the data of every site that has "Delete all requests…" ticked. On a network, "logged-in users" means the users of the whole network, as it does for comments in WordPress. A user who is removed from a site no longer follows requests there.

WordPress turns a web address on a line of its own into a video player or a preview. In feature requests the plugin turns that off, because the text comes from your visitors: your server would fetch whatever address they typed, and everyone who opens the request would load content from that site. A moderator who wants a video in a request can wrap its address in WordPress's embed shortcode: [embed]https://example.com/video[/embed]. Visitors cannot use shortcodes.

The limits for each IP address use the address your server sees. Most hosts pass on the visitor's address. If your server sees the address of the proxy instead, all visitors count as one, and a busy board can reach the limit for everyone. In that case, tell the plugin which header holds the visitor's address, from your theme or a small plugin. For Cloudflare: add_filter( 'mwtfrs_client_ip', function ( $ip ) { return isset( $_SERVER['HTTP_CF_CONNECTING_IP'] ) ? $_SERVER['HTTP_CF_CONNECTING_IP'] : $ip; } ); Only do this when every request reaches your server through that proxy, because anyone can send such a header. The vote limits themselves are under Feature Requests → Settings, and every limit can be changed with the mwtfrs_rate_limit filter.

They share one IP address, and by default 60 votes an hour can come from the logged-in users at one address. Raise "Logged-in users" under Feature Requests → Settings → Vote limits. Each user can still vote only once for a request, and 30 times an hour.

With WP-CLI, wp mwtfrs seed creates 30 sample requests with votes, and wp mwtfrs seed --delete removes them again. wp mwtfrs seed --requests=1000 --votes=50000 creates a large board to test with. wp mwtfrs recount recounts every request's votes.