55 results found
-
Manufacturer description in the data mapping
It should be possible to assign the manufacturer description to the stored manufacturer in the experience worlds or at least in the categories in the description and then in the data assignment.
Since there are no global manufacturer layouts, it should at least be possible to build one with the help of the data assignment.
2 votes -
There should be an option to request Paypal payments retrospectively.
It can happen that an order is subsequently changed or the shipping costs change. In such a case, there should be a possibility to request money via Paypal afterwards.
1 vote -
Allow manipulating mail data with MailBeforeSentEvent
Currently, MailBeforeSentEvent has no setter methods to manipulate mail data.
The Symfony documentation describes such an event where one could update subject and message properties: https://symfony.com/doc/current/event_dispatcher.html#how-to-customize-a-method-behavior-without-using-inheritance
My use case is that I want to edit the mail contents. For that, I need to adjust the return value of the private method "buildContents". That seems not possible with a decorator.
A workaround is to completely replace the core MailService class:
<service id="Shopware\Core\Content\Mail\Service\MailService" class="MyPlugin\Service\MailService">
...
</service>That, however, will lead to breaking changes if the MailService class gets patched in the future.
2 votes -
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.
3 votes -
Subscriptions: Forecast
The implementation of a forecasting feature optimizes our dealers' procurement processes by calculating product demand based on existing subscriptions. This results in predictable sales through regular deliveries, supporting efficient inventory management and ordering planning.
1 vote -
Improved first-time Setup (First Run Wizard)
The revised First Run Wizard for Shopware is designed to better meet the individual needs of each merchant by dynamically adapting to specific requirements and opportunities within the ecosystem. As part of the redesign, continuous support will also be implemented, providing assistance beyond the initial setup to enable merchants to use the Shopware platform more efficiently and purposefully.
1 vote -
Make ShopwareBundle extend from Symfony AbstractBundle
https://github.com/shopware/shopware/blob/trunk/src/Core/Framework/Bundle.php#L22
It would be great if a Shopware Bundle would extend from the Symfony AbstractBundle class to be able to add bundle configuration aligned to Symfony bundles more easily. See https://symfony.com/doc/6.4/bundles/configuration.html#using-the-abstractbundle-class
1 vote -
Switch wishlist cookies to technically required section
If technically & legally possible, it would be nice if we switched the cookies required to enable the wishlist to the technically required section.
This is because most customers who visit a shop only accept the technically required cookies and then often proceed to bother the shop owners about the wishlist feature not being available.
As we all know, customers often have a hard time reading and/or use browser addons which automatically accept the minimum amount of cookies possible.
2 votes -
Company address in the documents
The company address on the documents should be on two lines. One for the street and one line for the city
2 votes -
Customers pays for features like the B2B components
Make it possible for the shop owner to monetize features that the shop owner activates for its customers, currently "only" the B2B components. The shop owner activates "quick orders" and "employee management" for the customer and the customer pays the shop owner money for this "package".
2 votes -
Delayed dispatch of the "order placed" flow
For the "placed order" flow, there should be the option of a delay, as in many cases the payment method changes shortly after the order has been placed, e.g. because purchase on account is declined or the customer changes their mind.
In these cases, the order confirmation has already been sent via this flow and the mail therefore contains the wrong payment method.
Also very important if there are different e-mail templates for the different payment methods. Here too, this often leads to a problem, which could be solved by a delay.
1 vote -
Name the next major version just "Shopware"
After the Shopware 5 era and the two different products, Shopware 5 and Shopware 6, the next version should be named just "Shopware" (version 7.0.0) to get rid of this "Shopware 5" and/or "Shopware 6" thingy. It´s just "Shopware" in a specific version in the future.
Let "Shopware 6" don´t be the next Typo 3. 😉1 vote -
Correction of incompatibility with extensions
There is currently no Shopware guideline for extension manufacturers that extensions must be compatible with each other.
If an incompatibility between two extensions becomes apparent, manufacturers should be obliged (possibly contractually) to correct this incompatibility, as customers may end up paying for both extensions.
If you are dependent on two extensions, you currently have to hope for the goodwill of the manufacturers to correct the error.
1 vote -
Back button should lead to the correct page.
If you are working in a variant and then click on the "Back to variant overview" button, you will be taken to the first page of the overview, even if you were previously on a different page.
This means that you always have to open the desired page of the overview again.
It is best to be redirected to the page from which you originally came.
3 votes -
Elle Theme: Standardized display of payment methods and shipping methods
Payment methods currently have a white frame on the main page of the store. This is not the case for shipping methods and therefore results in a different appearance.
To be recreated in the standard Elle theme.
2 votes -
LAN-152 | Country names are only translated into German and English
Used Shopware Version: 6.5.8.4
Description: We noticed that country names are only translated into German and English.
This became clear after we installed a third-party plugin (country of delivery selection).
If you select a language other than English or German, nothing can be seen in the country of delivery selection.
Previous analyses / points checked:
Looked under Settings --> Countries and noticed that the respective countries have no translation.
Environment: 6.4.20.2 until 6.5.8.4
Expected result: Afghanistan, for example, is also translated into French
Actual result: Countrys only getting translated in German and English
2 votes -
Custom field (labels) should be translatable
It should be possible to translate the additional field labels. If I tick "Maintain in all administrator languages" in the settings, I can still only translate in DE and EN.
1 vote -
Possibility to deactivate the checkbox for the privacy policy in forms
It would be nice to have an option to deactivate the checkbox for the data protection information within the forms, as is also possible via the settings during registration.
2 votes -
Deactivate the newsletter in the footer of the Showroom theme
It should be possible to deactivate the newsletter field in the footer of the Showroom theme by default without the need for any extra template customization.
This would be a useful extension for many users if it could be easily deactivated in the admin.1 vote -
Restrict renaming media
If a medium (e.g. image) is used in an article or a post, it should not be possible to rename it via "Content > Media", as otherwise the article will appear in the frontend without an image.
1 vote
- Don't see your idea?