95 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…
7 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 made5 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.
15 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.
10 votes -
Regular Expressions
It should be possible to use regular expressions anywhere. For example in the rule builder.
3 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.
2 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
2 votes - for example :
-
Add updates notifications to user's permissions
The idea is to hide Shopware updates notifications to certain roles.
2 votes -
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 -
Fallback product-layout if NO Layout is assigned
If the values for columns
cms_page_id
andcmsPage
within tableproduct
will be set to "NULL", the "original" default layout for product pages will be used, although I've managed to set up a new product-page layout and marked it as "default" beforehand.Since a different layout was defined as default layout, this particular one should also be used as fallback whenever no layout is assigned.
Steps to reproduce:
- Create custom product layout
- Mark it as new default layout for product pages
- For already existing entries --> set values for mentioned columns to "NULL" or simply remove the layout assignment in…
5 votes -
Remove Admin Worker - CLI Worker as Default
Get rid of the admin worker and use cli worker as default.
18 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.
1 vote -
Captcha Info-Text
The info-text (look at screenshot) for the reCaptcha v3 is not self-explained.
"Grenzwertpunktzahl zwischen 0.0 und 1.0" means what? 1 = less or more bots?! 0 = good or bad value?!1 vote -
Custom field-Entity select-Category should show at least the top-level-category
We have a view top-level-categories with subcategories of the same name in this top-level-categories.
If you want to select a categorie in a custom field of the type "entity select" with the entity "category" it is impossible to find the right subcategorie, because the have all the same name. The field should show the category tree like the standard category selection for a product or at least the top-level-category.1 vote -
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.
1 vote -
Save sorting config in the admin
Sorting in the admin, for example in the customer overview, should be saved automatically when it is applied.
3 votes -
Add admin ownership to all (sales channel) entities
There have to be two types of admin users:
1. Super admin with all privelegies
2. Admin userThe super admin can see and edit all entities.
The admin user can see/use all public entites (for example categories) where the userId is NULL. He can create private entities, only visible for himself or super admins, the userId is the current admin user.
Why this idea makes sense?
Technically we just add a new context variable like the salesChannelId or languageId, the admin user can manage his own product sets without any risk to delete other products.
We could also make…1 vote -
Add extension/plugin ownership property for all entities
If an extension installs data in Shopware I have to remember the exactly IDs for uninstalling. A cleaner solution would be, to define an ownership for the data. If I uninstall the extension, the data can be automatically removed. This could be a technical name or the plugin_id with foreign key. So the plugin can be only uninstalled if the referenced data is also removed. This data could be write protected too, so the shop owner can't delete for example important mail templates or media folders.
1 vote -
Splitting the prices for user roles
The rights for productprice can be assigned under users and roles in the detailed privileges.
However, productprice includes the complete pricing, so it is not possible, for example, to assign rights only for the basic price so that a user does not have access to the extended prices, for example.
It would be user-friendly if there was a further division here than putting everything in product_price.1 vote
- Don't see your idea?