Product Issue Reports: setup and help

Upload and install mprissuesrevolution in Modules > Module Manager. Click Configure or open Improve > Issues. Use the equivalent module upload screen on older PrestaShop versions.

Use Issues to manage records and Settings > Configuration for display, reporting, and indexing options. The Settings area also provides Integrity, License, Support, and Update.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.

Choose the intended shop context before saving. Settings apply to that shop; when no shop-specific value is saved, the global setting applies.

For a read-only public tracker, keep Enable front display on and set Allow users to report issues to No. The module publishes manually reviewed information; it does not automatically detect store bugs.

Create and review issues in the intended shop context. Issue records carry a shop ID, and the public issue queries filter by that shop. Translations belong to their issue record; they do not provide a separate cross-shop publishing control. Save the intended display and reporting settings for each shop, remembering the global configuration fallback described above.

Save your changes. Tab headings can include open and total public counts, such as Known Issues (2/5). Pending reports do not count as public issues.

Open the Issues list and add a record. The list supports filters for product, title, status, severity, source, votes, ETA, active state, and indexable state.

For example, create a high-severity Open issue titled "Checkout button hidden after theme update", enter the affected versions and workaround, and save it as Active. When fixed, change Status to Resolved, fill Fixed in version, and add a Resolution note.

Pending is a moderation state. Only Open, Resolved, Closed, and Won't fix issues can appear publicly. Review a submitted report and change its status before expecting it on the public hub or product tab. Setting Active to No hides even an approved record.

Provide actual localized titles or descriptions. For a non-default language, cloned default-language title and description content can be excluded until at least one differs. Check each language separately after editing.

The default public paths are:

/known-issues
/known-issues/report
/known-issues/checkout-validation-error

Use links generated by the module for your language and shop. Older ID-based issue paths redirect to the clean slug URL. The installed meta page is module-mprissuesrevolution-issues, with default rewrite known-issues and initial title Known Issues & Bug Tracker. On modern PrestaShop, edit the hub's language-specific rewrite in Shop Parameters > Traffic & SEO.

The hub shows public status counts, open/resolved highlights, and a browser with search, product/status selection, and ordering. Browser interaction happens within the rendered hub. Legacy search/filter/sort/page request states redirect to the base hub URL; do not publish those variants as separate listing URLs.

Hub indexing and sitemap eligibility follow module SEO policy. Detail and report pages remain excluded even when stored indexable flags are enabled. The gSitemapAppendUrls hook requires a sitemap generator that consumes it; verify the generated XML.

The report form can be reached from the product interface or the public reporting page. Both forms apply the same submission checks.

The customer chooses a valid active product and enters a title and email, with an optional description. Validation uses byte lengths: title 10 to 512 bytes and description at most 2000 bytes. Non-ASCII characters can consume more than one byte. A valid email is required.

The form uses a security token and a hidden honeypot. Submissions are limited to three per email or signed-in customer during the preceding hour. Reports store source user, status Pending, Active Yes, and one report vote. They remain hidden until reviewed into a public status.

The built-in form has no file or screenshot upload. Use your normal support channel for attachments. The reporter email is report data for administration; do not copy it into public descriptions or workaround fields.

1. Create an active Open issue for a product and fill the current language's content.
2. Open the product and check the tab title, counts, dates, and status badge.
3. Open the hub and the issue's clean detail URL.
4. Submit a test public report and confirm it appears as Pending in the admin list.
5. Confirm it is absent publicly, then change it to Open and check again.
6. Test a second language and, if used, the generated sitemap.

If the tab is missing, check Enable front display, Hide tab when empty, product association, Active, public status, and theme hooks. If an issue disappears in one language, check that its translated title or description differs from the default-language content. If submission fails, refresh the form for a new token, check byte limits and email, and wait if the hourly limit has been reached.

Individual issue pages remain excluded from indexing regardless of the indexing settings. If a hub rewrite fails, check the installed meta entry, friendly-URL setting, and cached routing. Use Integrity for schema, hook, and infrastructure checks.

Template override paths include:

themes/your-theme/modules/mprissuesrevolution/views/templates/hook/product-tab.tpl
themes/your-theme/modules/mprissuesrevolution/views/templates/front/issues.tpl
themes/your-theme/modules/mprissuesrevolution/views/templates/front/issue.tpl

Theme CSS can use .mprissues-page, .mprissues-wrapper, .mpr-f-item, .mpr-f-badge, .mprissues-detail-panel--workaround, and .mprissues-severity--critical. For example:

.mprissues-wrapper .mpr-f-badge--open {
  background: #dc2626;
  color: #fff;
}

Export or record issues before uninstalling. The module unregisters theme styling, removes its meta page and menu, removes admin preferences and module content links, and drops module-owned issue and translation tables. Saved module settings remain in the database. If theme cleanup fails, uninstall stops before the remaining removal steps. Remote support links to the removed public pages will need updating.