82 results found
-
Replace Webpack with Vite in Shopware Administration Panel
Switching from Webpack to Vite in the Shopware Administration Panel would significantly improve development speed and the developer experience. Vite offers faster builds, better HMR (Hot Module Replacement), and modern JavaScript tooling. Its optimized build process and plugin ecosystem make it a future-proof choice for modern frontend development.
By adopting Vite, Shopware developers would benefit from shorter feedback loops during development and an overall more efficient and enjoyable workflow. Additionally, it aligns Shopware with the latest frontend development trends, ensuring continued relevance and appeal to a broader developer community.
7 votes -
Further information on a licence warning
If a licence warning is issued for an extension, only the external IP address is transmitted as the source. If there are 100 shops behind the same IP, the ‘faulty’ shop cannot be found as a result.
More meaningful details should also be transmitted (e.g. shop name, internal IP, unique shop properties).
3 votes -
Remove password prompt on "Your profile" edits (Language, Time zone)
When changing language or time zone under “Your profile” one is asked to confirm the current password. This is one of the very few locations where the password is asked for and while it may make sense for e-mail and password changes, language and time zone are more inconsequential (especially compared to what an admin account can do to a shop without ever being asked for a password)
2 votes -
Loading times of the article sliders
The article sliders currently take about one second to load properly. Until then, the first product of the slider is usually displayed briefly in large format.
An optimization of the loading time for article sliders with many products would be desirable.3 votes -
List all assignments of a Dynamic Product Group
EN
In the Rule Builder, there is an overview with the assignments for each rule. Such an overview would also be a great addition for the dynamic product groups, because the more product groups are used in categories, product comparisons, cross-selling etc., the more difficult it becomes to determine where a particular product group is used.DE
Im Rule Builder gibt es für jede Regel eine Übersicht mit den Zuordnungen. Eine solche Übersicht wäre auch für die Dynamischen Produktgruppen eine super Ergänzung, denn je mehr Produktgruppen in Kategorien, Producktvergleichn, Cross Sellings etc. zum Einsatz kommen, um so schwieriger wird es…2 votes -
Uninstallation via cli should delete the folder of an uninstalled extension
If an extension is uninstalled via cli, the folder in plugins is not removed. This may lead to incorrect licence warnings. The folder should therefore also be deleted when uninstalling.
1 vote -
Whitelist-Based Cache Key Handling for URL Parameters
Currently, Shopware allows excluding certain URL parameters from the cache key to save storage. However, this exclusion list keeps growing, making maintenance cumbersome. Instead of excluding parameters, a whitelist approach could offer more control and efficiency.
Analysis:
I tracked URL parameters in a default Shopware installation—from listing to PDP, filtering, and placing an order. These 19 parameters were captured (more possible):
cluster, keys, language, limit, locale, manufacturer, max-price, min-price, no-aggregations, order, orderId, p, paid, properties, rating, redirected, slots, timezone, searchInstead of maintaining an ever-growing exclusion list, switching to an allowlist approach would ensure that only essential parameters impact the…
1 vote -
Form Builder: send filled form to customer mail address in CC
If a customer filled the form and send to the merchant, the customer should get a copy of the filled form in CC.
7 votes -
Custom fields - floating point only with two decimal places
In the custom fields I can select "number" and then choose between integer and floating point number. However, when using a floating point number, my input is rounded to 2 decimal places. This should be adjustable in the admin if you need more than 2.
3 votes -
Optimise enlargement of product images
The product image should be possible by spreading the thumb and index finger. The entire form currently reacts to this.
This problem only occurs in our Shopware 6 shop. Our Shopware 5 shops all react correctly at this point. We urgently need an adjustment here.
2 votes -
Accidental up / down due to slipping during the gesture should be prevented.
Since Shopware 6 there is a problem (not within our Shopware 5 shops) that when swiping to scroll the images (product slider) it is no longer excluded that the form scrolls up or down in the wrong direction if accidentally moved.
This problem does not exist with our Shopware 5 shops, but only with our Shopware 6 shop.
The aim is to prevent the form from accidentally scrolling up or down when scrolling between images.
2 votes -
Make headless sales channel non-deletable
There are always support tickets where the customer has deleted the headless sales channel and the store is therefore no longer accessible.
As there is no conceivable reason for deleting the headless channel and this happens again and again with customers, resulting in support tickets, this option should be removed.
3 votes -
Custom product attributes are transmitted individually to Google Analytics
If Google Analytics is used for ads, the attributes of custom products are transmitted as individual items. This can quickly become overwhelming. A checkbox, for example, to group the attributes could be an option.
2 votes -
Rendering Mailtemplate
When an email template is customized, it's possible that certain objects cannot have a "null" value. If this occurs, the email template will not be sent, and no error message will be logged. This leads to additional analysis effort.
3 votes -
API: Status of E-Mail
Setzen der Status der einer E-Mail versand/nicht versandt nach Dokumentart an der Bestellung per API
Set the status of an email sent/not sent by document type on the order via API
2 votes -
Query data from Shopware Analytics
It would be good if the data from Shopware Analytics could be accessed via the API in order to integrate it into Grafana, for example.
1 vote -
It should be possible to prevent customers without a Paypal account from buying something via Paypal.
If you enter an email address in the Paypal login window that is not registered with Paypal, you can still be paid via Paypal by direct debit. It should be possible to prevent this.
1 vote -
Calculation of shipping costs for panels
I need a shipping condition. In Shopware I can choose between certain shopping cart properties (number of products, shopping cart value, shopping cart volume or shopping cart weight) or a rule from the rule builder. Using the rules from the rule builder, I can then, for example, go and say: If at least one of the products in the shopping cart is longer than 3m (whether it says metres or millimetres is not the issue here) and the weight is less than 30 kg, charge €10 shipping costs, if it is less than 50 kg, charge €20 shipping costs, etc.…
2 votes -
Rule Builder Rules for tax
There are special cases where the customer has to pay a different tax rate based on the zip code, for example. There is currently no way to use a rule to check which tax rate should be charged in such cases.
Such an option would be desirable for customers1 vote -
Rule for checking product availability
So far there are rules for checking the stock of a product. However, it would be useful to have a rule that checks whether the number of products in the shopping cart exceeds the number of available stock.
Customers could use this rule to check whether the order is really covered by the current stock or whether the number of products ordered exceeds the stock.
This is relevant for the availability of express shipping, for example.1 vote
- Don't see your idea?