- or
1269 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…
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 -
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 -
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 -
EAN as Listvalue for Variant and Productview
A thing which you have always to change inside a Product/Variant is the EAN-Code. Today i have to open the variant/Product to change that. It would be a big effort to have the possibiliy to change it in the list view.
(Extra Column EAN for Variant Listview and ProductListview)1 vote -
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 -
custom fields for checkout and invoice
We need custom fields so the customer is able to insert a reference or his external order number. This field should also be displayed in the invoice
5 votes -
Rule Builder - Additional operators for custom fields
Additional fields can be created with a date field and can also be used in a rule. Unfortunately, there aren't very suitable operators available. Useful ones would be: "Time until," "Time after," "Between," "Greater than," and "Less than."
2 votes -
"Questions about the article" function from SW5
What happened to the "Questions about the article?" function? In sw5 there was an enquiry form with direct reference to the article.
It would be nice to have this as standard in SW6.
6 votes -
"Amazon Pay" to shopware cloud
Cloud shops are advertised, but the major payment method ‘amazon pay’ is not offered. This must be available.
1 vote -
Formatting of the ratings
Formatting of the ratings is not taken over.
The ratings are always displayed without formatting, so it is not possible to insert line breaks.
This would be desirable so that the ratings are easy to read even with longer texts.1 vote -
Deactivate user
In addition to creating and deactivating users, it should also be possible to temporarily deactivate users in the admin (Settings > System > Users).
19 votes -
Two factor authentication support for admin
For security reasons it will be favorable to add native Two factor authentication support in the admin.
8 votes -
Add products with graduated prices directly to the shopping cart at listing level
For products with graduated prices, these cannot be added directly to the shopping cart at listing level. As soon as graduated prices are defined, “Details” appears at listing level instead of “Add to shopping cart”.
3 votes -
Provide the possibility to add and customize Data Layers
As it became critical to use data layers since the end of UA and because it's best to use tools like GTM (and because other tools like Meta, Bing and Ads are depended on them as well), It would be crucial to manage the data layers in Shopware.
4 votes -
Export for tax consultants/tax office
Within Shopware 5, it was possible to select and export data from various database columns for the tax office/tax consultant.
e.g.: ‘all orders from 1.7.2024 to 30.9.2024 and also specify the country of delivery and the tax rate per product’
This is no longer possible with Shopware 6, but should be standard for quarterly tax reports.
2 votes -
Allow the semicolon as a separator in the quick order
The quick order function of Shopware Commercial currently only allows the upload of .csv files that are separated by a comma. However, Microsoft Excel works with the semicolon for csv files by default. As a result, it has become a kind of industry standard in the B2B sector to use csv files with semicolons. It would be very helpful if you could set in the admin which separator is expected when uploading .csv files in the quick order.
2 votes -
Edit dashboard messages
It would be nice if customers themselves had the option of deactivating or moving messages on the dashboard.
3 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
7 votes
- Don't see your idea?