114 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/5902 votes -
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
2 votes -
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 -
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 -
Remove Admin Worker - CLI Worker as Default
Get rid of the admin worker and use cli worker as default.
20 votes -
Rule-based activation of "B2B Component" features
As a shop owner, I want to be able to activate B2B features for specific customers based on rules. For example, all customers from the customer group "B2B" can use "Quick orders" and "Order lists".
6 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 -
Native DeepL support
Native DeepL support for automate translation everything in shopware: products, shopping experiences, content pages, forms etc.
3 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 -
Fallback product-layout if NO Layout is assigned
If the values for columns
cms_page_idandcmsPagewithin tableproductwill 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 -
Possibility to tag/group and filter rules
We currently have 3 sales channels which all work a bit different regarding their sales and payment rules. In addition we will be using promotions extensively. This means that our rule builder is slowly but surely building up with rules and hard to manage. It would be good to be able to flag or group rules and sort / filter them accordingly. Right now we manage with a naming convention, but that's not ideal.
3 votes -
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 -
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
- Don't see your idea?