- Forums
- :
- Core Technology - Magento 2
- :
- Magento 2.x Feature Requests and Improvements : Hot Ideas
Options
- Mark all as New
- Mark all as Read
- Float this item to the top
- Subscribe
- Bookmark
- Subscribe to RSS Feed
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Magento 2.x Feature Requests and Improvements
Do you have ideas for new features, improvements to current features, or other suggestions for Magento 2? Then share your ideas in this forum! We love hearing about ways we can improve your experience working with Magento.
Before submitting an idea, be sure to check to see if a similar request has already been posted. You can add your endorsement and comments rather than creating a duplicate submission.
To plan out changes ahead of time on site, specifically on the home page, we use scheduled changes. An issue we have come across is that there is no way to preview these scheduled changes in mobile view. A large portion of people using the mobile view not having that ability is a hindrance. While we can make these changes on Staging, and push them live to view and test, we want to be able to completely ensure that the changes made on the Production site are perfect before going Live with the changes. If we inspect the preview page and set the dimensions to mobile view, it does not reflect what will happen once the page is live. It just smooshes up the desktop version of the page and adds no responsiveness.
... View more
See more ideas labeled with:
I'm trying to create pull request for magento provider for Apache airflow. So basically it will help to connect to different systems such as AWS , azure,Salesforce etc for etl and workflows schedule and monitoring. https://github.com/apache/airflow/pull/41556 I think it will be very helpful to handle backend data operations. I need community support to accept this pull request
... View more
See more ideas labeled with:
Currently the addresses are connected to Users. Using B2B features, can happen that all users belonging to the same company would use the same addresses. Currently we have to duplicate all addresses for all users of the same company. We would like to connect addresses also to the company entity so that are available for all users of that company.
... View more
History We started our first Magento Cloud project in 2019 and both Magento and us received several complaints about the bad performance (slow response-times of non-cached requests) from that customer back then. We did several other Magento/Adobe Commerce projects since 2019, some hosted on Magento cloud, others hosted on different infrastructure solutions, which included custom multi-node AWS-setups and single-node setups. Over all those years we started several attempts to optimize both the code-base of the projects and the configuration of the Magento Cloud infrastructure, which brought some improvements, but the resulting performance never came close to the one of the single-node setups that were used by most of projects. By numbers we are calculating an average of 2.5-times the response-time for Magento-Cloud projects compared to projects hosted e.g. on a single https://www.hetzner.com/dedicated-rootserver/ax102/ Current situation We received another complaint from a customer, again optimized the code-base and Magento-Cloud configuration, but also came up with our own considerations regarding the Magento Cloud infrastructure in general. We initially raised those requests at our onboarding team, the customer's suggest manager, were forwarded to the support, which forwarded us to this section of the forum at the end. Considerations Overall architecture To our knowledge the usage of a Magento Cloud infrastructure always implies the use of at least 3 different nodes on 3 different availability-zones. (Visual representation: https://experienceleague.adobe.com/docs/commerce-cloud-service/assets/az-stack-diagram.png?lang=en) From several cloud-projects (AWS and Magento Cloud) we also learned that the usage of several nodes/servers for the different services increases the over-all response time, as network-latencies are introduced into the communication between the application and its services and the replication of the data between the same service on the different service-nodes. Those network-latencies are even worse, if the the different nodes are distributed over several availability-zones. Is there a possibility to drop either the 3-node architecture, or at the least the use of different availability zones? We are aware that this would reduce the redundancy of such a setup, but from the feedback of our customers a better performance would be more important to them then the redundancy currently offered. An a number of those customers do not have the high number of traffic-volume that would require a multi-node setup. Type of CPU For our current customer executing a cat /proc/cpuinfo on one of the cloud-environments reveals the following data: model name : Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz cpu MHz : 2095.081 So Magento Cloud currently provides a CPU that was released back in 2017 and has only a CPU clock speed of 2.1 GHz. Whereas a hosting-option from another hoster (https://www.hetzner.com/dedicated-rootserver/ax102/) would give us a AMD Ryzen™ 9 7950X3D (from 2023) with 4.2 GHz. And yes, we are aware that the most recent hardware is not available at every location of AWS or Azure, but at least more recent hardware with higher CPU clock speed would be available at both of those provided, some of it even for cheaper prices than the hardware currently provided. https://learn.microsoft.com/de-de/azure/virtual-machines/linux/compute-benchmark-scores#hbv3 Is there a chance to get more recent hardware for our Magento Cloud customers?
... View more
See more ideas labeled with:
Given that the current invoice, shipment and credit memo PDFs look the same as in Magento 1 and PDF's are always a bit of a nightmare to customize for the merchants: I suggest to replace the PDFs with a html2pdf tool. Actually the preview of the invoice looks already really nice in the backend, so this could just be converted to pdf. This would maybe also help the problem Hirokazu Nishi mentioned in his tweet: "Magento2 still use LinLibertine font. It’s only for Alphabets. To change PDF font, we still have to rewrite some classes..." This idea resulted from a tweet/discussion here: https://twitter.com/hirokazu_nishi/status/770282916819578881 https://twitter.com/rescueAnn/status/770338589326635008 https://twitter.com/benmarks/status/770339381995384832
... View more
See more ideas labeled with:
Hello everyone, I'm experiencing slow performance on my Magento website, and I'm seeking advice on how to resolve it. Pages take a long time to load, and navigating between different sections feels sluggish. I would appreciate any suggestions or tips to improve the performance of my Magento website. Thank you!
... View more
See more ideas labeled with:
Hi everyone,
In most of the pages in Magento, we can find the "State/Province" before the "Country" field. Since the "State/Province" depends on the country, that is confusing since the customer has go to next field and select the country, and then go back to the previous field and select the state/province.
This is not correct in the most important page in the storefront, the onepage checkout:
And you can also see the wrong order in some pages of the admin panel:
In other pages, like the shopping cart page, the order is correct:
It would be better if the country can be selected first, then the state/province and finally the ZIP/Postal Code (just like the shopping cart page).
... View more
See more ideas labeled with:
The current Adobe Live Search implementation doesn't currently support adding translations. The only current way to add translations to the Search Popover "View All" and "Suggestions" labeling is to use CSS (as provided as a temp solution by the Adobe Support team). This is not an accessible friendly approach. The desire would be to replace the text within the label. Being able to translate within the i18n CSV files where most translations are defined would be best.
... View more
See more ideas labeled with:
There is a Best Seller report that business is highlight certain products using the label. This option is available in the admin panel under Reports > Products > Best Sellers Currently, the data supports daily, monthly and yearly timeline.
... View more
See more ideas labeled with:
Status:
Investigating
Submitted on
08-30-2016
01:10 PM
Submitted by
apiuser
on
08-30-2016
01:10 PM
Feature request from CRYX2, posted on GitHub Sep 16, 2015
Hello, I've not found any options to use multiple selection (for the same attribute) for layered navigation. In Magento 1 this options was very frustrating, now is implemented?
... View more
In the EU a Gift card (single-purpose voucher) has to be sold with tax applied to it - in other words, gift cards are taxable products also before they are redeemed. Example: A gift card with the face value of €100 including. tax, will be €80 excluding tax at a rate at 25%. The Gift Card has to be sold at €100 including. tax. It is required by law in the EU to sell Gift Cards incl. tax and this can't be configured with the current configurations available in the Commerce Gift Card module. Commerce Gift Card product type does not have an option for setting it to use a Tax Class: https://docs.magento.com/user-guide/customers/account-dashboard-gift-cards.html https://docs.magento.com/user-guide/configuration/sales/tax.html https://docs.magento.com/user-guide/configuration/sales/gift-cards.html (Not to be confused with “Tax Class for Gift Options” which is another functionality) Example resources: https://erply.com/all-that-you-need-to-know-about-taxation-of-gift-cards-in-eu/ https://www2.deloitte.com/ie/en/pages/tax/articles/vouchers-new-vat-rules.html
... View more
It would be helpful if Magento supported the direct integration of Google Analytcs 4. As is currently possible under Stores-> Sales -> Google Api for GTM and Universal Analytics.
... View more
See more ideas labeled with:
when a product creation fails it still creates the media items but doesnt clean them up
... View more
Currently in 2.4+, the process of applying category rules requires a manual save of each category. This is extremely time consuming for a store that has a lot of categories and also could severely impact the cache if done during business hours. These rules should be applied automatically or at least on a schedule. A bonus would be to do this in a cache-preserving way.
... View more
See more ideas labeled with:
When working with B2B, it is not uncommon for the customer to place large quantities in the basket. In addition to this, it has been noted that certain parts of the site, most notably the checkout, tend to slow down in relation to the amount of items that are added to the basket. The more items added, the slower certain areas become. We suggest refining the code in order to facilitate a large basket quantity, upwards of 200 perhaps, without losing to much time waiting for reloads. Specifically, the more items in the cart, the slower the following seems to process: /Webapi/Rest/Magento\Checkout\Api\TotalsInformationManagementInterface/calculate /checkout/sidebar/updateItemQty /checkout/cart/updatePost /checkout/cart/add /checkout/cart/delete /checkout/sidebar/removeItem
... View more
One big issue I find when working with UI Components is that you end up writing deeply nested xml trees. These quickly become hard to read, and are really unmanageable. I'd like to propose two new XML nodes to be introduced: alias and referenceAlias. These would provide a mechanism for reducing the amount of XML I need to write and manage when working with nested components. Consider the following: <?xml version="1.0"?>
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
<body>
<referenceBlock name="checkout.root">
<arguments>
<argument name="jsLayout" xsi:type="array">
<item name="components" xsi:type="array">
<item name="checkout" xsi:type="array">
<item name="children" xsi:type="array">
<item name="steps" xsi:type="array">
<item name="children" xsi:type="array">
<item name="shipping-step" xsi:type="array">
<item name="children" xsi:type="array">
<item name="shippingAddress" xsi:type="array">
<item name="component" xsi:type="string">Ashsmith_Checkout/js/view/shipping</item>
</item>
</item>
</item>
</item>
</item>
</item>
</item>
</item>
</argument>
</arguments>
</referenceBlock>
</body>
</page> It's deeply nested, and all to common when all you want to do is replace a component or alter it's configuration in some way. The alias and referenceAlias solution would result in XML that looks like this: <?xml version="1.0"?>
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
<body>
<alias name=checkout_step_shipping_address path=“checkout.root/arguments/jsLayout/components/checkout/children/steps/children/shipping-step/children/shippingAddress” />
<referenceAlias name="checkout_step_shipping_address">
<item name="component" xsi:type="string">Ashsmith_Checkout/js/view/shipping</item>
</referenceAlias>
</body>
</page> Immediately we have less depth, and can still get the job done. Our XML is easier to read and can be quickly understood by anyone jumping in. Furthermore, these aliases could be defined by the Magento core. They would serve as invaluable extension points for developers. Even better this feature request would not introduce any breaking changes. I go over this in a little more detail (and my reasoning behind it) over on my blog: www.ashsmith.io/magento2/suggestions-to-improve-ui-components/
... View more
See more ideas labeled with:
Feature request from acidreian666, posted on GitHub Jul 15, 2016
Steps to reproduce
Install Magento 2.1.zip from magento.com
Add Click Add Simple Product.
Click Advanced Pricing.
Expected result
Display a Textbox for MSRP.
Special Price
Special Price From
Cost
Tier Price
--
Actual result
--
Special Price
Special Price From
Cost
Tier Price
Missing MSRP input Textbox.
changing location of MSRP under Default Attribute set from Advanced Pricing to something else End result nothing still not showing up under any Group within "Add New Product"
Sorry if this is a duplicate I searched but i feel I'm the only person experiencing this.
... View more
Feature request from darrenjennings, posted on GitHub Oct 23, 2016
On latest mangeto version, would love to see TinyMCE upgraded and maintained since Magento is several versions behind latest TinyMCE. https://www.tinymce.com/
Newest version should include integration with image uploading/resizing/editing, magento widget/variable insertion etc.
I've attempted to upgrade the core myself so as to offer a PR, but it broke too many things along the way. :)
... View more
Status:
Investigating
Submitted on
08-30-2016
12:31 PM
Submitted by
apiuser
on
08-30-2016
12:31 PM
Feature request from erikhansen, posted on GitHub Jan 07, 2016
This issue covers what I consider to be two major usability issues with messages:
1. Error message hides after 5 seconds
When error messages are displayed on the frontend, they disappear after 5 seconds (this is controlled by the onHiddenChange method in app/code/Magento/Ui/view/frontend/web/js/view/messages.js ). If a user is not paying attention, if they are a slow reader, or if the error message is long, they message may disappear before they read the entire message. My recommendation would be to NOT hide the message but to leave it on the page until the user takes some other action that causes the message to be hidden.
Here is an example of an error message that will hide after 5 seconds:
@mttjohnson did some digging into what happens when there is an error with a payment method in the checkout process. It looks like the payment methods use the Magento_Ui/js/modal/alert component to display an alert-style modal that doesn't go away until the user closes it. The red error message I displayed above occurs when there is an exception thrown by Magento when progressing from Shipping > Billing, so it may not warrant an alert style popup, but it should at least persist on the page and not hide. This is what the alert-style popup looks like:
2. Error messages may display outside of current viewport
If a user is a on a small screen device, there are many situations where they will never see an error message. For example, if they're on the "Shipping" step of the checkout process and an error message is added, they may not see the error message get added to the top of the page. My suggestion would be to either smooth scroll the user up to the error message, display the error message next to the button they used to submit, or come up with a notification system that display notifications on top of all content.
... View more
Status:
Investigating
Submitted on
08-30-2016
12:37 PM
Submitted by
apiuser
on
08-30-2016
12:37 PM
Feature request from tanya-soroka, posted on GitHub Jan 17, 2014
Multi-node inventory
Multi-node inventory functionality will introduce support for multiple warehouses, management of product stock per website and warehouse, order processing through drop shippers and vendors. It will allow set up of multiple shipping origins, flexible shipping configurations, and automatic vendor notifications.
Functional Requirements
Ability to enable/disable shipping from multiple addresses (either you’re your business address or from 3rd party warehouses and suppliers)
Ability to specify the addresses of these warehouses/suppliers
Ability to assign products to different warehouses/suppliers
Ability to manage stocks in different warehouses
Ability to specify preferences for picking up products from warehouses
Ability to automatically define nearest warehouse to customer's destination
Ability to notify warehouse/supplier upon order and/or invoice creation
Ability to create/update email templates to be sent to warehouses/suppliers
Ability to see products assigned to selected warehouse
Ability to see shipments from selected warehouse
Inventory per Website
Provides ability to:
Set up a QTY attributes per website
Specify different inventory levels for each website
Track inventory level for each website
Track low stock for each website
Get a total QTY of the product
This feature entails the following changes:
General settings of inventory Scope should be available under Configuration > Catalog > Inventory Section
Additional rows on Product QTY of Product Grid (for products which are using inventory option)
Updates of Low Stock report
Warehouse Settings
It should be possible to enable and set up Multi-node inventory functionality. As a merchant, I want to have the following options:
Enable/Disable service
Show warehouse information on product page, shopping cart, checkout process, order/invoice/shipment/refund
Select any enabled Shipping service/method per warehouse
Manage Warehouses
The Manage Warehouses tab should appear under System > Store set upon a primary menu. It should contain the following action:
Create / Edit / Delete a new Warehouse.
Filter and search data of Warehouse list.
Provide general information about a warehouse: title and address.
Mass action, such as delete and update.
Admin user should have ability to specify the following warehouse data:
Warehouse contact information and Address
List of assigned Products
Shipping methods data
Sales data (Shipment, Orders, etc.)
Managing Inventory per Product
Alternatively, admin user should be able to specify warehouse/supplier data on the Product Information page and manage inventory per each warehouse individually.
The QTY field of the Inventory section (i.e. general quantity of a product) should display the sum of the numbers entered to the QTY fields per warehouses. It be set for read-only purposes.
Shipping / Delivery Configuration
Store owner should be able to select a shipping method from existing list of vendors (USPS, USP, DHL, FedEx, etc.). Additionally, one can set up a custom shipping method (Drop-shipping) per warehouse. Configuration settings, delivery fee, and delivery time are required on global/warehouse level.
Admin user should have ability to specify ship/delivery option for products from warehouse(s):
Shipping from a nearest warehouse (closest to customer's area)
** When a product that is assigned to multiple warehouses is added to the cart, the nearest warehouse is selected for delivery. Otherwise, product should be delivered from next nearest warehouse where it is available
Shipping from a warehouses with the highest priority
** When a product that is assigned to multiple warehouses is added to the cart, the warehouse with highest priority is selected for delivery. Other warehouses are selected according to the specified priority.
Checkout
Once multi-inventory functionality is enabled, the following delivery scenario should apply:
When ordered product is assigned to a warehouse, the address of a warehouse is considered as a pick-up address for the shipping service provider. Shipping rate to be calculated accordingly.
When ordered product is not assigned to a warehouse, the store address is considered as a pick-up address for the shipping service provider. The shipping rate is to be calculated accordingly.
When ordered products are assigned to multiple warehouses, multiple orders are created. Address of appropriate warehouse is considered as pick-up address for shipping service provider to each of the orders. The shipping rate is to be calculated accordingly for each created order.
Returning Items Assigned to Different Warehouses
Store address to be the return address for products. If Automatically Return Credit Memo Item to Stock feature is enabled, the returned items should affect the general quantity of the product and appropriate Warehouse should be considered as place of their storage.
Displaying the Warehouse/Supplier Information on the Order Review Page in Backend
Order View page should display warehouse/supplier information for every ordered product. The same data should be also displayed on the Invoice, Credit Memo and Shipment pages.
Products should be displayed on separate rows in case these products will be delivered from multiple warehouses.
Notifying Warehouse/Supplier Upon Creation of an Order in Backend
Admin user should be able to manage their notifications. Notifications can be configured to be sent per warehouse when an order/invoice/refund is created.
Creating Email Template for a Warehouse/Supplier
By default, email to a warehouse/supplier should contain all product details (i.e. product name, product parameters, quantity of each item, tracking information, and shipping method details). However, admin user should be able to create their own templates. There it should be ability possible to specify email template that will be used for sending a notification (per warehouse or globally).
Tax Calculation
Depending on tax configuration and local tax laws, tax may be collected for products shipped from a warehouse location and should be included when an order is placed.
Reports
Warehouse data should be updated with reports about Sales and Products, like Orders, Shipment, Low Stock and etc.
... View more
© 2019 Magento, Inc. All rights reserved.