Magento 2.x Feature Requests and Improvements

Feature request from navarr, posted on GitHub Feb 05, 2015 Suggested Labels: feature request, up for grabs Request Autocomplete is a web technology implemented in Chrome that enables very speedy entry of a customers credit card details, addresses, and more. It is very simple to implement, and would be a general improvement to Magento in all forms. More information: HTML5 Rocks page HTLM5 Rocks Demo Store (check it out!) Firefox browser implementation bug Previous Art: Magento1 Extension by the Chromium team ... View more

Feature request from seansan, posted on GitHub Mar 17, 2015 When one build up product reviews and a second store is opened. Then the product reviews are not enabled (selected from scope list) in the second store. This can be done manually, review per review. There should be a method to mass update product reviews to enable them in other store views. Some more information here http://magento.stackexchange.com/questions/55716/sql-to-make-product-reviews-available-in-other-store ... View more

Feature request from seansan, posted on GitHub Mar 17, 2015 It should ne able to pre-select a layered navigation filter for a category: meaning, that when opening the category page, then a layered navigation filter is already applied Suppose you sell shoes (configurable product) and you have a category stating to show all shoes in size 10 you would then create a normal shoe category (select all shoe products) then selected the (new setting) for a layered navigation pre-select filter for size 10 this way only shoes available in size 10 are shown http://magento.stackexchange.com/questions/55191/magento-set-selected-filter-in-layered-navigation ... View more

Feature request from fooman, posted on GitHub May 07, 2015 Custom Totals are a great feature of Magento. I do believe we can improve their implementation and reduce overall complexity by keeping custom totals in separate dedicated database tables similar to how we store line items. With the current structure to add a new custom total to cover base and order currency plus tax, at my last count, one has to add: 1.) 13 columns to table sales/order 2.) 4 columns to sales/invoice 3.) 4 columns to sales/creditmemo Not everyone gets this right including for example Enterprise custom totals: getData('base_' . $code) vs. sales/order::gw_card_base_price_invoiced I believe if we had the following tables sales/order_totals sales/order_invoice_totals sales/order_creditmemo_totals with the following columns: total_id parent_id code amount base_amount tax_amount base_tax_amount calculation_order and additionally for the sales/order_totals table description amount_invoiced base_amount_invoiced amount_refunded base_amount_refunded tax_amount_invoiced base_tax_amount_invoiced tax_amount_refunded base_tax_amount_refunded this would help a lot with the aim to a.) remove duplication of efforts (every custom total shouldn't need to add all these columns) b.) take away complexity of having to set up the database to reduce chances for errors Additionally to keep track of tax I think these should be linked through to the same table that we use to keep track of taxed items to allow for multiple taxes on the totals (and be able to reconstruct this later). If we don't link to the tax table we should at least add tax_percentage . ... View more

Feature request from chrom, posted on GitHub May 26, 2015 extend global product search through search the pages of the blog (CMS page) ... View more

Feature request from seansan, posted on GitHub Jul 25, 2015 Request for ability to add new cart rule action - type cart id Now it is not possible to give a discount on the FIRST item only For instance we have a deal: the first T-shirt with 50% off ... (as a try out) If the cart ID can be used in a rule action then this is possible Concrete: please add cart id as a new rule type ... View more

Feature request from chasteIT, posted on GitHub Sep 03, 2015 Filtering items in grouped product grids using the attributes of their associated simple products could allow users to select options to find their desired simple products similar to configurable product selectors, but it would also allow the store owner to display all of the available simple products initially. For example, a Grouped Product could contain TVs of brand Samsung, Vizio and LG available in sizes 50, 55 and 60 inches. Upon entering the page, the customer could see the grid of products and their varying brands, sizes and prices. The customer could then select options in a dropdown filter to only show their desired brand and size. A sorting feature for the initial grid would also be cool. Edit: I found Magneto extension, Grouped Products Filter, which does this exactly. Here is the demo. ... View more

Feature request from markoshust, posted on GitHub Sep 10, 2015 The customer id (entity_id) should be included in the customers export for referential checks & database/SQL update capabilities ... View more

Feature request from markoshust, posted on GitHub Sep 10, 2015 The customer id should be included in customer addresses export for referential check capabilities ... View more

Feature request from CRYX2, posted on GitHub Sep 18, 2015 Hello, i'm currently testing 1.0 beta and I think who all the textarea of block could be improved with a Syntax Highlighter like CodeMirror or Ace Editor. it would be a big improvement that should not take away too much work. ... View more

Feature request from owenhaynes, posted on GitHub Oct 25, 2015 At the moment the json API is not very compliant to http://jsonapi.org. This makes life hard when trying to use the magento API with angluarjs modules such as rectangular, angualr-restmod. I can imagine this is a lot of work. ... View more

Feature request from markoshust, posted on GitHub Oct 24, 2015 The ./bin/magento CLI tool contains the command admin:user:create . It would be very helpful to add another command admin:user:update , which would allow the user to update the admin password. This comes up a lot when taking over development for projects from other companies, and/or just needing a quick way to change the admin password to access the site. The same directives should probably be used from admin:user:create . ... View more

Feature request from arunkasyakar, posted on GitHub Nov 24, 2015 There are no rest api's available for wish list, review and rating related tasks. ... View more

Feature request from bubach, posted on GitHub Sep 29, 2014 Hi, I'd like to request just generally more settings for how and where images are stored. Possibly even fallback functionality for where to fetch images if not found in main path. One issue I have in particular with the current code base is on this line: https://github.com/magento/magento2/blob/develop/app/code/Magento/Catalog/Model/Product/Image.php#L501 Where store ID is set as part of the cache path. In some webshops where you have 10+ stores and literally all the images are identical, it's a huge waste to keep duplicates of every thinkable image size. Not to mention the server strain when clearing the image buffer. ... View more

Feature request from tzyganu, posted on GitHub Oct 08, 2014 I see that in Magento 2 (opposed to 1) the html elements generated by the template path hints have their own classes and can be easily identified in javascript. This goes nicely with the idea I have. How about, when the template path hints are activated, to have a small toolbar (or button or whatever) somewhere on the top or bottom of the page that will allow the developers to show/hide certain elements of the template path hints. For example calling jQuery('.debugging-hint-template-file').hide() / show() will hide/show the template names. The same can be done to hide the block class names using .debugging-hint-block-class . or the dotted borders can be hidden by jQuery('.debugging-hints').css({border:'none'}); . Right now the processes that involve template path hints are slow. First I need to enable the path hints, identify the class or template, do my modifications, see if they appear in the page, then disable the path hints to see how it looks without them, then enable them again if needed. I know that I can create buttons on my browsers with the actions I need but a built in feature would be better. ... View more

Feature request from ihor-sviziev, posted on GitHub Oct 21, 2014 From Magento 1.x we have a lot controllers that use _addContent. This method is fires after running loadLayout. As result we haven't ability to use action directive from layout files to use some manipulations, as example change template file for block (described there). I propose mark this method as deprecated and replace same places to layout updates. List of this places: https://github.com/magento/magento2/search?q=_addContent ... View more

Feature request from seansan, posted on GitHub Oct 27, 2014 Currently extension are clogging up our tab and menu bars. And esp the last couple of years everybody seems to add their company name and extension name in every menubar they can. Wlould be nice for the admin to stop or circumvent this. Pref. All extensions also in one place in the backend ... View more

Feature request from ihor-sviziev, posted on GitHub Nov 14, 2014 For now this class is very complicated and hard to understand their logic https://github.com/magento/magento2/blob/master/app/code/Magento/Sales/Model/Order/Payment.php#L1036 ... View more

Feature request from ihor-sviziev, posted on GitHub Jun 25, 2014 For now we have sorting store groups by store group name only. We should add sort_order field(like for store views) and sort by it. It's needed if we have few store groups and switcher between store groups on our website, now we haven't ability manage orders. ... View more