Magento 2.x Feature Requests and Improvements

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

Feature request from alexgoodey, posted on GitHub Aug 15, 2016 It is not possible to change the price of custom options at different scopes. If you change the scope when editing a product and change the price of a custom option the value is changed across all scopes. This functionality was present in Magento 1. Steps to reproduce Create a Magento environment with multiple websites and store views Create a simple product Add a custom option to the product with different values with different pricing Save the product Change the store view scope you are editing in and change the pricing of the custom options Save Review the custom option pricing at default and other storeview scopes Expected result Price of the custom option should be different at the storeview scope. Actual result Price of the custom option is changed to the new value at all scope levels ... View more

Feature request from paales, posted on GitHub Aug 15, 2016 Preconditions Magento 2.1 Steps to reproduce Run bin/magento setup:upgrade Expected result It only shows what it actually modifies Actual result It shows the names of all modules, making it hard to pick anything up what has changed. ... View more

Feature request from Marko-M, posted on GitHub Aug 16, 2016 Preconditions Magento 2 version 2.1.0 Use \Magento\Framework\Url::getUrl() from secure area of the store Steps to reproduce Make sure code is executed in secure area of the store (HTTPS) Generate URL in code /** * @var \Magento\Framework\Url */ protected $url; ... $this->url->getUrl( 'test/test/test', [ '_secure' => false ] ) Resulting URL is https://example.com/test/test/test Expected result Make sure code is executed in secure area of the store (HTTPS) Generate URL in code /** * @var \Magento\Framework\Url */ protected $url; ... $this->url->getUrl( 'test/test/test', [ '_secure' => false ] ) Resulting URL is http://example.com/test/test/test Reason behind such behavior is: https://github.com/magento/magento2/blob/2.1.0/lib/internal/Magento/Framework/Url.php#L364-L366 where code assumes that if current request is secure, requested url should be secure as well, regardless to '_secure' parameter saying otherwise. ... View more

Feature request from elioermini, posted on GitHub Aug 17, 2016 I think would be useful to have like in M1 the method streamOpen() . There is no other way to initialise the field $_streamHandler of the class File. Other methods in the class File rely on the initialisation of $_streamHandler and having it null I suppose that leaves the class just possible to use only extending it. ... View more

Feature request from hiephm, posted on GitHub Aug 19, 2016 @alankent Right now there are many classes that usually be inherited but all of their members are private (for example \Magento\Payment\Model\Method\Adapter). For child classes to use their parent members, we must re-declare constructor and all members again, which is not very convenience. I know that OOP good practice is keeping member as much private as possible. But given the extensible nature of Magento, I think most of the private member can be safely changed to protected. ... View more

Feature request from sumihiro, posted on GitHub Aug 22, 2016 I want to use Text Swatch Attribute with long text. But Default Store View value cannot be saved correctly. It will be shrink. Preconditions I'm using Magento2.1.0, and MySQL 5.6.30. Steps to reproduce Create new Attribute, and select Text Swatch. Set long text to Default Store View in Manage Swatch. Like: "01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 " Save Attribute. Expected result Default Store View value is saved full length. Actual result Value is shrink. Like: "012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234" May be, it is caused by limitation of max varchar length (255) of MySQL. mysql> desc eav_attribute_option_value; +-----------+----------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-----------+----------------------+------+-----+---------+----------------+ | value_id | int(10) unsigned | NO | PRI | NULL | auto_increment | | option_id | int(10) unsigned | NO | MUL | 0 | | | store_id | smallint(5) unsigned | NO | MUL | 0 | | | value | varchar(255) | YES | | NULL | | +-----------+----------------------+------+-----+---------+----------------+ 4 rows in set (0.00 sec) How to save value correctly? ... View more

Feature request from aholovan, posted on GitHub Aug 23, 2016 Looks like 'elementNameType' validator is very strict. I've got an exception in dev mode: 0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'name': [facet 'pattern'] The value '4d072daa2b95b9d3fd3995d2faaf2993' is not accepted by the pattern '[a-zA-Z][a-zA-Z\d-_.]*'. Line: 645 ... View more