FAQ and Questions and Answers Module
Your customers ask questions on the product page, and you answer them publicly, with moderation, votes, and email notifications. Additionally, you'll find editorial FAQs posted within categories or brands, marked with the FAQPage tag.
Compatible with PrestaShop 8 and 9.
Questions before buying
An unanswered question is a sale that goes to another tab.
Reviews come after the purchase; questions come before. RKR Questions answers them right on the product page, visible to the next customer with the same question.
Moderate questions, answers that work forever
The customer asks a question, and the question awaits your approval: it's written by a stranger on a page that Google indexes. You answer from within the thread, sign with the store's name, and, using a checkbox, publish the question and notify the customer by email.
/ Category and brand FAQs
Question-and-answer pairs that you write and post under a category or brand, ordered by position. They appear with FAQPage markup, which PrestaShop 9 does not generate by default.
If you come from another module, you bring the content with you.
An importer retrieves questions, answers, and FAQs from the tables in the previous module or from a CSV file. It has a simulation button that outputs the same numbers as the data it later prints, allows for repetition without duplication, and generates a report for each decision.
No false promises. Since 2023, Google only displays FAQ dropdowns for government and healthcare websites. The markup remains correct and is read by other search engines and assistants, but we don't guarantee those results on Google. And it's not a reviews module: if you already have one, this one covers something else.
Compatible with PrestaShop 8.0 to 9.x · GDPR: Deletion depersonalizes without losing responsiveness
Developed and maintained by REKIRE
v1.0.3
Three fixes that came out when running the module through maesaldetailer's PrestaShop 9 copy, with its 2,913 real rows.
- The rescue simulation wasn't counting the responses. It reported 2,002 responses, whereas the actual rescue wrote 2.904. In the simulation
writeThread()` returned zero—"not written"—even when the row was valid, so the ID map remained empty and the response loop skipped the 903 responses without any notification. Furthermore, the product of each response wasn't checked, meaning that a discard that was going to occur wasn't reflected in the report. And that simulation number is precisely the one someone noted to later verify that the successful import was successful. - The report didn't add up: 2,913 read, 2,904 written, and 8 discarded. One was missing, and there was no way to know which one. It's the answer to a discarded question—"Your product is no longer in the catalog"—which was skipped with a "
continuewithout being recorded. Now it's counted aspregunta_descartada, and the count closes. tests/ backoffice.test.jscould not run against a client copy. It fabricated the domain asand the copies are.test So, the screen test was only valid in the lab stores, where there's no data. Now it reads.ias.test DOMAINfrom the.envfile and acceptsRKRQ_BO_USERandRKRQ_BO_PASS, because in a client copy, theADMIN_PASSWDfrom the.envfile doesn't open the back office. Integration tests go from 41 to 45: the simulation has to count the same things that are written, discard the same things, and the report has to match.
4 other products in the same category
También podría interesarte
Questions and answers
Nobody has asked anything about this product yet.