Magento 2.x Feature Requests and Improvements

We have a Adobe Commerce Instance with multi brand and multi country stores, and we share the same product catalogo accros de stores and also the same category tree.   And we need the feature to sort products on the categories in the diferent way for each website.   For example we have the website A and de website B in the same instance, and we have the same category tree for these two website and also share the same products.   We need sort the products on category TVs, and we have the procuts with codes 10001 and 10002, we need put first the product  10001 for the website A, and put first the product 10002 for the website B.   Now the sort on categories is global.   If you need more information please let me know.   Thank you. ... View more

Hi, I am facing a problem with configurable products. If you create a configurable product and create some product variations based on lets say color & size, if you change the price and image for a specific variation and select this variation on the configurable product page, the price and image will change. This is a very good feature altough the expected behaviour for me would be that the description and specifications for this selected variation would be shown, in stead of the specifications of the configurable product itself. Why does it change the price and image, but not the description and product specifications? I attached a screenshot to give you an idea of the issue. I also used to have this problem in Magento 1 and found a module for this which solved the problem. However this module is not supported for Magento 2. https://www.magentocommerce.com/magento-connect/sdocp-simple-details-on-configurable-products-1.html Is there a way this can be done programmatically or fixed in the core?   Kind regards, Falco ... View more

Broadly speaking, there is a few different ways of expressing application state in such a way that it's useful debugging:   Logs (implemented in M2 with the excellent psr/log interface) Time series data (also known as metrics). Things like Data Dog, Promethiums, Sensu and so on. Traces; primarily expressed by opentracing.io, but also Zipkin, Lightstep  This feature request is to track the implementation of #2; the expression of time series data in the application, as well as the export of this data via whatever mechanism might be setup to receive it.   Time series data exposed by an application can provide extremely rapid feedback on an applications performance. This information can be used for a number of useful processes such as: Allowing infrastructure to make decisions around whether to modify the applications runtime environment Debugging the application performance during runtime Alerting when an application violates it's SLO Note: I am doing some work on this with PHP more generally tracked on github. Best place to contrib beyond core support is there.   There is currently no simple way to express such time series data in Magento. There are several efforts that have been done to implement this in a third party, vendor specific way including:   https://github.com/sitewards/magento-prometheus https://github.com/magento-hackathon/Hackathon_Datadog https://newrelic.com/partner/magento https://github.com/janpapenbrock/magento-statsd However, these suffer form a few drawbacks. In particular,    There is no standard API (such as the psr/log api) that can be invoked in third party extensions reliably It locks the users into a hosting infrastructure; undesirable for the continuity of the project. Additionally, there are various metrics that would prove extremely useful when debugging Magento:   Cache hit rates (https://github.com/magento/magento2/issues/11151) Cron metrics, such as last execution per job, queue length etc. Indexer status (expressed as 1 or 0) Cache enabled status (expressed as 1 or 0) Cache invalidations issued Orders in various states (processing, shipped etc) Customer logins (aggregate, not per customers) HTTP status codes However, the utilities aren't limited to the above. In particular, third party code often has reason to express it's health (such as the code developed by an agency) to ensure custom logic is functioning correctly, and that a feature is delivering sufficient value to jusify it's cost.   General Background     It is suggested the implementer have some experience implementing and using application instrumentation. There is a body of knowledge in this area that is immense of it's own right, and not a task that is so simple.   Beyond that, the goal of the work should be to checkpoint the data, but defer all processing to the implementing time series databases. It should also have minimal impact on performance. Lastly, high cardinarily data can be expressed through logs or traces, and is perhaps not something that is easily expressed by time series metrics (though honeycomb et. al would beg to differ)   Primitives     The open source monitoring package Prometheus expresses the primitives: counter gauge histograma summary  The author has implemented this in several places, and has found uses for counter and gauge in a repeated way, as well as a limited use for histogram. To begin, the implementation of "guage" and "counter" would be amply sufficient to justify the majority of cases. This is supported by both Prometheus and DataDog, and it's presumed the majority of time series databases.   Non Goals   It should not be a goal of this work to implement the metrics view in Magento. This can be approached as a separate task, but the primary intent of this work is to express time series data in such a way it can be consumed by third party services.   It should not be a goal of this work to track the time associated with the time series data. The sampling is left to the third party application implementations.   It should not be a goal of this work to instrument third party applications (redis). They have their own implementations, and should be considered separate services.    It's unclear whether instrumenting the PHP runtime itself would be beneficial, though this can likely be handled in the bespoke cases it's required by third party utilisation of the above library.   Interface   Ideally there should be an interface similar to the psr/log exposed that allows the checkpointing of metrics. Something like:     <?php class Foo { private $oMetricRegistry; /** * Dependencies automagically wired by DI */ public function __construct( // Singleton injected that stores the metrics. Invariably a global, persists towards the end of the request \Magento\Framework\Metrics $oMetricRegistry ) { $this->oMetricRegistry; // Ensure the metric exists. This operation is an idempotent "create if not exists" type operation. $this->oMetricRegistry->register( // metric identifier 'vendor_extension_foo_thing', // metric type. Can be one of "count" or "gauge"; potentially "histogram". 'count', // label keys. Labels are mechanisms to slice time series data, supported by both data dog and prometheus [ 'attribute' ] ); } public function doThing() { // An operation changing the state of the metric. In this case, an increment -- it's a count. $this->oMetricRegistry->increment( // The metric identifier 'vendor_extension_foo_thing', // The label values. ['value'] ); } } This would allow an extremely simple API to quickly expose the data for ingestion into time series.   Storage   Ideally, the storage engine should be pluggable, but implement:   APCu In Memory (or "null" when considering parity with psr/log) Redis MySQL This would cater the wide range of hosting constraints that Magento can operate with, with a predisposition for not changing exising behaviour (checkpoint to memory but flush at the end of each request)   Exposition   There are various ways that the data may be exposed. It's suggested the core team deliberately not support any mechanim (except perhaps a native admin panel one, expressed as separate work). Instead, rely on third party / community vendors to provide the required libraries, similar to psr/log.   Broader PHP community involvement     It is the authors hope that this conversation is extended to the broader PHP community, perhasp through the involvement in FIG. A single interface for time series data would have ramifications for the langauge more generally.   Future Work   Once implemented, Magento's introspectability could be extended further by implementing traces.   Related Reading: http://www.brendangregg.com/usemethod.html https://prometheus.io/docs/introduction/overview/ https://github.com/DataDog/php-datadogstatsd https://github.com/Jimdo/prometheus_client_php   ... View more

Hello, I believe this is more of a question than a suggestion. Amasty adds a block with technical information in the admin area (see below). Is it safe? Is it possible to add it to vanilla Magento to avoid every extension vendor adding this information? Access control would be more convenient to set up to one page rather than many. ... View more

Feature request from aleron75, posted on GitHub May 10, 2016 Hi, this is not something which doesn't work but something that doesn't work as expected, so feel free to take it more as a suggestion than as a bug. As stated in the title, I expected dates saved in UTC just like in Magento 1 but it doesn't seem to work this way in Magento 2. What's more, the \Magento\Eav\Model\Entity\Attribute\Backend\Time\Created and \Magento\Eav\Model\Entity\Attribute\Backend\Time\Updated attribute backend models don't seem to have the same logic implemented (even if I don't think that any default attribute use them at date). You can read some considerations and suggestions here: http://magento.stackexchange.com/questions/114706/magento-2-best-practice-to-get-current-date Thank you ... View more

Feature request from tadhgbowe, posted on GitHub Nov 30, 2015 I am creating a new Configurable product via the Admin Panel (based on color). My simple products (children) already exist via a product import. When I click on "Edit Configurations" it takes me down the path of creating new simple variations. I don't want to do this. I simply want to select the existing products. Interestingly if I go ahead and generate some simple variations via the "Edit Configurations" after the product save I can see a new link "Add Products Manually" beside "Edit Configurations". That's what I want to see the first time around after I inform it that the new configurable product is based on color. The "Edit Configurations" wizard needs to allow me to select existing products after I've told it what configurable attributes I'm working with e.g. color or size. Is this a known issue? Thanks Tadhg ... View more

Feature request from webtekindo, posted on GitHub Feb 10, 2016 It should be nice to have an option in Admin to display price range for configurable products instead of only displaying the minimal price. 50$ - 90$ (minimal price) - (maximal price) That range may be display on the product listing, and on the product page when no options selected yet I beleive many companies have use cases on which they use the configurable product type, but price may vary a lot depending on the configurable options. ... View more

Feature request from hostep, posted on GitHub Aug 17, 2015 Hi guys Why is the telephone number still required on a customer address? We hear from our shop owners that a lot of customers refuse to enter something in there or just enter gibberish. An ideal solution would be if you could add a configuration option in the backend similar to the Gender , Tax/Vat Number and Date of Birth fields. So an option for showing the telephone number where you can choose between No , Optional or Required . What do you think? I had to implement this today into a Magento CE 1.x store and it was kind of a terrible experience, changing stuff in the database, remove the hard coded validation of that field (which is still present btw: https://github.com/magento/magento2/blob/93312cae42824274722fe7a285d5ce8e40f177a1/app/code/Magento/Customer/Model/Address/AbstractAddress.php#L572), ... Related to https://github.com/magento/magento2/issues/624 ... View more

A big restriction in Magento is that it is not possible to use store view codes multiple times for different stores / websites.   For example this should be possible:   www.store1.com/en www.store1.com/de www.store1.com/nl   www.store2.com/en www.store2.com/de www.store2.com/nl   www.store3.com/en www.store3.com/de www.store3.com/nl   But this is not possible, because the store view code must be unique.   Now we have to do something like this:   www.store1.com/en www.store1.com/de www.store1.com/nl   www.store2.com/eng www.store2.com/deu www.store2.com/nld   www.store3.com/l_en www.store3.com/l_de www.store3.com/l_nl   And this just doesn't make sense. It would be nice to have the possibility to use store view codes across different websites / stores. Or to rewrite the storeview codes on the frontend, something like this:   code - rewrite to eng - en fra - fr deu - fr   english - en  french - fr german - de ... View more

We need an alternative to the customer email login which is phone number login. It may not sound useful in Western countries but in China, it's necessary. Chinese people only use this login method with Taobao (taobao.com), Tmall (tmall.com) or JD (jd.com), they are used to it.   Without this basic option, Magento 2 will never make it in China.   ... View more

When managing attribute and attribute set data via the REST API, all the endpoints required to create a complete attribute set with attribute groups and attributes assigned to that set and those groups are present and available.   However, the reverse is not true. There is an endpoint missing in retrieving all of this data for an already existing attribute set. Specifically, the attribute group that each attribute in an attribute set belongs to. Attributes for an attribute set are retrieved by set and do not contain the attribute group they are present in either. This is largely obstructive to the process of fully and bi-directionally integrating the attribute set system with an external source.   In short, include the ID of the attribute group that an attribute belongs to in the returned JSON when listing attributes in an attribute set using the REST API. (Or otherwise include an endpoint that would make this information available). ... View more

Our payment partner - Adyen offers a feature to see which browser a customer used to make a purchase, so long as the order was made using their Card services.    For other standalone payment methods such as Amazon Pay and PayPal; I would like to suggest an information box within the order history for the admins benefit only, so that we may track which Browser a person used to complete an order and monitor whether a certain browser and/or version is causing errors or failing to track conversions within Bing or Google.    The idea came from the information found in our Adyen control panel.     ... View more

For some reason, page builder does not let you add image alt tags to images when you are adding in background images via page builder. Not having image alt tags is a bad practice for numerous reasons ... View more

We are having an issue with how GA 360 is reporting revenue when a line level discount is applied to an order. The example shared in a support ticket shows how a basic Magento store setup is reflecting the problem, so the bug is built in to the out-of-the-box instance of Magento Commerce. In our site's case, we have a more customized Cart setup but the problem is the same. As a result, GA is reflecting all of our Revenue reporting incorrectly.   It doesn't appear that I can attach a file here, so a more detailed explanation is as follows.  When a customer uses a coupon which applies a discount to 1 of say 3 products in their cart, the GA purchase event records the product price to be the original price.  This should be recording the updated, discounted price.  We are able to confirm that this discounted price is available in the "Row Total" Magento field.  So the data is there for the taking.  Our request is that Magento use the Row Total amount in the corresponding GA events for Product Price.   Business Impact: all of our discount revenue tracking on products is wildly different.  This impacts our ability to read the success of campaigns and requires a great deal of manual effort to adjust for the error.  Please correct!!! ... View more

In Page Builder, when selecting images, the tiled view is acceptable until you have a lot of images in a single folder.  Another view option, list / details, would be optimal here.  This would allow you to see the full file name, size, type, etc. and allow for sorting on any of the columns. ... View more

Feature request from paales, posted on GitHub Jul 31, 2016 I just added 19 products to my category. The frontend doesn't show any products. It would be really helpful to give a hint why a product isn't visible on the shop. (After being a Magento developer for years, I still struggle with such a basic thing..) In an effort to improve the usability of the system and greatly improve the merchant experience, context aware hints are crucial. Explain what is going on and how should the merchant fix their 'mistakes'. The idea is to add a visibility-helper-icon to product grids so that it is clear why products aren't shown and suggestions how to fix this. With this, we can collapse the Visibility, Status and maybe Websites column into one 'Visibility Helper' column (or just an icon behind the name of the product). The visibility helper icon will have a popover with additional information why this is happening: Not visible: Icon: http://fontawesome.io/icon/eye-slash/ Product isn't visible anywhere //one or more applicable Product is disabled [Enable Product] Inventory is set to 0 [Set inventory] //when the setting is enabled Product is set to Not Visible Individually and isn't part of a composite product [Make visible] Product is set to Catalog but isn't connected to a visible category Limited The product has limited visibility Product is set to Not Visible Individually but part of a composite product. Product is set to Search [Set Catalog Search] OR Product is set to Catalog, Search but isn't attached to a visible category. [Add Category] Product is set to Visibility: Catalog but isn't connected to a visible category [Assign to Category] Visible Conditions: The above conditions don't match Tooltip: Gives a link to the category and product view page. Questions: How are we going to handle store view / website specific values without having huge popovers? Might it be a good idea to include salable information as well? ... View more

Say, we have setup a factory role, how to hidden customers emails for this factor administration role, and disallow factory to see all customers emails, please? ... View more

Currently PWA Studio supports Braintree payments out of the box in its Venia storefront implementation. It will be great if it can support all the payment methods which comes by default with luma theme.    Here I am requesting to have Purchase order payment method compatible with PWA studio in native magento.   Thank you! ... View more

We need to use the Quick Order functionality for the Venia theme but this is not available for Venia theme. This functionality is only compatible with luma theme.   As this is a core feature available for Adobe commerce, hence the expectation is we should be able to use if we are going with pwa (venia).   Ref - https://experienceleague.adobe.com/docs/commerce-admin/b2b/quick-order.html?lang=en ... View more