101 results found
-
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 -
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/
-
Flow Builder - B2B component trigger and actions
Add action item to automatically set b2b component flags based on customer group
1 vote -
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 -
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 -
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 -
HTML Sanitizer + Custom Fields
Fields sind ein zentrales Konzept, werden aber in der Doku bezüglich dem HTML Sanitizer in 6.5 ausgespart.
Doku + mit Core ausgelieferte shopware.yml
https://docs.shopware.com/de/shopware-6-de/tutorials-und-faq/html-sanitizer
https://github.com/shopware/shopware/blob/6.5.x/src/Core/Framework/Resources/config/packages/shopware.yamlFragen
1) Ist eine Konfiguration für ein einzelnes customfield überhaupt möglich?
2) Ist eine Konfiguration für alle customfields einer Tabelle möglich.Siehe auch
Siehe https://forum.shopware.com/t/html-sanitizer-ausnahme-fuer-zusatzfelder/100536/2
Custom1 vote -
Log events as an individual selection menu in Settings / System / Event log
Regarding the logging events in SW6: From our point of view, it would be very useful to be able to select which events are logged and which are not when setting up Shopware. We understand that it is not the intention that a nonsensical number of entries should be recorded. However, it would be very useful for those users who want to see which emails have been sent, for example. We are sure that this is important for many users. Best regards - info@ladenbau-gehlert.de
1 vote -
filter admin
The filter options in the admin should be adjusted a little. For example, it should also be possible to use rules from the Rule Builder to multiply the possibilities.
An example of this would be
"Customer - is one of sales channel - XYZ"This is particularly useful for marketing purposes if the AI copilot cannot handle things.
1 vote -
Option to deactivate/activate all non-shopware extensions
Since extensions from other manufacturers very often cause errors and many customers are not very familiar with databases, an option in the admin would be advantageous to deactivate and activate all non-shopware extensions.
Customers currently use the following article for this:
This article is mentioned very frequently in support tickets and, due to its complexity, often leads to customers needing further help because they are not familiar with the database.
This would save the customer a lot of time and lead to faster ticket resolution in support.
1 vote -
Wildcards in dates to create anual repeating periods
Why not having the opportunity to insert dates with wildcards like "02.04.*" which would open the possibility to create scheculed time-periods which will be active "every year" or also "every month". My intention is to create time-periods in rules for the sales in year which i could use to show or hide blocks in a template.
1 vote -
Custom fields: Allow configuration of digits for number float field
In the custom field settings, it should be possible to set the number of decimal places for floating point number fields. If you add this to the config array within the custom field config, it already works. There is only one setting option in the Admin.
1 vote -
Item-related discounts in the shopping cart and invoice.
We have a big problem with the fact that the discounts are only displayed as a single item. In the case of partial deliveries, the customer only receives the (too high) discount on one invoice and no discount is displayed on the second partial delivery. If products from a partial delivery are canceled, this has no effect on the discount.
1 vote -
Rollback feature for shopware Update
In support tickets and in various forums you often read about problems with Shopware updates. It is not uncommon for the store (frontend and admin) to no longer be accessible after an update.
To avoid destroying the entire store or the customer's test environment, the update should check the accessibility of the frontend/admin at the end. If, for example, the browser returns an error 500, a rollback should be triggered to restore the store to its previous state.
Currently, the customer is often faced with an unsolvable problem in this case and loses a lot of time until the store…
1 vote -
Password generator for new customers inside administration
We would love to get back the password generator from shopware 5 for adding new customers from administration. We don't often need it, but in case we need it, it was way more comfortable in Shopware 5.
If there are any plans for the b2b suite, to give sales representatives the option to add new customers, it would be quite neccessary, I think.
1 vote
- Don't see your idea?