Magento 2.x Feature Requests and Improvements

Feature request from paales, posted on GitHub Aug 03, 2016 I want to have all product information imported but I want to be able to override the description of a certain product, but the prices and stock should import like normal. Just like the new core config values, it would be nice to have a scope above the default scope. This would solve the problem that a Merchant needs to overrides the values on each store-view (which is undoable with a Multi Store Setup). If the Use Import Values is unchecked the Merchant is able to change the value. A new flag gets created in a new catalog_product_import_export_overrides (or some other table) table. When importing the system checks this table to skip certain import-values. ... View more

As part of the new 3-D Secure standard that is coming into force in Europe, there are a number of new parameters that should be sent to credit card acquirers. For a full list of the new fields check Credit Card 3DS2 Fields Currently missing information as far as my research showed: customer last login date customer password change date how many attempts to add a credit card to vault (e.g. tried to add 100 credentials and only the last one was valid) customer suspicious activity (there should be a way for a merchant to mark a customer as suspicious) street 3 field for billing and shipping address mobile phone and work phone (add 2 additional phone fields) expected delivery date for preordered products To ensure full compliance with the 3-D Secure standard this fields should be added. ... View more

The "My Orders" view on accounts simply gives a list of orders sorted chronologically with the ability to set the number of records displayed per page.    It would be ideal to give a search function for the user to be able to search/filter for orders by a number of parameters including    - Order Number - Order Date (Including Date Range)  - Product   - Status     The only articles / extensions that i have ever found have been giving the administrator the ability to search for this. However for customers who are placing larger volumes of orders via a portal this could/would be a very useful piece of functionality ... View more

When creating tables in Module/Setup/InstallSchema.php I would like "Magento\Framework\DB\Ddl\Table.php" to support the JSON data type as it has its advantages. For DBs that do not have a JSON data type, they can default to text.   At the moment I need to add my column manually to enable the usage of the JSON data type. $sql = <<<EOT ALTER TABLE my_table ADD COLUMN column_name JSON NOT NULL AFTER a_table_column; EOT; $connection->query($sql);   ... View more

With all the data-breaches and insecurity on the internet, it would be helpful if Magento enabled FIDO strong-authentication as a standard feature to protect user accounts from getting hacked.  Savvy users can then choose to protect themselves with a FIDO Authenticator instead of just userid/passwords.   FIDO is an industry-standard security protocol for web-applications, currently enabled on sites like Google, Facebook, SFDC and many other sites.  It will soon be standardized by the W3C for WebAuthentication.  But, by having Magento include it as a standard feature, it will enable one of the strongest authentication protocols on the market for Magento sites and their customers.    We will be happy to provide some source-code to enable this - we've already implemented the core protocol into Magento 2, but since we're not Magento experts, we'd ideally like to see Magento include/adapt it into their core product.    Let me know how we can help further.  Thanks. ... View more

We always run into errors when including "additional_attributes" column because one of our custom attributes uses commas/description-type box. Changing the delimiter is not a good solution as it also means updating it on your machine. Our CSV's are usually transferred to multiple people and should always be ready to go with comma delimiters. We would like Magento 2 to use Magento 1's system of separating each attribute into it's own column. The importer isn't very useful for bulk product uploading if our most important attributes need to be omitted and we've resorted to a Firebear Importer module. Could this be something a future version of M2 fixes? This would avoid a lot of headache and make a much more readable CSV product export. ... View more

See https://github.com/magento/magento2/issues/6709  Thanks ... View more

In the Magento CE intro it says that the ability to have multiple stores is one of the most powerful features.  I spent time configuring multiple websites / stores / views, only to discover that you can't even assign certain users to certain stores within the admin!  Plus the sales reports are combined for all the stores by default, and there is no way to make the admin page default to show the sales report only for the store that belongs to the logged in user.  This is fundamental to having multiple stores.  Right now this is more like having multiple shopping racks (shoe section, underwear section, shirt section) rather than having multiple stores (company1, company2).  My feature request is to stop saying that Magento has a powerful multi-store ability so that other people don't waste as much time as I did trying to set up multiple stores to discover this huge limitation. ... View more

All auto-generated factory classes, should implement common interface.  All factories, have to have public function create(array $data = array()) method anyway. So why they do not implement some common FactoryInterface interface?   ... View more

The idea is to have an option how customers are adressed. For example personal like "Hello Ben" or formal like " Dear Mr. Marks". These could be on webshop welcome message and also in transactional mails. ... View more

For a configurable product that has tier prices can the unit price on the product page update to the correct tier price based on the quantity that the user enters. e.g. Buy 100 for £1.55 Buy 200 for £1.04 each and save 33% Buy 300 for £0.78 each and save 50% Buy 400 for £0.70 each and save 56% Buy 500 for £0.62 each and save 60% If the user enters 100, the unit price displays as £1.55 correctly. However if the user enters 200, the unit price remains £1.55 whereas it should display £1.04. It does not display the correct tier price until you add the item to the cart. ... View more

Feature request from bondimedical3, posted on GitHub Jan 04, 2017 Google is making a big push with AMP pages in mobile search results. I am seeing more and more AMP results in SERPS and I believe if Magento would like to keep a competitive edge in the market it will need to begin to look at adding this feature to Magento 2. Google SERPs are constantly changing with new features and they have even added an AMP carousel in mobile results where if there are more than 3 AMP results on the first page a carousel appears on the top where people can scroll through. In the future this will become a necessity for all e-commerce platforms. https://www.ampproject.org ... View more

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

Currently it is not possible to have an admin menu link with more than 3 arguments:   menu.xml: ... <add id="Module::module_name-id" action="module/controller/action/paramFoo/valueBar" .../>   is menu item link is truncated to: 'module/controller/action/' and ignores the 'paramFoo/valueBar' addition.    I'd suggest adding another property to the <add tag, something like:   actionParams="paramFoo=valueBar&paramLorem=valueIpsum" which would then be added to the $params array in the Magento\Backend\Model\Menu\Item::getUrl() method. ... View more

when a product creation fails it still creates the media items but doesnt clean them up ... View more

Magento divides sales rule discount amounts across the orders in a multiship order - it seems to do this based on the percentage of the quote total that the address in question represents.  However, when one of the orders does not meet the conditions of the sales rule, the portion of the discount that would be assigned to that order is just "lost".  Here is a more specific example: Normal situation: Example without a subtotal condition on the rule: Original line item subtotal: $100 Original sales rule discount total: $10 shipment 1 item total: $70 shipment 2 total: $30 shipment 1 = 70% of original total shipment 2 = 30% of original total shipment 1 discount: $7 shipment 2 discount: $3 Example WITH subtotal condition of equal or greater than $50 on the discount rule: Original line item subtotal: $100 Original sales rule discount total: $10 shipment 1 item total: $70 shipment 2 total: $30 (DO NOT MEET $50 minimum condition) shipment 1 = 70% of original total shipment 2 = 30% of original total shipment 1 discount: $7 shipment 2 discount: $0 Would expect all $10 of the discount to be applied to shipment 1 since it qualified for the sales rule and the full $10 discount from the quote should be awarded somewhere. I have reproduced this on a vanilla magento install with 2.4.5-p1.  The only thing non-core in this install is the adobe product recommendations module which I am using to test a different adobe error in a different ticket. This issue was investigated in an Adobe Support ticket: https://support.magento.com/hc/en-us/requests/569054 . The investigation found that this has been incorrectly implemented but not able to be fixed as a support request.  Instead this feature request is needed. The support ticket includes screen shots showing how to set up the scenario, as well as a short video showing what actions to perform to cause the issue. ... View more

Given to the documentation it's possible to change the image properties in view.xml. But sadly the quality of the image isn't reflected.   So it's only possible to change the values for the properties: width height constrain aspect_ratio frame transparency background (doesn't work btw.) The quality property is missing.   Please add the possibility to change the image quality property.     ... View more

Feature request from mttjohnson, posted on GitHub Nov 06, 2015 Working from the Magento 2.0.0-RC I ran into a scenario where an setup install script failed halfway through installing some data and I found that it inserted and modified the database to the point it hit an exception. I haven't noticed much use of database transactions inside the install scripts, but I found that it doesn't take much to add them to the start and end of the install() method. I found an example of using database transactions in \Magento\Checkout\Setup\InstallData and I went ahead and tested wrapping the contents of my install script. It seems like wrapping database install scripts inside a database transaction should be a recommended practice so that we can avoid half installed modules that can be very difficult to troubleshoot afterwards. public function install(ModuleDataSetupInterface $setup, ModuleContextInterface $context) { $connection = $setup->getConnection(); try { $connection->beginTransaction(); // Do a bunch of stuff here that may change things in the database and // you want to retain the option to rollback the changes if an error occurs // If no errors occur commit all the database changes $connection->commit(); } catch (\Exception $e) { // If an error occured rollback the database changes as if they never happened $connection->rollback(); throw $e; } } I have run into several situations trying to clean up magento sites that had things half installed and contained additional or missing changes to the database. Having gone through the mess of cleaning up partial upgrades leads me to believe there is room for improvement around the setup scripts. When would it be an ok idea to partially install data in the database? ... View more

Feature request from hostep, posted on GitHub Aug 24, 2016 Preconditions Magento CE 2.1.0 A whole afternoon of debugging joy (oh no, I already did this for you, don't worry) Steps to reproduce Take a look at how the billing address fields are composed: https://github.com/magento/magento2/blob/c5d618d5439362f50ba0f21d3fadf418cc765190/app/code/Magento/Checkout/Block/Checkout/LayoutProcessor.php#L201-L246 Compare this to the shipping address fields: https://github.com/magento/magento2/blob/c5d618d5439362f50ba0f21d3fadf418cc765190/app/code/Magento/Checkout/Block/Checkout/LayoutProcessor.php#L165 Expected result I expected to be able to change the sort order of the billing address fields in the checkout using xml or some other "convenient" way, but found this is almost impossible without manually altering the sort_order field in the customer_eav_attribute table. Actual result Not able to sort the billing address fields in a convenient and easy way. Discussion To be able to sort the shipping address fields in the checkout, we can create a file checkout_index_index.xml with something like this: <?xml version="1.0"?> <page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" layout="checkout" 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="children" xsi:type="array"> <item name="shipping-address-fieldset" xsi:type="array"> <item name="children" xsi:type="array"> <item name="region_id" xsi:type="array"> <item name="sortOrder" xsi:type="string">87</item> </item> <item name="postcode" xsi:type="array"> <item name="sortOrder" xsi:type="string">80</item> </item> <item name="company" xsi:type="array"> <item name="sortOrder" xsi:type="string">45</item> </item> <item name="vat_id" xsi:type="array"> <item name="sortOrder" xsi:type="string">46</item> </item> <item name="country_id" xsi:type="array"> <item name="sortOrder" xsi:type="string">85</item> </item> <item name="telephone" xsi:type="array"> <item name="sortOrder" xsi:type="string">90</item> </item> </item> </item> </item> </item> </item> </item> </item> </item> </item> </item> </item> </argument> </arguments> </referenceBlock> </body> </page> I was hoping there was a similar way for the billing address fields, but came to the conclusion after viewing https://github.com/magento/magento2/blob/c5d618d5439362f50ba0f21d3fadf418cc765190/app/code/Magento/Checkout/Block/Checkout/LayoutProcessor.php#L201-L246 this is not possible due to those hardcoded values. Or am I missing something obvious here? ... View more