FAQ Professional

Fixed

• Saving was blocked — across the whole shop, not just the FAQs. Anyone trying to save a product, an order, a category or a setting could not get through while this plugin was active. The plugin called a function of the shop system that only exists from Shopware 6.7.13 onwards. Only shops on a Shopware version below 6.7.13 were affected — for them this update resolves it completely. If your shop already runs 6.7.13 or newer, nothing ever went wrong for you.
• The statistics tile “Unanswered FAQs” was misleading. It lists questions nobody has ever opened — not questions without an answer. It is now called “Never opened FAQs”, matching the line beneath it.
• The product assignment of an FAQ group needed two lines. The field showed as many entries as the fields above it, although product names are considerably longer — the remainder wrapped onto a second line and the form looked untidy. It now shows fewer entries and stays on one line; the count beside them still names the full set.
• Updating from an older version could stop halfway through. If a table the plugin expected was missing from the database, the update halted there and everything after it was left undone. The visible symptom was the new category and product assignments simply not being there afterwards. The update now steps over a missing table instead of stopping.
• If a table belonging to this plugin is missing because an earlier update failed, the update now brings it back itself, instead of leaving it permanently missing. Running the update again used not to help either: once the migration that creates the table was already marked as done, it never ran a second time, and the table stayed gone for good. Anyone who wants to check or trigger this by hand can now use the console command syn:faq:tables:check (with --repair to fix it).

Important when updating

If your update to 6.7.6 broke off, there is nothing to repair by hand. The steps left undone will run automatically during this update.

Fixed

Affects managing FAQs in the backend unless stated otherwise.

• A newly assigned question lands at the end of the list instead of the top. Previously every save reset its position in every group. Existing groups are numbered once during the update; your order is preserved.
• The Quote button in the answer editor deleted the selected text instead of converting it. It now wraps it.
• The search term you typed stayed behind after picking an entry. It now disappears, and the list offers all entries again.
• The question and group lists remember which columns you switched on — per user account, including column order and compact mode.
• After saving you return to where you came from. To stay on the screen, use the second button next to it.
• The save buttons show that writing is in progress. With many assignments this takes a noticeable moment.
• An active entry can always be switched off, even after losing its last assignment. Only switching it on is blocked.
• Groups with more than roughly 9,400 assignments were shown incompletely. Saving in that state could lose the part not loaded. The full set is now read.
• An FAQ group's description now appears in the shop, between the group heading and the first question.
• The Cancel button in the delete dialog shows "Cancel" again instead of an internal text key.
• Labels in the administration have been tidied up, including placeholder texts and the spelling of "FAQ group".
• The answer field's label sits above the field again, with proper spacing below.

New

• "All sales channels" with a single switch — including channels created later. Your existing selection stays saved and applies again once you switch it off.
• FAQ groups can be assigned to categories and products, not only through tags. A tag is still enough, and so is a category. Subcategories do not inherit the assignment.
• Anchor links optionally without the group name. shipping-how-long-does-delivery-take then becomes how-long-does-delivery-take. Links you have already shared keep working either way. The previous form is preconfigured — change nothing and nothing changes.
• Selecting groups, tags, categories and products is clearer. What you type is matched at the start of a word first; for large numbers there is a "Show all" dialog with search and an alphabet index.
• Groups sharing a name can be told apart — the question count follows, for example "Shipping & Delivery (195)".
• The question and group lists can be filtered by sales channel.
• The group list shows the "Categories" and "Products" columns.
• Category pages show assigned FAQ groups even without a CMS block. An existing block still takes precedence.

Important for this update

Shops running Elasticsearch need a reindex so that "All sales channels" also takes effect in the shop search. Details in UPGRADE.md.

Your existing links are unaffected.

Fixed

Affects how the FAQs appear in the shop, and there above all visitors working
without a mouse — with the keyboard or with a screen reader.

• An outline shows again where the keyboard currently is. Anyone moving
  through the questions with the tab key now sees the current question
  highlighted; previously there was no way to tell which question would open on
  pressing enter. When operating with a mouse the outline stays away — there you
  know where you are anyway.
• A link inside a question no longer gets in the way. When a question
  contained a link, that link sat inside the expand control. Screen readers
  cannot resolve a control within a control: the link was unreachable and the
  control not reliably operable. Links in the question are now shown as text;
  formatting such as bold or italic is preserved. Nothing changes in the
  answer — links stay clickable there, and that is where they belong.

Both points concern mandatory levels of accessibility (WCAG 2.2, levels A and
AA). For online shops the European Accessibility Act has required them since
June 2025.

Improved

• Source code optimisations for better readability.

Fixed

Affects installations where the administration is rebuilt from source —
typically agency and deployment environments. Anyone installing the plugin from
the store and using the prebuilt files supplied with it was not affected.

• The administration build completes again. The package was missing the
  file that lists the required JavaScript packages. Without it Shopware does not
  fetch them and the build stops with "Rollup failed to resolve import"; until
  now the only remedy was to add the file by hand.
• Seven JavaScript packages are now listed explicitly. Until now they came
  along only because another package brings them. With package managers that use
  strict layouts — pnpm or Yarn, for instance — the build could fail on this.

Improved

• The list on a statistics page that is still empty ends with punctuation and
  writes "30 days" as a figure.

Fixed

Affects the statistics page in the backend, and there above all shops where
little or nothing has happened yet. Wherever a figure was still missing, the
page either left parts out or moved them.

• Four tiles stand side by side again. The fourth one — "Ratings" — was
  missing as long as nobody had rated an answer; it now shows a dash until the
  first rating arrives.
• The small charts inside the tiles have their full height again. When the
  green or red comparison figure above a chart is missing — the normal case
  during a shop's first days — the chart was previously squeezed into a quarter
  of its height, leaving a large empty area beneath it.
• Tiles without figures show a fine line where the bars will later appear.
  Previously the area was simply empty.
• The period below the first tile appears only once there is one. On a new
  shop the word "History:" previously stood there with nothing behind it.
• Anyone narrowing down by sales channel or language that has no views yet
  now reads exactly that. Previously the same sentence appeared as on a shop
  without any data at all — even when other channels had long been delivering
  figures.
• The "Reset statistics" button appears only when there is something to
  reset.
• An internal association between question and FAQ group carried the wrong
  name. This had no effect on the display in the shop or in the backend — the
  association is not read anywhere in the plugin. Anyone extending the plugin
  with their own code now receives it as expected.

New

• A statistics page that is still empty explains what will appear there —
  and names the condition for it: the FAQs have to be visible in the shop, as
  their own page, as a product tab, in the category or as a CMS block.

Improved

• Source code optimisations for better readability.

Fixed

Affects all shops. The command palette in the answer editor — the menu that
appears after typing a slash — was missing two behaviours that only become
apparent when you keep typing after the slash.

• The selection narrows with every character typed. Typing tab after the
  slash now shows only the matching commands; previously the full list
  remained.
• The menu follows the caret. It now sits below the position being typed at
  with every character; previously it stayed where the slash had been typed.

Improved

• The supported PHP versions are now stated explicitly: 8.2 to 8.5.
  Installation on an older version is refused up front instead of failing
  during operation — previously the lower bound was left open, although the
  code uses language features from 8.2 onwards.
• The source code has been brought in line with the expressive means of
  those versions throughout, making it shorter and more uniform to read.
  Behaviour is unchanged.

Also included

Version 6.7.1 was not released separately. If you are coming from 6.7.0, this
update brings its changes as well:

• The statistics show trends. Below each of the four tiles you can see how
  the value developed: one bar per day for views, a ring for the ratings.
  Hovering over a day shows the date and the count.
• The rating percentage is put into context. Next to the percentage there is
  a sentence naming it. How meaningful the figure is depends on the number of
  votes cast.
• Every tile states the change against the preceding period of equal length.
• Notification titles and column headings appear in the language set for the
  administration. This affected the list and edit pages for questions and
  groups.

New

• Statistics now include charts. Each of the four tiles shows how its value developed: one bar per day for views, a ring for ratings. Hovering a day reveals its date and count, including days without a single view. Previously the tiles held four numbers with no chart.
• The rating percentage is put in context. A sentence next to the figure states what it amounts to. How dependable the figure is depends on the number of votes cast: where there are few, the hover text names the range the actual value falls in.
• Each tile states the change against the preceding period of equal length — green for an increase, red for a decrease, grey where the value is unchanged. Where no complete preceding period exists yet, the absolute increase is shown instead of a percentage.

Fixed

Affects shops whose administration is run in English.

• Notification titles and column headings appear in the language the administration is set to. The lists and editing pages for questions and groups were affected; previously these texts were hard-coded and stayed German in an English backend.

Maintenance

• The foundations of the editor for answers and group descriptions have been updated. The changes concern tables, lists and the interplay with the administration. Editing questions and answers is unaffected.
• Builds of the plugin are reproducible. All third-party packages are pinned to fixed versions and checksums. Previously this applied to only some of them, so two installations could end up with different packages. Storefront operation is unaffected.
• Statistics processing is split into individually testable parts, both administration indexers share a common base, and the route definition is YAML. Behaviour is unchanged.

• The update deactivates questions and groups that have no sales channel or no group. The rule has always been stated next to the active switch: a question can only be active once a sales channel and a group are assigned. Until now it was enforced by the admin list view — silently, on opening the page, with no feedback. That had a consequence few would suspect: such questions remained findable through the shop's search until someone happened to open the right admin page. Whether a customer saw a result depended on backend behaviour. The update now enforces the rule once, traceably. The entries themselves are kept and still appear in the list with a red notice — they are simply no longer active.
• Sales channels without a storefront can no longer be selected. The selection fields for FAQ groups, for questions and in the statistics filter offered every channel, including "Headless" and "Product comparison". None of them has an HTML storefront: an FAQ assigned there is never displayed, and the statistics filter reliably produced an empty report without any indication why. Existing assignments to such channels are removed by the update. Questions and groups themselves are left untouched.
• The FAQ lists in the admin open considerably faster. The group list attached every question of a group to each row, merely to show four numbers: count, clicks and the helpfulness rating. With a well-filled FAQ inventory that added up to several megabytes per page view; now it is a few dozen kilobytes. The question list likewise loaded complete sales channel records per row just so one column could show names. The displayed figures are unchanged; they are now calculated rather than collected.
• Entries per page are now the same in both lists: 25, 50 or 100. Previously questions offered 15/30/50/100 starting at 15, groups 15/25/50/100 starting at 25. The smallest step is gone — fifteen rows fill half a screen these days.
• New: how long the click log is kept. Selectable under "Data retention": 12 months, 24 months or keep indefinitely. A daily task then cleans up by itself. The default is "keep indefinitely" — an update should not delete statistics nobody asked to remove. Choose a period there if you want the table pruned.
• Statistics evaluate noticeably faster. The filter by sales channel and language used columns that were in no index, so every report read the entire click table. That goes unnoticed with a few rows, not with real traffic. In addition, "reset statistics" now respects the active filter instead of always clearing everything.
• The admin search now finds umlauts. Searching for "Größe" or "Rückgabe" previously returned no results at all, even though the questions were there.
• A question now appears only once per page. Where the same question belongs to two groups — for instance a general question meant to appear everywhere, alongside the product tab — it was previously output more than once, both visibly and in the markup for search engines. This now applies across the whole page, not just per output area.
• The copy icon is off by default. New under “Formatting / Appearance”: “Show copy link behind each question”. Nothing about your FAQ page changes on update — the spacing of the questions is untouched as well. Turn it on there if you want it.
• A linked question now appears at the top instead of mid-screen. The same link used to end up in three different places depending on whether you opened it fresh, confirmed it again in the address bar, or reloaded the page. All three now land in the same spot, clear of the header.
• A copy icon behind every question. One click puts the link to that exact question on the clipboard — handy for mailing a customer the one answer that fits instead of pointing them at the FAQ page. Deliberately built as a button, not a link: with thousands of questions there would otherwise be just as many extra internal links on one page for search engines to follow. It adds no extra links to your page.
• Switching language keeps the question you were reading. Open a question, switch the language, and you land on the same question in the new language instead of at the top of the page. If it does not exist there, the page top it is.
• FAQ suggestions in the search led nowhere in other languages. In a shop with language domains every suggestion pointed at the address without the language prefix — a page that does not exist. It went unnoticed because it never happens in the default language.
• Links to a single question are now readable. Instead of …/faq-page#faq-d4d4d4d4…-f6f6f6f6… it now reads …/faq-page#general-questions-how-do-i-order — group name and question in short form. Anyone passing such a link on by email, chat or ticket can see at a glance where it leads; an AI assistant reading llms.txt passes on the same readable link. Applied to the FAQ accordion, the search suggestions, the search result page and llms.txt.
• Links already shared keep working unchanged. Every question additionally keeps its previous anchor faq-{groupId}-{faqId} in exactly the place it has always been. A link a customer saved months ago, or left in a forum, still jumps to the right question and opens it. No previous anchor is dropped.
• Fixed: a single incompletely translated FAQ group took down /llms-full.txt for that language entirely. The page answered with a server error, so not just that one group was missing but all the others with it. This state arises in any shop as soon as someone creates a group and adds the translation later. A group without a translation now simply appears without a name.
• The machine-readable files are now correct per language. Addresses carry the language path of the respective sales channel domain (/en/… instead of the default-language address), and the FAQ page is resolved via the SEO address of that very language. Where the page does not exist in a language, no per-question links appear — and the file says so explicitly instead of looking as if the shop had no FAQs at all.
• Anchor links follow the text actually displayed in each language. With "Fall back to the default language when a translation is missing" enabled, the page shows the default-language text — and the link then points there too. Every question keeps its own unique anchor in every language.
• llms.txt is now an index instead of a data dump. It carries one section per FAQ group and links every question straight to its place on your FAQ page — an AI assistant jumps to the single answer instead of reading through everything. Previously the entire stock sat in this one file; in a mid-sized shop that meant several megabytes, and many requests broke off before the end. It is now a few dozen kilobytes.
• New: /llms-full.txt with the complete collection. Every question with its full answer, linked from llms.txt so a model actually finds it. Answers are no longer cut off after 500 characters.
• Lists and paragraphs in answers no longer run together into one word. "Payment methods:PayPalCredit cardPrepayment" reads as "Payment methods: PayPal, Credit card, Prepayment" again — the same applies to lists, paragraphs, headings, line breaks and tables. Of all places, the file meant for machines was full of gibberish.
• The link to /faq is gone: that address does not exist in the shop, so the link led nowhere. The page from the "FAQ landing page for search results" setting is linked instead. If none is selected, no question link appears at all — better none than a dead one.
• Both files only list groups that actually appear in the shop, and are served as Markdown, as llmstxt.org requires. The existing /llms.txt address keeps answering unchanged.
• FAQs can now be placed in a column. Until now the FAQ output was only available as a full-width block. There is now an FAQ element that can be placed into any column via "Replace element" in the Shopping Experiences editor — for example into the right half of a two-column layout. Which questions appear is governed by the page's tags as usual. The heading level of the group name is configurable on the element so it fits the outline of the page it sits on.
• The FAQ block now shows in the Shopping Experiences editor what will later appear in the shop. Previously it showed only the title and an empty box below it. Pick a sample product or category under "Demo entity" in the sidebar and you will see the groups and questions that actually apply to that object. Without a selection, a note explains what the selection depends on — nothing is shown that the shop would not output later.
• The FAQ block and the FAQ element now appear under their own heading "FAQ Professional" in the selection dialog instead of under "Text". Existing Shopping Experiences are unaffected.
• When several FAQ sections sit on one page they no longer collapse each other. Previously, opening a question closed an open question in the other section.
• The schema.org markup now appears exactly once per page, regardless of whether the FAQs come from the product tab, the block or the new element.
• New editor for answers and group descriptions. The previous text field is replaced by an editor with images, video, quotes, callout boxes and slash commands. Existing content is carried over unchanged — verified against a cross-section of real field content, every one of them character-exact.
• The question is now a plain text field. A question needs no formatting. Questions already saved remain untouched and are displayed unchanged in the shop; anyone editing one will see the markup it contains as text.
• Opening an FAQ entry in the editor no longer alters the links it contains. Previously the editor would have added rel="nofollow" and a new target window on save — affecting how search engines rate them, without anyone having edited anything.
• The search results page now groups FAQ hits by their group and shows the group name as a heading instead of a badge next to each question. This matches the CMS block and the product tab.
• "Was this answer helpful?" now actually works on the search results page — the buttons were visible there but had no effect.
• On a non-default language the field again shows the default-language text as a placeholder, so translators can see what they are working on.
• Four display settings take effect again: icon style, icon position, separator line and its colour could be configured but had no effect on the output.
• The options "Show group name as heading", "Display group name in bold" and "Display question in bold" can now actually be switched off.
• FAQs next to the search suggestions now also appear in shops with multiple language domains.
• The structured data now only contains questions that are actually visible on the page, and is capped at 100 entries.
• The scheduled cleanup task for votes older than one year aborted on its first deletion run. Fixed.
• The description texts no longer promise Google rich snippets: Google switched off the FAQ presentation in search results in May 2026. The schema.org markup itself is unchanged and is still read by search engines and AI assistants.
• New version scheme: the first two digits name the Shopware line this release targets. In terms of content it is the direct continuation of 2.4.0.

• First release for Shopware 6.6. Feature set matches version 2.4.0 of the Shopware 6.7 line.
• New version scheme: the first two digits name the Shopware line a release is built for. Versions 6.6.x run on Shopware 6.6, versions 6.7.x on Shopware 6.7.

• You can now choose whether FAQs appear above or below the products on the search results page. New setting under "Search".

New Features

- New setting under "General": "Fall back to default language for untranslated FAQs" (off by default). When turned on, FAQs that have not been translated yet are shown in the shop's default language instead of being hidden.

- New "Translations" column in the FAQ list and the FAQ Groups list. It shows at a glance which languages already have a translation (✓) and which are still missing (✗).

Improvements

- FAQ search now only shows FAQs in the language you are browsing. A German FAQ no longer shows up when searching in the English shop (unless you turn on the new fallback setting above).

- FAQ search now stays up to date automatically. No separate command needs to be run anymore.

- Clearer wording in the search settings ("search suggest" instead of "search dropdown") so the option is easier to find.

- When editing a FAQ or FAQ group in a language other than the shop's default, you can now leave the text empty and the default language content is used instead. Only the default language still requires the text to be filled in.

Bugfixes

- Fixed an error that could break product and other pages in a language where the FAQs had not been translated yet (for example an English shop with FAQs maintained only in German). Untranslated FAQs are now simply hidden, or shown in the default language if the new fallback setting is turned on.

- Fixed the "Question & Answer need to be filled" and "Groupname needs to be assigned" messages appearing when saving a translation in a non-default language. These texts are no longer required there.

## New Features

- Plugin configuration "Search": new toggle "Show FAQs on search result page" (default: on) — completely disables the FAQ list on the `/search` result page

- Plugin configuration "Search": new "Hidden" option for the search dropdown position — completely disables FAQ suggestions in the suggest dropdown

## Improvements

- FAQ accordion anchor IDs switched from question slug to the stable format `faq-{groupId}-{faqId}` — prevents anchor collisions when identical questions exist across groups and survives question rewordings. Applied consistently to search result page and search-suggest links

- Administration: `flagUrl` in the FAQ overview now uses Shopware's `asset` filter instead of a hardcoded `/bundles/` path — resolves correctly in setups with external asset storage (CDN/S3)

## Bugfixes

- Search result page and search-suggest: HTML entities in FAQ questions (e.g. `&`) were double-encoded and rendered as `&` — appended `|raw` after `|striptags` so already-encoded entities from the rich-text field are not escaped again

Fixed missing use statement for FaqGroupCollection in ProductPageLoadedSubscriber

- New feature: Dynamic /llms.txt route — outputs all active FAQ groups with questions and answers as machine-readable plain text, compatible with the llmstxt.org standard for AI readiness.

- Improvement: Revised display position logic — "Product tab, or CMS block if present" now shows FAQs in the product tab only when no CMS FAQ block is present on the page (CMS takes priority).

Configuration label updated accordingly.

- Bugfix: Display position "Everywhere" did not show FAQs in the product tab when a CMS FAQ block was simultaneously present on the page — condition corrected.

- Improvement: Removed "Don't display FAQ tab" option from plugin configuration — tab visibility is controlled per FAQ group via the group's "display position" setting.

- Security: LIMIT values in SQL queries of the statistics controller are now explicitly cast to int. Added whitelist guard in FaqHelpfulService — column name is validated before being used in SQL

statements.

- Statistics: Most-read FAQs are now always read from `syn_faq_click_log` — fixes missing entries when the denormalized `click_count` cache was stale

- Statistics: Country flags in the "Clicks by Language & Domain" widget were not displayed — corrected file extension (`.svg` → `.png`), fixed mapping for `en-US` (→ `us`) and `no-NO` (→ `nb`)

• Faq search setting + improved search with search term for index pages
• Schema.org answerCount error fixed
• Refactor frontend to control cms/tab/both views
• Add missing snippets
• Faq/FaqGroup pages now update the global search filter to Faq/Faq group

• restrict faq and groups to selected sales channels only for all pages

• restrict faq and groups to selected sales channels only

• fix issue with FAQ styles

• first Shopware-store relaunch

• Migration tables added

• add manufacturer prefix to css classes and twig blocks
• renamed files to include manufacturer prefix
• refactoring to make inner css classes plugin specific
• add Migration missing folder

• fix error in FAQ-Grouping

• Shopware-Code-Review-Errors fixed

• Shopware-Code-Review-Errors fixed

Removed broken namespaces