102 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…
10 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 made7 votes -
Mailer: Different SMTP data for different sales channels
More and more providers are prohibiting the sending of emails that do not come from the same domain.
However, as you can only store the access data of one domain in the mailer, this becomes a major problem as soon as you enter several sales channels with different domains.
From that moment on, not all messages can be sent or are rejected by the provider.
"mailbox unavailable\r\n 550 Sender address is not allowed.""
It should therefore be possible to configure the mailer settings for each sales channel.
5 votes -
Hausnummer von Straße trennen
Es fehlt die Möglichkeit die Straße und die Hausnummer in zwei getrennten Kästchen anzeigen zu lassen und im Backend seperat angezeigt zu bekommen.
Wir haben in der Woche ca. 50 Bestellungen wo nur die Straße ohne Hausnummer eingefügt wird und wir diese Bestellungen nicht versenden können.
Es gibt zwar einen Workaround über das "Straße & Hausnummer in 2 Felder Plugin" aber es wäre wirklich nett, wenn man das von Haus aus direkt im System einstellen könnte.
13 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).
6 votes -
Email log
It would be great if there was an email log again, like in Shopware 5, in which you can clearly see all the emails that have been sent.
17 votes -
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.
3 votes -
Auto added product
- for example :
if product A (bottles/flaschen) is added to the cart, then product B (deposit/Pfand) is added automatically
this should be available for both self-hosted and cloud, as it was requested very often
3 votes - for example :
-
Separate role permission to deactivate the dashboard statistics
At the moment the dashboard statistics are bound to the permission to see the orders. If a role just need the right to work with the orders, and the merchant does not want, that the role member is able to look at the statistics, he has no way to configure this.
It would be nice to have a permission to deactivate the statistics or the complete dashboard to a role.
1 voteWe will remove the dashboard statistics and will integrate a proper rights and role management to the planned statistics. Feel free to check the progress on that on the public roadmap: https://www.shopware.com/de/roadmap/
-
Regular Expressions
It should be possible to use regular expressions anywhere. For example in the rule builder.
3 votes -
Flowbuilder - form related triggers
Implement triggers that validate on specific fields / entries within a (custom)-form.
For example: If field1 (checkbox) is true / checked, then perform action xy on customers.
2 votes -
Add updates notifications to user's permissions
The idea is to hide Shopware updates notifications to certain roles.
2 votes -
Extend system requirements
When an update is to be done via the admin, the tab "System Requirements" always appears, but it does not check the technical requirements for the database, etc.
1 vote -
Option to add Default Value for Custom Fields.
I think adding an option to choose a default value for the custom Fields would be a good improvement for the Admin. I was recently implementing a new Custom Field Set and I wanted to add default values that would be set anywhere where you would like to use the custom Fields.
I just saw that there was also another issue that was opened a few years ago. It seems this is a wanted feature and would be greatly appreciated if you would plan it.
https://issues.shopware.com/issues/NEXT-7414
https://github.com/shopware/shopware/issues/5901 vote -
Deactivate e-mail header / footer in the templates
It should be possible to deactivate the header and footer in the e-mail templates or, even better, to choose between different headers and footers.
This would allow a much more flexible design of the emails.
1 vote -
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.
1 vote -
OPcache clearing with admin and API
We occasionally have customers who have errors (PHP exception, 404 etc.) after updating extensions (SW6: Paypal extension, security plugin etc.).
A reset of the opcache helps in many cases.
As in Shopware 5, resetting the OPCache should also be possible in Shopware 6 via the admin or via API. This can solve many problems with extension updates.
2 votes -
Flow Builder - B2B component trigger and actions
Add action item to automatically set b2b component flags based on customer group
1 vote -
Remove Admin Worker - CLI Worker as Default
Get rid of the admin worker and use cli worker as default.
19 votes -
Bug in rule builder > "count of completed orders"
Tested object: completed orders are not counted correctly - or maybe not at all.
My order list shows customer orders that are marked as “completed”. (Payment: pending, shipping: partial or completed). But the rule ignores the fact. Even if I set all 3 fields (order, payment, shipping) to "completed" as a test, this rule doesn't apply.
1 vote
- Don't see your idea?