Magento 2.x Feature Requests and Improvements

Hello, Ive started developing magento2 and the cli tool is very nice and easy to use. But I was missing some tools for code generation like modules and themes. Everytime you create a module or theme you have to create the same boilerplate registration.php, module.xml and other config files.   For example to create a new module: php bin/magento module:create Vendor ModuleName   This code could be generated through the CLI tool. A good example is the @angular/cli tool for Angular.     ... View more

We would like the ability to import a CSV that includes a full redirect map of old URLs to new URLs when a site is being replatformed on Magento. We have found with many clients that they have hundreds of redirects for various pages on the new site that needs to be created. It would be incredibly efficient if we could do a bulk import function with this so we avoid spending hours building server level redirects or entering them one at a time. ... View more

I  know there are endpoints for both fetching an address by id and deleting one by id. Listed below: (customerAddressRepositoryV1) as listed here http://devdocs.magento.com/swagger/index_20.html#/ 1) To get a address  Endpoint: /V1/customers/addresses/{addressId} Method: GET 2) To delete a address Endpoint: /V1/addresses/{addressId} Method: DELETE The issue with either of them is that they are not accessible by customer token. They seem to only work with Admin Token Authentication. If a customer adds multiple addresses and selects a specific one to fetch entire details or delete it, it should be allowed from his customer access. Please suggest. ... View more

(From https://github.com/magento/magento2/issues/7852)   Steps: Run "bin/mage module:disable Magento_Review" in a standard Magento installation Actual Result: The module can't be disabled because Magento_Customer depends on it. Expected Result: The module Magento_Review is disabled. Is it really necessary that the Customer module depends on the Review module? It's the only reason why I can't disable the Review module and a quick search for "Magento\Review" in the Customer module's codebase reveals that only a single file references a class in Review: \Magento\Customer\Block\Adminhtml\Edit\Tab\Reviews. I'm sure this can be refactored to remove the dependency, right? ... View more

https://framework.zend.com/blog/2016-06-28-zf1-eol.html   So Magento will migrate lib components to other   zf2 or doctrine etc? for example still magento using Zend_Db from zf1. ... View more

There should be a default product media attribute "Hover Image". Product image assigned to this attribute should be visible when user Mouse hover the product image on category page and original image comes back on moue out. This small feature will improve the user experience and benefit conversion rate as well. ... View more

Feature request from davidnguyen2205, posted on GitHub Oct 27, 2016 Preconditions Magento 2.1.1 Steps to reproduce Add tax rate & rule (10%) Change some settings in Stores > Configuration > Sales > Tax: Add a new product (for testing): Price: $10 Save then indexer:reindex and clear cache or even disable cache. Expected result The price in frontend included tax. The test product's price is $11. The price when calling rest api ( /V1/products/SKU + /V1/carts/mine + /V1/carts/mine/items ) included tax. The test product's price is $11. Actual result On website, it's great. On the response, the price is always excluded tax. Is that missing something in my steps to set up the product's price included tax? Or is that an issue? ... View more

It would be so useful to be able to adjust the columns data eg stock levels, quantity and price on the catalog page rather than having to open each individual product. ... View more

In Cache Management, when refreshing caches it would be useful to be able to select only those Caches that are "Invalidated" from the Mass Action menu ... View more

Currently when using configurable products the stock threshold is not working.   For example: You have a configurable product based on 5 simple products. Shirt-S (stock 10), Shirt-M (stock 3), Shirt-L (stock 10), Shirt-XL (stock 10) and Shirt-XXL (stock 10). The stock threshold is set to 5.   When a user clicks size M the stock status should change to: Only 3 in stock. But it does not. ... View more

When using configurable products based on two or more attributes that make up the simple products, the layered navigation ignores the stock status.   This problem allready existed in M1 and remains in M2.   Sample: Configurable products has 4 simple products (no backorders allowed, do not display out of stock items): Shirt-Black-S Qty 2 Shirt-Black-M Qty 2 Shirt-Red-S Qty 2 Shirt-Red-M Qty 0 (sold out)   When a users filters layered navigation on color Black and Size M they will still get the configurable product even though the Red M is sold out.   Would be so nice if the layered navigation index would handle this correctly. ... View more

If your locale is not set to en_US, the PayPal module uses the really old button style:     It would be better for an admin to be able to choose the PayPal button flavour inside the payment method, and have the following choices: https://developer.paypal.com/docs/classic/api/buttons/   Also, see Magento\Paypal\Model\Config line 983 (Magento 2.1.3) ... View more

Currently the translations in Magento 2 will use the original string if there is no translation. For instance: en_US.csv:   "My First String","My First Translation" "My Second String","My Second Translation" nl_NL.csv:   "My First String","Mijn Eerste Vertaling" if you do the following when language is set to 'en_US': echo __('My First String') . '<br>' . __('My Second String'). '<br>' . __('My Third String'); The output will be:  My First Translation My Second Translation My Third String (falls back on original string)     if you do this when language is set to 'nl_NL':, the output will be: Mijn eerste vertaling My Second String (falls back on original string) My Third String (falls back on original string)   I think it would be really useful for it to fall back on the default language first, so the output would be: Mijn eerste vertaling My Second translation (falls back on en_US translation) My Third String (falls back on original string)   Why? Because this would open up the ability to use short placeholder strings in the code, instead of the long translations. For instance, you could do: "ACCOUNT_NOT_CONFIRMED","This account is not confirmed. <a href=""%1"">Click here</a> to resend confirmation email."   This also gives the benefit of being able to correct the en_US language files (for instance when having spelling mistakes) without having to worry about translations or the string in the code. ... View more

Based on those links ux.stackexchange.com, www.lukew.com/, https://medium.com/ Magento 2 maybe should be using the method from Mikkel Bo Schmidt article to chose country and state instead of dropdown list like it uses now?   If Magento choses to use it (To me it seems Magento 2 tries to get as far from dropdown as possible) then a way how module developers can also use it should be well documented not like drop-down list creation now.   Examples: Magento 2 module Royal Mail Shipping where the list of radio buttons is quite big for customer to look through would need that.   Also Estonian post offices dropdown menus added to shipping method that are in more difficulty to create in Magento 2 (Maybe that is the reason why Estonia does not have any commercial shops that uses Magento 2.x) then they were in magento 1.x pages, but they are necessary because no one would scan through such amount of radio buttons.   The way described in those posts can solved both problems (city and state drop-down and shipping methods).   As it is well known most of the orders that are made in ecommerce websites comes from mobile devices and as mentioned articles referred dropdown lists are not user friendly.   Hopefully shipping-methods block extension would get finally documentation for long list of items.   CAN ANYONE SEE A REASON WHY MAGENTO SHOULD NOT USE SOLUTION FROM THOSE ARTICLES?!   ESTONIAN SHIPPING-METHOD EXAMPLE: www.apollo.ee ... View more

Feature request from valibus, posted on GitHub Oct 14, 2016 Edit: i guess this is linked to #5648 . This is still waiting for update after a bug created the 14th July (3 month ago => wheen will you fix it) Anyway, i hope this video i make will help all of you to understand our problem. Preconditions Magento 2.1 CE PHP 7 having already some simple product created for example : variation 1, variation 2 Steps to reproduce Go to back office Create a configurable product Go to configuration area in the product sheet and start the assistant there is the problem : you couldn't select existing production you have to create other product before. Expected result Be able to select simple product using a specific attribute for variation (if was OK in magento 1.9) Actual result there is the problem : you couldn't select existing production you have to create other product before. Please check in attachement the video (using internet explorer to read the swf file) you will see the function to select existing product only appear at 1:30 only after completing the assistant and creating the virtual product we don't need. linked to issue : 7011 ... View more

With the prevalence of custom pricing contracts with the various carriers, it would be nice to add multiple FedEx account numbers, or UPS account numbers to your shipping method settings based on the service being used. We have international shipping under one account and domestic under another because we get different price breaks. ... View more

Feature request from IvanChepurnyi, posted on GitHub Mar 04, 2016 It is a proposal for the future pull request, upon product team and dev team approval 1. Scalability Problem At the moment, Magento database gets unmanageable, when you have URL rewrites for products and categories combined. The problem is in the way how URL rewrite table is build up. Becuase URL rewrite generator creates an entry in a database table for each combination of product and category. So it makes databases with only 3000 of products and 200 categories grow into 600,000 record table for URL rewrites. That limits most of the Magento merchants to create SEO valuable URL structure when they URL rewrites lookup takes more time that it could. Solution Use combination algorithm at runtime instead of generating all possible combination of URL. I already had PoC with one of my existing customers on 1.x; I have plans to port to Magento 2.0 if core team would be interested in such performance improvement contribution. How does combination algorithm work? Let consider we have the following URL: path1/path2/path3/path4 Then we can chain multiple processors for URL match. In default implementation there will be 2: Full match processor Combined processor Full match processor Simply lookups the full URL rewrite, if it does not return match, then the next one is used Combined processor Splits the given URL in two parts: path1/path2/path3 and path4 . If there is a URL rewrite for the first part and it has the flag, that it is combinable with another record, the processor then makes a request to find URL rewrite target for path4 . By having specific merge algorithms assigned to it (category + product or even more in feature), it will create a virtual rewrite record that will be used to forward the request to a needed target path How does it affect Canonical Url for a Product? This algorithm allows to specify canonical category even at runtime, and you don't need to create a separate index for it. How does it affect Duplicates of URL? Because path1/path2/path3 and path4 should be unique in the main table, combining them together does not bring any issue, except if there is path1/path2/path3/path4 rewrite exists. How does it affect Current Installments? It will use the same tables that exist atm. 2. Internationalization Problem Because Magento URL generator removes all the characters from non-latin alphabet, it makes impossible to use all the possibilities of allowed URI specification (RFC3986) Solution By lifting the logic behind the algorithm of URL generator we can gain much broad SEO possibilities, including ones with different writing schemes (Cyrillic, Chinese, Arabic, etc.). As you can easily use UTF-8 characters in URL path as soon as you escape with rawurlencode when building the rewritten URL, then on the processing convert it back with rawurldecode. SEO experts will love that as it gives better search results rankings in non-latin alphabets. This approach does make it even possible to generate URL rewrite lookup in much easier faster manner, as you can simply replace all the defined prohibited characters with "-" (dash). So it allows moving URL generation logic to the pure database level. How does it affect Current Installments? There are no changes to already translated URLs, it might re-index it a bit differently, but then redirect rewrite history will make auto-redirect. 3. Large Varchar Index Problem As request path is a string match, when you have a huge database it makes it much slower to lookup the required record. Solution There is a simple solution that can help improve performance dramatically on such datasets. As all of us know CRC32 is an integer checksum of 32 bits (perfect for INT column). MySQL has a built-in function for calculating it and PHP has it as well. It is not widely used as it has much higher collision probability than other checksum algorithms. But it is a perfect solution for fast closest match calculation. It can have 5 billion different checksums calculated based on the input. The probability that a 100,000 record in the database will collide is 1 to 50. So there might be the worst scenario 50 records returned for one record lookup, but you can add a single char field to reduce that to only URLs starting with the same letter. Then on PHP side, you only walk over an array of returned result and check the closest match. This option allows managing millions of URL rewrite entries with reasonable lookup time. How does it affect Current Installments? It won't change existing table structure as the new table will be introduced, and existing records will be inserted by a simple SQL query during migration. New records will be handled in the URL indexer itself. ... View more

Feature request from MaximKitsenko, posted on GitHub Sep 01, 2016 Previous versions of magento (1.7.x-1.9.x) provides API Method that returns current magento store version. Why did you removed this API in Magento2? Please add this method to API! I'm developing Magento wrapper for .net ([https://www.nuget.org/packages/MagentoAccess/]) and i need this API to support a lot of Magento's versions. ... View more

Feature request from mzeis, posted on GitHub Feb 12, 2015 Some extensions log useless stuff that pollutes the logs. The problem could be avoided if Magento as well as the extension vendors would pay more attention to the log levels already provided and use them accordingly (e.g. differentiate between debug output and real information / notices / warnings / errors). As it may not be possible to force using the correct log levels it would be nice to have an option in the System Configuration to disable logging. One of many possible ways to solve this in the UI would be to have a multi-select listing all modules in the installation. ... View more