- or
1391 results found
-
Total of all products without list prices
There should be a condition in the rulebuilder for the total sum of all products that not have a list price. So that promotions can refer exclusively to non-discounted products.
1 vote -
Allow data mapping of custom fields in CMS Elements
Currently it is only possible to use shopware standard fields via data mapping in CMS elements. It would be great if we could also use custom fields here.
9 votes -
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 -
I am trying to customize SEO URL slugs and encountered an issue
When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.
This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when we are using inheritance for all the descriptions and stuff. But when I turn it on, you force me to pick one of the variants. But I don't logically want it to be one of the variants, i want it to be main product. That leads me to another problem that I tried to solve with you: main product cant have the same product number as variant. So I cannot create variant as main product - so I cannot use it as main product for canonical URL. BUT! I think you would tell me: change storefront presentation, lets go to Product-Variants-Storefront presentation-Product lsitings and instead of Main product you could pick one variant and go with it. But I don't want to do it, because if I choose it as "Main product" in the storefront it is more beneficial since it shows, that there are more variants and price starts at.... You know what I mean? I don't want the specific size of the product be as main variant, you actually told me not to, since you require variant and main product to have different product number.
This is actually really frustrating. Because I want it (as it should be):
- main product - main URL - it is main product page that I want to be crawled by search engines
- variants - url with whatever slug added to the main product URL, but I don't want Google to crawl it.
Sounds pretty easy, right? And it even works like that, just not in case if I want to use MetaTitle as a slug.You give me these:
- main product - main URL (i want to use meta title for that and you allow it since it is in the list of supported variants)
- variant - can't use meta title - it makes it different url, which is ugly and not practical
- seo canonical - can use only variant, not meta title, so basically I have many duplicate pages and it takes us down from Google.When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.
This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates…
2 votes -
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 -
No mandatory fields for Import
The fact that there are mandatory fields during import means that unnecessary data (e.g. stock in the event of a price change) is transferred, but this only delays the duration of the import and makes no sense.
For example, it is not necessary to change the stock when changing prices. This is not necessary and only delays the duration of the import. For large customers, the import takes many hours.
It would therefore be desirable to be able to deactivate the dependencies.
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 -
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 -
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 -
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 -
Extend ScheduledTask "delete_newsletter_recipient_task"
It seems that the deletenewsletterrecipient_task only removes unconfirmed newsletter subscribers that remain in that particular state for longer than x-days. It would be good, if we could automatically remove all newsletter recipents that already unsubscribed and remain in status "Awaiting deletion". Those currently have to be deleted manually.
10 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 -
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
- Don't see your idea?