- or
No existing idea results
- ~ No ideas found ~
1267 results found
-
Possibility for the customer to filter products according to availability in the storefront
Possibility for the customer to filter products according to availability
1 vote -
Remove cookie setting “Google advertising and marketing”
We have updated our store to version 6.5.8.7 today due to the 404 security vulnerability. Now the option “Marketing > Google Advertising and Marketing” appears in the cookie settings, which was probably added with the adjustment NEXT-32925 - Add Google Consent V2 in version 6.5.8.6. However, we do not use tracking (especially not from Google), so displaying the setting makes no sense, may even raise additional customer questions and has a bad aftertaste. I don't like the fact that the option simply appears unasked after the update in the cookie settings in the storefront - especially since you are forced to make the update, as it was not included as a patch in the security plugin (if I have understood this correctly)... Unfortunately, I have not found a way to hide the option. It would make sense if the option is not displayed at all if you have not stored a tracking ID in the sales channel.
https://forum.shopware.com/t/cookie-einstellung-google-werbung-und-marketing-entfernen/103280
We have updated our store to version 6.5.8.7 today due to the 404 security vulnerability. Now the option “Marketing > Google Advertising and Marketing” appears in the cookie settings, which was probably added with the adjustment NEXT-32925 - Add Google Consent V2 in version 6.5.8.6. However, we do not use tracking (especially not from Google), so displaying the setting makes no sense, may even raise additional customer questions and has a bad aftertaste. I don't like the fact that the option simply appears unasked after the update in the cookie settings in the storefront - especially since you are forced…
1 vote -
increase "Entry per page" in catalogue > products
Should be instead of: 10, 25, 50, 75, 100
50, 100, 200
Default should be 100.
Why: to see more products at once and on larger resolution display (higher that FullHD) it is not a problem to see 200 products at once.
14 votes -
The default country should be preselected during registration.
The default country should be preselected during registration, or at least there should be an option to set this.
2 votes -
Custom fields - floating point only with two decimal places
In the custom fields I can select "number" and then choose between integer and floating point number. However, when using a floating point number, my input is rounded to 2 decimal places. This should be adjustable in the admin if you need more than 2.
3 votes -
Support partial quantities and decimals in order quantity & inventory
As a merchant, I want to manage and sell products in partial quantities or decimals, so that I can efficiently handle use cases like selling goods by weight, length, or volume, and better meet the needs of industries requiring fractional units.
This will improve flexibility for different business models and ensure seamless inventory management and customer satisfaction.
1 vote -
Country settings per sales channel
It should be possible to define country settings (e.g. setting the "shipping"-flag) per sales channel
1 vote -
Captcha / DSGVO friendly solution
EN:
Honeybot seems not to the effective, so we need a new captcha solution.Inspired on captcha solution on the plugin store:
- Timeout Captcha (timeout if the form is submitted earlier: the captcha is invalid)
- Bad-Word-Captcha (with regular expressions)Since the processing remains local, there are no GDPR problems, e.g. no mention in the cookie consent or in the data protection declaration is necessary.
DE:
Honeybot scheint nicht mehr effektiv zu sein, somit brauchen wir eine neue Captcha-Lösung.Inspiriert von der Captcha-Lösung im Plugin-Store:
- Timeout Captcha (Timeout, wenn das Formular früher abgeschickt wird: das Captcha ist ungültig)
- Bad-Word-Captcha (mit regulären Ausdrücken)Da die Verarbeitung lokal verbleibt gibts hier auch keine DSGVO Probleme, z.B. keine Aufnahme im Cookie Consent oder in der Datenschutzerklärung notwendig.
EN:
Honeybot seems not to the effective, so we need a new captcha solution.Inspired on captcha solution on the plugin store:
- Timeout Captcha (timeout if the form is submitted earlier: the captcha is invalid)
- Bad-Word-Captcha (with regular expressions)Since the processing remains local, there are no GDPR problems, e.g. no mention in the cookie consent or in the data protection declaration is necessary.
DE:
Honeybot scheint nicht mehr effektiv zu sein, somit brauchen wir eine neue Captcha-Lösung.Inspiriert von der Captcha-Lösung im Plugin-Store:
- Timeout Captcha (Timeout, wenn das Formular früher abgeschickt wird: das Captcha ist ungültig)…1 vote -
Multi-Change Cover on Variants
(This feedback was formerly created as NEXT-23370)
EN
The multiple changes should definitely make it possible to set the cover image. If an article has many variants that don't differ in appearance, it's a real punishment to go through them all and set the cover images by hand. Not to mention how much time is wasted doing it.
DE
Über die Mehrfachänderungen sollte es unbedingt ermöglicht werden das Coverbild zu setzen. Hat mein ein Artikel mit vielen Varianten, die sich optisch aber nicht weiter unterscheiden ist es eine echte Strafe alle durchzugehen und die Coverbilder von Hand zu setzen. Ganz davon abgesehen wieviel Zeit man dabei verschwendet.
(This feedback was formerly created as NEXT-23370)
EN
The multiple changes should definitely make it possible to set the cover image. If an article has many variants that don't differ in appearance, it's a real punishment to go through them all and set the cover images by hand. Not to mention how much time is wasted doing it.
DE
Über die Mehrfachänderungen sollte es unbedingt ermöglicht werden das Coverbild zu setzen. Hat mein ein Artikel mit vielen Varianten, die sich optisch aber nicht weiter unterscheiden ist es eine echte Strafe alle durchzugehen und die Coverbilder von Hand zu setzen. Ganz…
1 vote -
Optimise enlargement of product images
The product image should be possible by spreading the thumb and index finger. The entire form currently reacts to this.
This problem only occurs in our Shopware 6 shop. Our Shopware 5 shops all react correctly at this point. We urgently need an adjustment here.
2 votes -
Accidental up / down due to slipping during the gesture should be prevented.
Since Shopware 6 there is a problem (not within our Shopware 5 shops) that when swiping to scroll the images (product slider) it is no longer excluded that the form scrolls up or down in the wrong direction if accidentally moved.
This problem does not exist with our Shopware 5 shops, but only with our Shopware 6 shop.
The aim is to prevent the form from accidentally scrolling up or down when scrolling between images.
2 votes -
Show HTML code of documents
When you open the created documents, they are PDFs and when you preview them, you do not see the code from the Twig files of the documents, but something else.
However, since you can only download PDFs, you can't really see what the associated HTML code and the applied CSS looks in the browser's developer tools.
If you know this, you can adapt the templates much more easily.
Now you have to guess the passages you want to change.
2 votes -
Admin Search: set if the search used fuzzy search (fault tolerant) or not
EN:
Set if the search used fuzzy search (fault tolerant) or not because we have the problem there are to many search results, if type the exact mail address in the customer search field, of the mail address domain. If typed in the exact mail address only one or two results (if there is a customer and a guest account with the same mail address should the shown). If entered the mail address domain only all customer with the exact mail address domain should be shown.The search bar in the admin for customers is in great need of improvement.
DE:
Es soll festgelegt werden können, ob bei der Suche Fuzzy-Suche (fehlertolerant) ist oder nicht, da wir das Problem haben, dass es zu viele Suchergebnisse gibt, wenn die genaue E-Mail-Adresse der E-Mail-Adressdomäne in das Kundensuchfeld eingeben werden. Wenn die genaue E-Mail-Adresse eingeben, werden nur ein oder zwei Ergebnisse angezeigt (wenn ein Kunden- und ein Gastkonto mit derselben E-Mail-Adresse vorhanden sind, sollten diese angezeigt werden). Bei Eingabe der E-Mail-Adressdomäne sollten nur alle Kunden mit der genauen E-Mail-Adressdomäne angezeigt werden.Die Suchleiste im Admin bei den Kunden ist stark verbesserungsbedüftig.
EN:
Set if the search used fuzzy search (fault tolerant) or not because we have the problem there are to many search results, if type the exact mail address in the customer search field, of the mail address domain. If typed in the exact mail address only one or two results (if there is a customer and a guest account with the same mail address should the shown). If entered the mail address domain only all customer with the exact mail address domain should be shown.The search bar in the admin for customers is in great need of improvement.
…
4 votes -
Clean the cache partially
It should be possible to clean the cache partially. In this way the server is not forced to rebuild everything, and it's really important for performances (also PSH told me that). Check how Adobe manage it: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/manage-cache
1 vote -
Language-specific images
Presently, it is not possible to use language specific images, the very same image is shown in every language. However, it totally makes sense to have language specific images as Online merchants may use it in combination with text to tease the prospect purchaser or even use e.g. banner images for "call to action".
See example attached (<a href="http://www.freepik.com">Designed by Freepik</a>)
9 votes -
increase "Entry per page" in customer overview
Should be instead of: 10, 25, 50, 75, 100
New: 50, 100, 200
Default should be 100.
Why: to see more customers at once and on larger resolution display (higher that FullHD) it is not a problem to see 200 customers at once.
15 votes -
Improve return management with automatic stock adjustment
It should finally be possible to create several returns within one order. Currently you can only create one return. That is far too less.
On the other hand, the return items should be automatically added back to the stock. Currently you still have to do this manually. However, if an order is placed for this return item in the meantime, there are immediate stock inconsistencies.
Creating a credit note via a return is far too complicated for this. The creation of credit notes should be urgently improved.
1 vote -
Reviews analyzed by category
It would be helpful if product reviews can be analyzed not only by product, but also by category
1 vote -
SW6 - erweitertes / verbessertes Logging für Production (DEV log for PROD)
https://issues.shopware.com/issues/NEXT-34433
EN:
Description: The production environment of Shopware 6 lacks a logging function to be able to trace errors in particular. This was much better and easier with Shopware 5. In Shopware 6 it is only possible to get a halfway usable logging for a production environment with a lot of expertise and trickery.Problem: A (longer-term) changeover from a production environment to a DEV environment is not an option for 99% of store operators, as the frontend naturally changes as a result and becomes debuggable for everyone, etc. The second problem is that some errors only occur in LIVE operation (e.g. customer-specific errors / empty shopping baskets / session errors etc.) which logically cannot or can only be partially reproduced in a test environment.
Therefore, a useful logging extension would not only be desirable, but in my opinion a mandatory program for every professional store system.
Suggestion for improvement: -> integrate different logging options for the production environment -> integrate an overview like the "Frosh Tools" plugin to make logging easy for every store operator. (possibly also similar to Shopware 5)
How you can currently convert the entire logging manually (temporary solution) is described here: https://stackoverflow.com/a/78143930/23062645
––
DE:
Beschreibung: In der production Umgebung von Shopware 6 fehlt eine Logging-Funktion um insbesondere bei Fehlern diese nachvollziehen zu können. Das war bei Shopware 5 weitaus besser und einfacher gelöst. In Shopware 6 ist es nur mit viel Fachwissen und Tricksereien möglich ein halbwegs brauchbares Logging für eine Produktivumgebung hin zu bekommen.Problem: Ein (längerfristiges) Umstellen von Produktivumgebung auf DEV Umgebung ist für 99% der Shopbetreiber keine Option, da sich natürlich auch das Frontend hierdurch verändert und für jeden debugbar wird usw. Das zweite Problem liegt darin, dass einige Fehler nur im LIVE-Betrieb auftreten (z.B. kundenspezifische Fehler / leere Warenkörbe / Session Fehler etc.) die in eine Testumgebung logischerweise nicht oder nur teilweise nachgestellt werden können.
Daher wäre eine brauchbare Logging Erweiterung nicht nur wünschensert sondern in meinen Augen Pflichtprogramm für jedes professionelles Shopsystem.
Verbesserungsvorschlag: -> verschiedene Loggingoptionen für Production Umgebung integrieren -> Übersicht integrieren wie durch das "Frosh Tools" Plugin um das Logging auch für jeden Shopbetreiber unkompliziert darstellen zu können. (ggf. auch so ähnlich wie bei Shopware 5)
Wie man das ganze Logging aktuell manuell umbauen kann (tempräre Lösung), ist hier beschrieben: https://stackoverflow.com/a/78143930/23062645
Für den Anfang wäre ein Optionsfeld mit verschiedenen Logging-Stufen erstmal ausreichend:
Logging Typ: [Prod-Log (Standard) ]( Dev-Log | Dev-Log ohne "deprecated" Meldungen (empfohlen bei Fehlern) )Vorschlag: Unter "Administration - Einstellungen - System" den Button "Ereignis Logs" in "Logging" umbenennen und darunter die Logfiles nach dem Schema von Frosh-Tools auswählen und anzeigen lassen. Alternativ einen neuen Button hinzufügen, wenn das Ereignis Log nicht so mal eben erweiterbar ist... In dem Fall bitte eien Hinweistext mit einem Link mit einbauen "für die Ereignis-Logs klicken sie >hier<" und bei den Ereignis Logs "für weitere Log-Dateien klicken Sie >hier<") ;)
--
Spätere Erweiterungen / Verbesserungsvorschläge:
Wenn man damit intern die Monolog.yaml konfiguriert, könnte man auch noch eine Optionsfeld einfügen mit dem Text "Split Log-Files into daily files (default) | single log-file". (type: rotating_file | stream) Ein Input-Feld mit Keyword-Filter (auszuschließende Keywords) (z.B. deprecated) schön.In der Log-View:
Input Feld "Filtern nach ..." Ein "Download-Logfile" Button.EDIT: Auf die grandiose Formatierung dieses Beitrags habe ich keinen Einfluss, weil schlichtweg die Buttons fehlen... Aber darüber rege ich mich nicht weiter auf... Baustellen gibts hier genug...
https://issues.shopware.com/issues/NEXT-34433
EN:
Description: The production environment of Shopware 6 lacks a logging function to be able to trace errors in particular. This was much better and easier with Shopware 5. In Shopware 6 it is only possible to get a halfway usable logging for a production environment with a lot of expertise and trickery.Problem: A (longer-term) changeover from a production environment to a DEV environment is not an option for 99% of store operators, as the frontend naturally changes as a result and becomes debuggable for everyone, etc. The second problem is that some errors only occur in…
12 votes -
Basic price always visible in cart
Add an option to have the basic price always visible in the cart, even if the basic unit and the sales unit are equal.
Füge eine Option hinzu, den Grundpreis immer im Warenkorb anzuzeigen, auch wenn die Grundeinheit und Verkaufseinheit übereinstimmen.
1 vote
- Don't see your idea?