Feature Requests & Voting: setup and help

Upload and install mprfeaturerequest in Modules > Module Manager. Open Configure, then use Improve > Feature Requests > Settings > Configuration for the settings form. The module also provides Dashboard and Requests, with Integrity, License, Support, and Update under Settings.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.

The product tab supports legacy hooks and displayProductExtraContent.

Installation creates request, localized request-content, content invalidation, vote, and comment tables with the shop database prefix. It also installs configuration and admin infrastructure. There is no separate cron command required for basic submissions and voting.

For a moderated guest-submission board, leave Require Login to Submit off and Require Admin Approval on. For customer-only submission, turn the login setting on.

Voting

Each new public submission is created with one automatic submitter vote. Allow Guest Voting controls later guest voting; it does not prevent the initial automatic vote on an accepted guest submission.

Display

Notifications

Notify Admin on New Request defaults to Yes. Admin Email defaults to empty, with a form hint to use the shop email. New requests do not trigger email notifications. Review Requests directly.

Save the form after changing settings. Most settings are shared across all shops. The Where to show feature requests setting under Display is an exception: select a single shop, then choose Own pages (the default) for the dedicated request pages or Module help for the module help page provided by Product Tabs. If a suitable help page is unavailable, the dedicated request pages are used. This location is saved per shop.

Open Feature Requests > Requests. You can filter, export, edit, delete, and apply bulk status changes. The statuses are:

Change a moderated request from Submitted to Under Review or another public status to publish it. Put a public reply in Admin Note. Keep private material out of that field.

The editor includes multilingual Title and Description, customer details, votes, and status. When creating an entry, select Product and Source language. For existing entries, Correct customer source content explicitly applies a source correction while preserving the original. Reviewed against current source marks a translation reviewed. Delete translation removes a selected non-source translation. Reload an editor that reports a revision conflict before resubmitting changes.

The storefront prefers a reviewed translation matching the current source. It falls back to source content, or eligible default-language recovery content, when a current translation is unavailable.

Open a product's Feature Requests tab. The browser supports votes, newest, and status ordering, plus status filtering and pagination. The form and browser have full-page paths as well as fragment/AJAX interactions. Do not depend on the old modal-only or Load more-only workflow.

Submit a test with a title of 5 to 255 characters and a description of 10 to 2000 characters. A guest must also supply a valid name and email. The name limit is 128 characters. Submission is limited to three requests per product, shop, and IP during the last 24 hours.

1. Submit a request with approval required.
2. Confirm it appears in the admin Requests list.
3. Check that it is hidden in an unrelated browser. A guest sees their own submission only with the submission receipt; sharing an IP address does not give access.
4. Change it to Under Review and add an Admin Note.
5. Verify the public list, vote behavior, and response display.
6. Test voting as both a signed-in customer and a guest with your chosen settings.

Default English routes are:

/feature-requests
/feature-requests/page/{page}
/feature-requests/{request-slug}
/feature-requests/module/{product-slug}
/feature-requests/module/{product-slug}/page/{page}

Included prefixes are feature-requests for English, funktionswuensche for German, demandes-de-fonctionnalites for French, propozycje-funkcji for Polish, richieste-funzionalita for Italian, and solicitudes-de-funciones for Spanish. Use generated links for language and shop prefixes.

The gSitemapAppendUrls entry uses priority 0.5, weekly change frequency, and the latest public update or current time. Verify it in your actual sitemap generator.

Theme override paths include:

themes/your-theme/modules/mprfeaturerequest/views/templates/hook/product-requests.tpl
themes/your-theme/modules/mprfeaturerequest/views/templates/hook/request-item.tpl
themes/your-theme/modules/mprfeaturerequest/views/templates/front/roadmap.tpl
themes/your-theme/modules/mprfeaturerequest/views/templates/front/detail.tpl
themes/your-theme/modules/mprfeaturerequest/views/templates/front/module-requests.tpl

Use .mprfr-container, .mprfr-status-badge, .mprfr-item__admin-note, and .mprfr-dashboard__pill for theme CSS changes after checking the rendered element.

If a request is missing, check its status, product, shop, enabled settings, and owner receipt. If submission fails, check field lengths, the daily limit, and the security-token error; refresh the form before retrying. A Content was saved. Cache refresh is pending; do not submit again. response means the submission succeeded. Review the existing entry instead of creating a duplicate.

Use Integrity for schema and infrastructure failures. Submitting a request does not send an email. This module is a request board; use your support process for urgent store faults.

Export any requests you need before uninstalling. Uninstall removes configuration, admin preferences and menus, theme registration, and module-owned schema tables, including request content, votes, and comments. Disabling the module is the reversible option when you need to retain the installed data.