Magento 2.x Feature Requests and Improvements

Feature request from karanbhomiagit, posted on GitHub Jun 29, 2016 Steps to reproduce Install Magento from develop branch. Try creating a simple product by making a call to REST API POST /V1/products. [Example] { "product": { "sku": "atoi-item", "name": "atoi-item", "status": "1", "type_id": "simple", "visibility": "4", "attribute_set_id": "4", "price": "3", "custom_attributes": [ { "attribute_code": "description", "value": "descreeeeeeption" }, { "attribute_code": "category_ids", "value": [ "1", "2" ] } ] } } I get a response : Status code 400. Body : { "message": "Unable to save product" } Expected result Error message in the response body should be more specific. There are so many field values that are required to be set on the request JSON, there is no way for the person making the request to identify where the request went wrong. Actual result [Example] Error message appears: "Unable to save product". ... View more

Feature request from webartistse, posted on GitHub Jun 29, 2016 Steps to reproduce System > Export Entity Type > products Several configs to somehow export useful data Expected result Select what products I want Deselect some columns Export as Excel XML Support for saving a filter option set. Actual result Total mess of everything This export function is not even useful in any way We have 4 stores but same product catalog. We have config prouct with variants. In export file every product appear 4 times. One row is store blank but seems to have all info. 3 other rows has many empty fields but same SKU as the first one. This exclude thing is all wrong. Lets say I want to export all product for a specific store. Its not possible. I tried to exclude products thats missing info in some fields since its duplicates but export does not apply the exclude filter if the field is empty. Tried many many ways in 30 minutes without any luck with something useful. Using Magento 2.0.7 ... View more

Feature request from basselalaraaj, posted on GitHub Jul 26, 2016 fixes #5805 ... View more

Feature request from tkn98, posted on GitHub Jul 28, 2016 Array keys cast to integer on string SKUs that could represent a PHP integer, however the Mysql comparison is string based for which - to prevent a cast in Mysql - it needs string quotes. These string quotes then need again the $sku as string. This is fixed by casting to string. Background: If you import many records with SKU that are numeric strings, Mysql performance is impacted negatively. ... View more

Feature request from paales, posted on GitHub Jul 29, 2016 Preconditions Magento 2.1.0 Steps to reproduce Setup 50 stores, with 50 seperate root categories with each their own subcategories. Import products using the importer, 200 should be enough Expected result It does a little bit less than 14000 queries for 200 products ;) Actual result [Screenshot, logs] ... View more

Feature request from Vinai, posted on GitHub Jul 30, 2016 Whenever I try to use a custom or core UI component the experience is frustrating, time consuming and painful. It would be great to see the components either made simpler (to use and understand how they work) or to be replaced with something simpler altogether :tada:. There is so much JS "magic" and conventions and poor documentation I find the developer experience severely lacking. Much of the XML is bonkers to read and write. So much of it seems to be "just do X and it will work" without information on WHY and HOW to debug if something does not work. The combination of a ton of PHP, XML and JS makes for a very tricky debugging process. It is very hard to properly write tests in small steps. Much of it is "add ALL the required code or NOTHING will work". Seemingly simply things become bloated tasks. Preconditions This applies to any version of Magento 2 from beta up to the latest version on github. Steps to reproduce Try to use UI components, either custom ones or core ones, without using extensive copy&paste and actively avoiding the urge to even think the question "Why?". Expected result The system should be simple to use AND understand. Actual result Hours wasted slogging through code and documentation, trying to understand WTF I got wrong and I find myself questioning some of my life choices. ... View more

Feature request from allanpaiste, posted on GitHub Aug 04, 2016 Currently it's not possible to create an 'image' EAV attribute for category as the code in many places has been hardcoded to talk only with attribute that is explicitly been named 'image'. This PR addresses that problem by steering the code towards more generic approach to the whole situation by detecting all matching attributes via backendModel check. Related issue: https://github.com/magento/magento2/issues/5438 ... View more

Feature request from ednacool, posted on GitHub Aug 04, 2016 Special Price From Date to Date not coming on configurable products at backhand i wanna show deal price via this but unfortunately this is not coming Magento ver 2.1.0 ... View more

Feature request from Corefix, posted on GitHub Aug 05, 2016 A problem will occur when you are adding any success message and the quickly changing page, fx adding a product to cart and then going to another page before the 3 seconds pass. This is especially true when dealing with production mode sites with all cache enable. I'm not a Javascript wizard so not sure any time is needed at all. But it should definitely be decreased. If their have been any thoughts on why this is 3 seconds I would love to know it. ... View more

Feature request from fooman, posted on GitHub Aug 05, 2016 UI Components are not easy to use - for an intro see http://alanstorm.com/magento_2_introducing_ui_components ... View more

Feature request from dvynograd, posted on GitHub Aug 07, 2016 This PR is fixing the issue that happens due to crashes during merging xml layout updates for widgets. STEP TO REPRODUCE Create a new widget. Specify the next settings: Type: CMS Page Link (Can be any widget which has user filling fields in widget the option section). Design Package/Theme: Magento LUMA Assign to Store Views: All store view. Layout Updates: Add Layout Update -> Display on -> All pages. Widget Options: Anchor Custom Text: “ Anchor Custom Title: “ Save a widget, clear the cache and open any page on the frontend. E.R. See new link added to a page. A.R. Exception is appeared (see 1133837156634.txt ) Note The issue is reproducible for any html character. This problem was fixed by adding CDATA in xml source. But also there is a second case with special character see 1.xml.txt That part of issue was fixed by changing filter to ENT_DISALLOWED in htmlspecialchars function. ... View more

Feature request from springimport, posted on GitHub Aug 08, 2016 What about add Additional info section in new issue template? Example. Additional info Q A Magento version 2.1.0 PHP version 7 x64 Operating system Windows 10 x64 ... View more

Feature request from F-Gueguen, posted on GitHub Aug 09, 2016 Hello, I use magento 2.1, maria db 10.1.14, nginx 1.11.2, varnish 4.1, php 7.0.7 with an architecture nginx http2->varnish->nginx->magento I have a store where I need to have hundreds of simple products associated to some configurable products (I sell sofa, you can change some colors, corner side, material, etc, and I need a stock per variation, so I have to use the configurable). The fact is I understand it's pretty long to generate the simple products, but then each time I need to edit the configurable, it loads and save the list of simple products, which sometimes breaks my page and takes forever. Would it be possible to have the "simple product" part of the page loaded only when needed? Same scenario, would it be possible to change the attributes to select order without loading the simple product list itself, as we could do in Magento 1? It's not possible to change this order by csv if I'm right. Thank you for your time and for this wonderful tool :) François ... View more

Feature request from sjovanig, posted on GitHub Aug 10, 2016 ... View more

Feature request from meng-tian, posted on GitHub Aug 10, 2016 The current implementation of \Magento\Catalog\Model\ProductRepository::getList does not allow filter products by stores. When specify store_id filter in $searchCriteria , an exception throws Invalid attribute name: store_id . This pull request adds support for store filtering by using the \Magento\Catalog\Model\ResourceModel\Product\Collection::addStoreFilter method. ... View more

Feature request from meng-tian, posted on GitHub Aug 12, 2016 The REST endpoint of product list is: http://<magento_host>/rest/<store_code>/V1/products It is intuitive to think the result of this endpoint should be filtered by <store_code> . For instance, specifying store code default should return products in default store; specifying store code all should return all products. However, in Magento 2.0.8, specifying different store code return the same result. This issue also apply to Magento 2.1.0 (#5723). This pull request will take <store_code> into consideration when retrieving products. A plugin is enabled only for web services areas. The plugin is not enabled for global dependency injection configuration as it may affect users in other areas, e.g., front store. Note: this pull request depends on #6095. ... View more

Feature request from Khaleel, posted on GitHub Aug 12, 2016 Hi Where do I begin to vent my frustrations with this platform? Firstly I will bring to your attention this Stackoverflow bounty which no one from the Magento Community gave an answer for that I a hoping will garner here: http://stackoverflow.com/questions/38589283/a-faster-route-to-deploying-static-content-in-magento-2-dev-to-live-etc?noredirect=1#comment65177020_38589283 Why is it that the Magento Team thought it was acceptable to turn a live website into Maintenance mode to carry out a deployment? Our company makes serious money and it is just - absurd - to consider ever placing our site in downtime (at any time or day). We literally ship our code to git and then pull on the live server and then deploy static content and this takes an incredible amount of time. Just this week, our developers made a few mistakes and we had to re-deploy twice. 45 mins of no sales. Clearly this is not a solution. There must be something were not doing correctly; but your own documentation, recommends it. @alankent who says 'I am not a frontend dev' Clearly not. Otherwise you would have chosen Sass and dropped the insane idea of Magento UI, which no one really knows what it is. And then further you would have scrapped RequireJS and all the insane (not SEO friendly) KnockoutJS bloat even on the cart. Please can you answer regarding this. It is been raised across the web on many threads on Stackoverflow which my bounty failed and even on this post: https://github.com/magento/magento2/issues/2104 other devs see the insane feature of this. Why is it sooooo slow to make changes to Less and JS even in a developer mode node. You have to recompile files (no Livereload; which I get people not a fan of) but seriously? Make a padding or margin change; delete all var folders, re compile static files for all languages and then run grunt to generate less etc - seriously? ALL our Front End Engineers are strong with JavaScript and CSS and most are (including me) previously Back End Developers. It is insane. Please can this be addressed? Gulp and Grunt is one argument but the process of static deploy on development mode is one thing - a live environment? Seriously? ... View more

Feature request from qmarlats, posted on GitHub Aug 12, 2016 Do you planned to allow custom options for simple products associated with configurable products like this extension did? Since there are no any alternative extension for Magento 2 it would be really usefull. ... View more

Feature request from techteamus, posted on GitHub Aug 14, 2016 Affected version: Community 2.1.0 During test deployments of my Magento 2 setup I continually ran into problems if I used a language other than en_US. After running the setup and a 'bin/magento setup:static-content:deploy en_GB' the front end files would display just fine but the admin interface was missing all the CSS etc. I eventually traced the problem back to how the initial admin user is created. Regardless of what language is chosen during setup the admin user is always setup with the interface locale as en_US. To me this seems counter intuitive, the initial admin user should be configured with the same language as the store configuration. Changing the admin user interface locale to en_GB in the database (not recommended) solves the problem instantly and the admin interface displays as expected. If the initial admin user was correctly configured this would have saved me time and I have no doubt other people are trudging around in circles try to resolve what looks like a complex issue but is in fact a simple configuration problem. ... View more