174 results found
-
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 -
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 -
Manufacturer link should be translatable
We often use this as a "brand"-link to link internally on the website. Would be awesome if translatable.
4 votes -
Assign product layouts per sales channel
Instead of only relying on languages only, product layouts should be able to be defined for each sales channel.
4 votes -
Clear cache after replacing an image
We would prefer that after the one-to-one replacement of images in the media manager automatically clears the cache.
This is already known from other CMS systems.The reason why the feature would be good is that the page does not display an image without clearing the cache. Since the old assignment was overwritten and the new assignment is not active
4 votes -
SwagPublisher - Allow selection of Sales Channel for preview of drafts
Currently, when previewing a draft, it will always preview the whole thing with the theme you've selected in your "standard" shopping channel. So when previewing a draft you designed for an entirely different channel with a different theme, the draft is not terribly helpful.
4 votes -
New layout block "Tabs"
As a merchant, I like to structure my shop's content with taps, whether on a product detail page or on a simple landing page. A tab block could easily be filled with individual elements like sliders, texts or videos.
4 votes -
Better mobile-first support
The mobil-first approach may be technically lived, but it does not exist in the application. There are no options for mobile content settings or adjustments. Not even a preview exists. Here you can only be reactive on the road. Even the headless approach only affects the display, but not the usability as an admin.
4 votes -
Option to choose how many elements are visible in a multi-element-block
In picture sliders, commerce sliders, multi-element-blocks, the max quantitiy of elements visible side by side at once is capped at 3 (except of the cross selling block afaik). The customer should be able to choose a number higher than three. A full sized commerce slider with only three products visible is just too little and the three ones visible are way too big
4 votes -
Publishing Workflow
For easier collaboration in teams, lower chances for errors a configurable publishing workflow would help
4 votes -
Improve handling of 100+ shopping experiences
Improve handling of 100+ shopping experience
4 votesInitial status update
-
Listings for Landingpages
It should be possible to add product listings to landingpages (landingpages as the category type, not the layout). Solution could be the possibilty to select also layouts of type "Listing" in the Landingpages. Currently one can only select layouts of type "Landingpage".
4 votesInitial status update
-
Save form data to database
Currently data submitted by forms is only transferred via mail to the merchant. Therefor it can't be used for any further processing.
Therefor it should be possible (optional?) to (also) send all form data to the database so the merchant can re-use it for ...4 votesInitial status update
-
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 -
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: 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”.
3 votes -
Shopware Publisher: Creates a possibility to restore old versions
Creates a way to restore old versions within Shopware Publisher
3 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 -
Lock against multiple sending of custom forms
When using a very extensive custom form, the customer experienced a delay after clicking on Send. He was able to click on the button several times, as a result of which the form data was also sent several times by email. The customer's suggestion is to deactivate the respective buttons after submitting and then reactivate them when a result is achieved.
This would be a useful addition, as it would prevent any errors in the event of delays in the response.
Beim Einsatz einer sehr umfangreichen Custom Form kam es beim Kunden zu einer Verzögerung, nachdem der Shopkunde auf Absenden…
3 votes -
Show CMS element label (same for blocks)
It would be nice to see the used elements (and blocks) in admin to identify them. Especially with custom elements.
Similar elements are sometimes hard to distinguish or retrievable.
3 votes
- Don't see your idea?