188 results found
-
Expand the Rule Builder condition: ‘Billing address: Street’ > ‘contains’
For example, to exclude the value ‘Packstation’ within the street name for payment types, the value ‘contains’ is also required there.
5 votes -
Be able to create new Address Snippets
Currently, there is only a predefined set of snippets, that can be selected in "Settings > Shop > Countries > 'SELECT_COUNTRY' > Address Handling" for the Address Markup.
Adding new Snippets would be great for instance to add a new snippet for the street number or to customize the Address markup as you need it.
2 votes -
Presets for roles
There should be fixed roles for employees. The classic roles such as customer service (read only) and SEO should be available as standard. Access to each individual setting point should be separately selectable.
1 vote -
Display of variants in product-sliders and cross sellings if assigned via dynamic product group
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always…
3 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."
3 votes -
Add discount as sorting option
There is currently no nice way to create a sorting option based on the discount of products in the Admin under "Settings > Shop > Products > Sorting options".
It is a common use case (especially during times like Black Friday), that consumers sort the products based on the discount. It would be valuable to have that option also for Shopware.
3 votes -
When I work in the Admin, I don't want to fall back into the overviews again and again, but to the last editing location.
When I'm in the admin and search for something in products, for example, then edit it and go back, I expect to return to the last search result and not end up in the overview.
9 votes -
Set default value for account type in register form
We need to define a default value for the account type select in register forms (private / business)
3 votes -
Deactivate user
In addition to creating and deactivating users, it should also be possible to temporarily deactivate users in the admin (Settings > System > Users).
27 votes -
Add User Permission for Notifications in Administration
Certain roles don't need to get notifications about licence violations and updates. Therefore, we need to bind those notifications to dedicated user permissions.
5 votes -
Settings > System > Users & Permissions: Rename Snippets to Textbausteine
If your admin interface is set to German, the right for the “tTextbausteine” is displayed as snippets in the role of a user. This should be renamed.
2 votes -
Optimization of plugin management and configuration in Shopware 6 Admin
We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.
Note from Shopware Support:
We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and…3 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.
11 votes -
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…
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…
13 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)…1 vote -
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 -
Payment methods only available for admin orders / Hide specific payment methods in checkout
It should be possible to enable certain payment methods for admin orders only, without them being visible in the frontend.
9 votes -
Searchable comments
Customers can add comments on the checkout page
Issue is that in the Administration, it is until now not possible to search for comments of customers
Example:
- customer calls the shop owner and asks if the comment made was considered
- customer wants something excluded or special made10 votes -
Extend rate limit to storefront operations optionally
We can protect most "vulnerable" parts of the store already with a rate limiter. This includes the contact form or login & password reset pages for both the frontend and the Admin.
However, there are "vulnerable" parts for the cart (and potentially other parts) as well. A shop owner monitored that presumably a bot rapidly added products to a cart over and over again over hours, placing high load on the database due to the spam collecting in the cart table.
Since we already have a rate limiter in the code, it would be nice and possibly fairly simple to…
2 votes
- Don't see your idea?