Child pages
  • Product Questions - Magento 2
Skip to end of metadata
Go to start of metadata


Firefox user notice:

Please use different web browser to view this document.

Sorry for the inconvenience.

Product Questions - Magento 2

The Magento 2 Product Questions extension appends a dedicated tab to product pages where customers can ask public and private questions (accessible for admins only), get answers, and give rating to individual questions. Store admins can decide which questions should be published, made private or public, or rejected and timely inform shoppers on their question status updates by email. The extension’s sharing options allow displaying questions for individual store views and selected products.

Product Page

Thank you for choosing Aheadworks!

Installing Product Questions

Command Line Installation

1. Backup your web directory and store database

2. Download Product Questions installation package

 3. Upload contents of the Product Questions installation package to your store root directory.

 4. In SSH console of your server navigate to your store root folder:

cd path_to_the_store_root_folder


php -f bin/magento module:enable Aheadworks_Pquestion


php -f bin/magento setup:upgrade


php -f bin/magento setup:static-content:deploy

5. Flush store cache; log out from the backend and log in again.


Make sure the installation is done from under the FTP administrator account. Otherwise, make sure to set 775 permissions to the store root directory after the extension is deployed.

Composer Installation

1. Log in to your customer account at and navigate to Account -> Composer access;

2. Configure your store to work with the Aheadworks composer repository:

Add composer repository to composer.json by running:

composer config repositories.aheadworks composer in the Magento installation root.

Use a key pair provided as login and pass. You can optionally save them in the global composer auth file.

 3. You can start using AW composer now.

 For extension names, navigate to Account -> Composer access.

 4. Open the root Magento directory on your server and send Composer the following command:

composer require <component-name>:<version>

Note: Use the previously copied component name and version.

 5. Make sure that Composer finished the installation without errors. Flush store cache, log out and log into the backend again.


Set up cron

If you have already configured cron jobs for your Magento installation then you can skip this step. Read the following instructions on setting cron job for your Magento store: Magento user guide 

Generally, it would be enough to run in SSH console of your server: 



And insert the following line:  



Don't forget to confirm saving request when exit.



Migrating questions from Magento 1

Product Questions 1.1 for Magento 2 introduces a questions migration tool. The questions and answers generated by Product Questions for Magento 1 can be migrated with the help of Magento Data Migration Tool. To migrate the tickets follow the steps below:


Read carefully and consider this information of top priority as otherwise, it may result in an accident data losses.


  1. Magento Data Migration Tool is required to be installed prior to starting the migration.
    The migration script relies heavily on Magento Data Migration tool. Understanding how it works will prove useful during the migration process.
  2. Backup Magento 2 databases before the migration to have an opportunity to revert any changes.
    Ticket migration may involve rewriting database tables, so backup is advised.
  3. Questions and answers can be properly and confidently migrated only from the M1 Product Questions 2.x.x version and above. If you have previous versions installed, do not try migrating them on your own.
  4. Migration specifics:
    You need to make sure that the Magento Webstore and Website IDs are the same;
    Target customers on a destination store are determined and assigned by customer emails specified in the source Magento1 store;
    Target products on a destination store are determined and assigned by product SKUs stored in the source Magento1 store;
    Target product attribute sets on a destination store are determined and assigned by attribute set names provided in the source Magento1 store.
  5. Sharing options migration specifics:
    Product question sharing options are converted in the following way

     - Product(s) -> Selected Products with SKU condition (Certain Product, if only one product is selected)
     - Attribute Set -> Selected Products with Attribute Set condition
     - Website & Global -> All products

    If there is no chance to determine the products suitable to share a particular question, this question receives the sharing status - 'All Products', and the publishment status - 'Unpublished'. And, the corresponding notification about such questions is added to the migration log (aw_pq2_migration.log).

1. Install Data Migration Tool following the instructions provided by the Magento team.

2. Copy contents of the /etc or /src folders (for Magento 2.1.x and Magento 2.2.x respectively) found in the installation package of Product Questions for Magento 2 to vendor/magento/data-migration-tool/ folder.

3. Navigate to vendor/magento/data-migration-tool/etc/aw_pq2/ and open config.xml for edit.

More information on the tag values and what one should put inside can be found in the Magento Data Migration Tool configuration instructions.
<source> - is the source database the questions and answers should be migrated from.
<destination> - is the target database the questions and answers should be migrated to.

4. Run the migration process from the console:

bin/magento migrate:data -r vendor/magento/data-migration-tool/etc/aw_pq2/config.xml

5. Ticket migration is complete.


Introducing Product Questions


Product Questions extension introduces question/answer thread to the product pages of your store. Whether you want to answer the questions yourself or let the community do it for you, Product Questions offers a communication platform with the following options:

  • Public/private questions;
  • Manual/auto approval;
  • Guest questions;
  • Email notifications.


Getting Around


Once installed the extension introduces question blocks to the store product pages and its section to the customer account area.

Product page blocks

At the product pages, customers have an access to the Product Questions tab. To ask a question or answer it customers are suggested to:

  • Specify the name;
  • Email address;
  • Type in the question;
  • Decide if they want the question to be private or displayed for other store customers.

All the approved questions are displayed below the questions block.

The question approved is followed by the answers. The answers can be submitted by either store administrator or other customers or both, depending on the Product Questions settings.

Each question and answer can be rated by the store customers. Rating system serves as an additional sorting tool along with the date question/answer posted.

Customer account

The Product questions section of the customer account is represented by all the questions asked and the answers given.

Form this section customers can see if the question has been answered yet or if a particular question or answer has been published.

Moreover, Product Questions extension allows subscribing to the email notifications about the question and answer updates. The subscription is independent for questions and answers and can be canceled at any time.


Store backend


Questions grid

For the backend, the extension introduces its page under Marketing > Product Questions by aheadWorks > Product Questions.

This is the section where store administrator manages and answers the questions asked. The product questions grid can be adjusted according to a particular task:

  •  button allows adding/disabling the columns in the grid, some may be excessive and some relevant to the current tasks;
  •  button allows looking for the questions matching a set of attributes;
  • button allows saving perfect grid look you found to quickly load it whenever required.

The questions can be selected and published, rejected, deleted, set available for public or private, right from the grid.


Product Questions extension comes with a set of filters that can be accessed by clicking ‘Filters’ icon  or ‘Views’ icon .

All the filters applied are displayed above the questions grid and can be disabled at any time:

'By product' grid

The 'By Product' grid is another question management screen available for Product Questions extension.

This screen represents all the products available at the store and a number of questions asked for this particular product, making this grid somewhat of a reporting tool. The filters described previously can also be applied to the 'By Product' grid. 

By clicking a product of interest store administrator is redirected to the Manage Questions screen with the product clicked acting as a filter:

Answering questions

To answer a question store administrator needs to click it in the grid.

The question form provides store administrator will full control over the question asked. Administrator can:

  • Change the question’s visibility;
  • Adjust rating;
  • Edit the question’s body;
  • Answer it and manage the answers provided.

Additionally store administrator can set the sharing options:

            • Select the store view the question is available for;
            • Decide for what products the questions should be displayed;
            • Set the conditions for displaying the question.

Once done with the question store administrator can decide if it should be approved, rejected or deleted.


Extension settings


Product Questions extension comes ready for work right after installation. However, if required store administrator can personalize the extension behavior under Store > Configuration > aheadWorks extensions > Product Questions.

Settings are represented with the three sections:

  • General Settings – let store administrator control the extension behavior and functional aspects of the Product Questions;
  • Interface Settings – suggest defining the look and feel of the Product Questions blocks;
  • Notification Settings – controls how the notifications are handled.

General Settings

  • Who Can Ask Questions from Product Page – defines if only registered customers can ask questions;
  • Who Can Answer Questions for Product Page – defines if only customers who have purchased the product can answer the questions;
  • Approve Answers Automatically – if set to 'yes' all answers are approved automatically;
  • Guests can rate – if set to 'yes' guest customers will have an opportunity to rate questions and answers;
  • Subscribe customers to Product Questions emails automatically – defines if customers are subscribed to Product Questions updated by default;
  • Customer-defined question visibility – if set to 'No' customers cannot define questions visibility.

Interface settings

  • Number of questions to display – defines a number of questions to be displayed below the Product Questions tab;
  • Number of answers to display – defines a number of answers to be displayed below the question;
  • Display URLs as links – defines if URLs in questions and answers should be clickable;
  • Default questions sort by – defines if questions should be sorted by rating or date;
  • Default sort order – defines if the sort order is descending or ascending.

Notification settings

  • Send admin notifications to this email address – all the Product Questions notifications will be sent to this email address;
  • Email Sender – defines the emails that will send notifications;
  • Admin notifications about new questions – defines the email template;
  • Admin notifications about new answers – defines the email template;
  • Customer notifications about new replies to their questions – defines the email template;
  • Customer notifications about the questions status change – defines the email template;
  • Customer notifications about the answer status change – defines the email template;
  • Auto-Responder to customer about his new question/answer – defines the email template;
  • Remove the web copies of the emails older than X days – defines for how long should the web copies of the emails should be stored in the database (aw_pq_notification_queue).

Product Page

You can always find the latest version of the software, full documentation, demos, screenshots, and reviews on
License agreement:
Contact Us:
Copyright © 2018 Aheadworks Co.

  • No labels