- or
1510 results found
-
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…
13 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 -
free shipping
Toggle free shipping on the product either by country or by sales channel.
Introducing this feature is essential for the internationalization of an online store.
2 votes -
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 -
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 -
Add filters in the media library
In the media library we would like to have the following filters so that it will be easier to detect unused files:
- file used
- file unused
- data type
8 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 -
BMECat 1.2 or BMECat 2005 format for catalog import and export
BMECat 1.2 or BMECat 2005 format for catalog import and export.
BMEcat is a standardized exchange format for product information based on XML. Developed at the University of Essen, it first became widespread in German-speaking countries and then increasingly in Europe. BMEcat is now the world's dominant exchange format for electronic product catalogs.
7 votes -
Reviews analyzed by category
It would be helpful if product reviews can be analyzed not only by product, but also by category
1 vote -
Promotion label
Used promotions have a position in the cart, given the promotion's name. That name therefore normally should be something "understandable for the customer".
However when having a larger number of promotions, it can get quite confusion to work internally with all the promotions in a shop, having nothing but these "customer friendly names".Solution: The "name" of promotions is their internal identifier. Above that every promotion gets a field for a public "label" which its position in the cart gets labeled when cashed in.
Example:
Shop has three different promotions named "10 % new customer promotion", "10 % newsletter voucher" and "10 % easter campaign" for unique identification internally.
When used, each of these promotions positions uses its "labals" instead of their "names", which could even be the same label in all three cases (for example simply "your 10 % discount")Used promotions have a position in the cart, given the promotion's name. That name therefore normally should be something "understandable for the customer".
However when having a larger number of promotions, it can get quite confusion to work internally with all the promotions in a shop, having nothing but these "customer friendly names".Solution: The "name" of promotions is their internal identifier. Above that every promotion gets a field for a public "label" which its position in the cart gets labeled when cashed in.
Example:
Shop has three different promotions named "10 % new customer promotion", "10 % newsletter voucher"…8 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 -
Add function to be able to order custom products without personalization.
Currently it is only possible to order custom products without personalization if no configuration option is declared as a mandatory field in the custom products template. This means that the customer can only order the original product if the store has not set any mandatory fields in the personalization.
Sometimes store operators want to be able to sell the original product without personalization. However, for certain products, mandatory fields are required in the custom product template if the customer wants to personalize this product so that the necessary options are selected by the customer.
Here it would be very good to have a new function checkbox that makes it possible to order products as original despite mandatory fields in the configuration.
Currently it is only possible to order custom products without personalization if no configuration option is declared as a mandatory field in the custom products template. This means that the customer can only order the original product if the store has not set any mandatory fields in the personalization.
Sometimes store operators want to be able to sell the original product without personalization. However, for certain products, mandatory fields are required in the custom product template if the customer wants to personalize this product so that the necessary options are selected by the customer.
Here it would be very good…
2 votes -
Bulk AI text generation and translation
Bulk AI text generation and translation refers to using AI to create and convert large amounts of text across different languages. This technology automates writing and translating texts, which can be especially useful for content creation and localization on a large scale. The aim is to produce high-quality, coherent text quickly and efficiently.
7 votes -
Add new address on change
Let's say a customer uses one the same address as default delivery and default billing address. If editing this particular address through the administration and either(!) clicking
"Set as default delivery address"
OR
"Set as default billing address"it automatically marks this one address as default delivery and default billing address anyways - most likely because there only is one address.
In this case it would be nice, if we could automatically add a new address if the only address available is being edited and used for either "default shipping address" OR "default billing address". So in total I would have the "original address" (before editing) and the edited one (only marked as default shipping OR default billing)
Let's say a customer uses one the same address as default delivery and default billing address. If editing this particular address through the administration and either(!) clicking
"Set as default delivery address"
OR
"Set as default billing address"it automatically marks this one address as default delivery and default billing address anyways - most likely because there only is one address.
In this case it would be nice, if we could automatically add a new address if the only address available is being edited and used for either "default shipping address" OR "default billing address". So in total I would…
2 votes -
Make headless sales channel non-deletable
There are always support tickets where the customer has deleted the headless sales channel and the store is therefore no longer accessible.
As there is no conceivable reason for deleting the headless channel and this happens again and again with customers, resulting in support tickets, this option should be removed.
3 votes -
Custom product attributes are transmitted individually to Google Analytics
If Google Analytics is used for ads, the attributes of custom products are transmitted as individual items. This can quickly become overwhelming. A checkbox, for example, to group the attributes could be an option.
2 votes -
Position related discounts in cart / order details
Enable position related discounts in cart and order details. Currently all discounts that have been granted for one cart are beeing summed up and they show as one dedicated position.
8 votes -
Apply Discount as direct deduction with extended display (Strike prices) in the frontend.
In Shopware 6, the discount is not displayed directly on the product, as it was in Shopware 5, but rather as a separate item in the shopping cart.
I would like to have the option to avoid this. For example:
If there is a 10% discount on products from a specific brand, the discount (Strike prices) should be applied globally directly to the product without having to manually reduce each item and later readjust them. In Shopware 5, this was handled much better, as the price reductions were visible both in the frontend and on Google, which is not the case with a cart-based discount.It would be great if you could integrate the function from the Advanced Promotion Suite SW5 into Shopware 6.
In Shopware 6, the discount is not displayed directly on the product, as it was in Shopware 5, but rather as a separate item in the shopping cart.
I would like to have the option to avoid this. For example:
If there is a 10% discount on products from a specific brand, the discount (Strike prices) should be applied globally directly to the product without having to manually reduce each item and later readjust them. In Shopware 5, this was handled much better, as the price reductions were visible both in the frontend and on Google, which is not the…3 votes
- Don't see your idea?