167 results found
-
Blog with Custom Entities
Blogs are an excellent way for businesses to tell stories and generate more traffic around their products. Currently, running a blog requires external setups, which often need coding skills, manual workflows and are disconnected from the shop system. Therefore we will provide an integrated blog functionality as a first example of using custom entities. This will enable merchants to write content, design and publish blog posts without coding skills.
62 votes -
Replacing the sw-text-editor editor
It would be a great Idea to schedule the replacement of the sw-text-editor by a better editor like Tiptap as it is mentioned in the architectural desicion report: https://developer.shopware.com/docs/resources/references/adr/2023-03-27-admin-text-editor-evaluation.html
69 votes -
CMS Extension: Allow custom form to be used for newsletter sign-up
Currently, a custom form provided by the CMS extension can only be used to have a customer send a request to a predefined e-mail address. The ability to also use a custom form for newsletter registration would allow the shop owner to customize the layout or add some basic things, i.e. their own mandatory terms & conditions checkboxes.
3 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 -
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 -
Shopware Publisher: Creates a possibility to restore old versions
Creates a way to restore old versions within Shopware Publisher
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 -
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 -
Shopware Publisher: Improve viisbility of changes
It is currently difficult to see what exactly has been changed in the world of experience, as the relevant areas are not really made recognizable. This only works with “Block added”.
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 -
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.
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 -
Preview of time-configured display
Within CMS pages, for example, you can use the Rule Builder to configure the time-controlled display of blocks and thus control actions, for example.
In order to be able to check such sometimes complex structures, you should be able to log into the customer account and then change the date using a timeline, so to speak.
This allows you to view the CMS pages from the customer view at a specific point in time and quickly and easily check whether everything has been configured correctly. For very large campaigns, this reduces misconfiguration and the potential loss of money.
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 -
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…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 -
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.
2 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 -
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 -
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.
24 votes
- Don't see your idea?