184 results found
-
Read more for CMS Shopping Experiences Block / Weiterlesen bei CMS Erlebniswelten Block (Truncate text)
EN:
The possibility to select read more and read less in the CMS Shopping Experiences Block. Configuration: the lines after the button for read more is showed.DE:
Die Möglichkeit auf der CMS Erlebniswelten weiterlesen und weniger lesen anzeigen zu lassen. Konfiguration: Zeilen nachdem der Button weiterlesen und weniger lesen angezeigt wird.1 vote -
View/delete all unused images/media files
A way to display all unused media files in the admin panel and then delete them. This feature was available in Shopware 5.
Eine Möglichkeit im Admin alle nicht verwendeten Mediendatein anzeigen zu lassen und diese dann auch zu löschen. Diese Funktion gab es in Shopware 5.
4 votes -
Delete media - folders get not removed
If a medium is deleted manually in Contents > Media, the folder path, e.g.
/media/38/85/66/1728367134/, is retained, only the file is removed. The same phenomenon also occurs when deleting/clearing up via Command line. Even if each directory only takes up a small amount of space, many empty directories quickly accumulate, which means that a lot of unnecessary space is taken up.Please also remove the directories when cleaning up.
Wenn ein Medium in Inhalte > Medien manuell gelöscht wird, bleibt der Ordnerpfad z.B.
/media/38/85/66/1728367134/erhalten, nur die Datei wird entfernt. Das gleiche Phänomen tritt auch auf, wenn die Löschung…12 votes -
Enhanced Mobile Customization Options for Storefront
The mobile version of the storefront offers limited customization options compared to the desktop view. While sections can be disabled for mobile, more granular controls — such as adjusting font sizes, spacing, borders, or hiding certain elements like tables — are missing. Providing more flexibility for mobile-specific design adjustments would significantly improve the user experience and storefront quality across devices.
1 vote -
Category teaser image for subcategories in navigation flyout
Currently, display images from categories are only shown in the navigation flyout if it is a main category. For subcategories, however, the display image can only be used for display on the respective listing page.
It would be desirable if the display image could also be shown for subcategories within the navigation flyout (configurable via option).
1 vote -
Dynamic mail recipients for custom forms
Allow dynamic mail recipients based on selection witihin a custom form.
Example: A custom contact form contains a dedicated field for "subject:".
Based on whatever a customer is selecting here (e.g. complaint, technical issues etc...) the mail recipient may change.The mail recipient should be determined dynamically. There must therefore be a type of mapping or rule builder within the form configurations in which the mail recipients can be assigned to specific selection values.
3 votes -
Drafting: Create a draft state of your changes
Problem:
Users cannot currently create and manage a comprehensive draft state for changes across their storefronts. This makes it difficult to plan, test, or iterate on updates without affecting the live environment. As a result, merchants may delay changes, work in risky live environments, or rely on inefficient workarounds — increasing the likelihood of errors and reducing agility in campaign or content management.Solution:
Create and manage a draft state for all kinds of changes in Shopware before publishing them live. This allows you to bundle multiple updates, such as content, design, and promotions, into a draft, enabling safe workflows…3 votes -
Improve error feedback on misconfigured Shopping Experience blocks
When configuring a Shopping Experience template, you should get more detailed error messages when misconfiguring a given block.
For example: Creating a new product detail page with the "Three columns, product boxes" block is not possible without configuring it. When trying to save it only says
"Page could not be saved, because of the following errors:
Some blocks were not configured sufficiently."It would be nice to have a better feedback on which blocks are actually misconfigured. Either via a red border or by actually pointing to it somehow.
2 votes -
Improve inheritance
Many fields shouldn't be inherited from the main language, e.g. meta title, meta description or image titles and alt texts. If no translation is entered for these, it would be better if meta description, image titles and alt text would fall back to the product name. And meta description doesn't need a fall back at all.
Inheriting these fields from the main language only leads to problems. In our case, the main language is german. If we sell a product on our english sales channel as well, there's no way we will ever need german meta data for that channel.
3 votes -
Default layout specific for different sales channels
EN
We have been waiting for this feature for a long time, a category layout created by us set as default layout, super, mega, awesome since SW6...... however, this category layout is applied to all our sales channels. This is unfortunately impractical as we have three different brand stores, and the category layouts can and should be visually different from each other.Example:
Store 1 has custom category layout for its category pages
Store 2 has custom category layout for its category pages
Store 3 has custom category layout for its category pages
–
DE
Wir haben, ein von uns…4 votes -
Lack of Insert-Anywhere Function for Sections in Shopping Experiences
In many of our CMS projects, we regularly need to insert new sections into the middle of existing Shopping Experience pages.
Problem:
Currently, Shopware only allows new sections to be added at the top or bottom of the page. If you want to place a section between two existing ones, you must:Add the new section at the end or beginning.
Manually drag and drop it up/down through the page structure.
For longer pages, this is time-consuming and error-prone.
Wish / Recommendation:
A simple solution such as a “+” button between sections (like in many visual builders) or a contextual…1 vote -
YouTube Shorts integration
YouTube videos can already be integrated into Shopping Experiences via the YouTube video element, but YouTube shorts are not yet supported by this element.
3 votes -
Confirm deletion of blocks beforehand
If you delete a block in the cms, this change is implemented and saved immediately. If this happens accidentally, it can lead to unintentional data loss, which can cause a lot of frustration.
It would therefore be good if the deletion had to be confirmed beforehand or if it was no longer saved automatically.2 votes -
gallery fullscreen option does not show there is something clickable
When using a gallery-block with the option enable full-gallery and hovering over it
→ it does not show, that something is clickablerequest:
the customer's mouse should show a "hand" so that the customer can tell that it is click-able2 votes -
Extend the element varienty in shopping experiences | Funktion Elemente austauschen überarbeiten
EN
It would be very practical if it were possible to select any element in the “Replace element” function, which can also be added in the block settings. Because at the moment there are only selected elements there. However, we have often needed an element that is not available for selection. For example, the image element “two columns, centered”.
–
DE
Es wäre sehr praktisch, wenn es bei der Funktion "Element austauschen" möglich wäre jedes Element auszuwählen, was man auch in den Block Einstellungen hinzufügen kann. Denn momentan gibt es dort nur ausgewählte Elemente. Jedoch kam es bei uns schon…1 vote -
Connect multiple databases to a Shop
Customer data is often a very sensitiv topic. In our case, the desired set up for storing the data would be to have one database for the Shop relevant and a complete separate database for all customer related data.
2 votes -
Shopping experiences: "Topseller" sort for product-slider
There are different values for sorting within the configuration of the product slider. The ‘Topseller’ selection is missing at this point, which would result in a further and useful customisation of the configuration. This would make sense at this point and is requested by customers.
7 votes -
replace Tiny Slider as the default slider
The current default slider integration with tinyslider seems not be maintained anymore.
It would be good to switch to a maintained slider lib again as tinyslider has a multitude of issues, espacially with accessibilty and it is not really customizable.4 votes -
Copying CMS content - reusable elements
It would be nice to have the option of copying elements from the shopping experiences and using them in a different place.
Example: We have the "XY" section in the start page - this should be filled and customised once and then copied in the next step and used in another page.
26 votes -
Change size and location of CMS blocks dynamically
At the moment the size and the location of CMS blocks in the shopping experiences a fixed. The only options to change the size is to switch the display mode.
It would be great to dynamically change the sizes and not to be limited by the fixed bounds.
2 votes
- Don't see your idea?