Magento 2.x Feature Requests and Improvements

Feature request from ldusan84, posted on GitHub Dec 25, 2014 I think that Magento2 should import namespaces and use aliases instead of using fully qualified namespaces all over the place. Here is an example. What I suggest is that instead of: throw new \Magento\Framework\Model\Exception( __('Invalid login or password.'), self::EXCEPTION_INVALID_EMAIL_OR_PASSWORD ); We could have: use \Magento\Framework\Model\Exception as MagentoException /* ... */ throw new MagentoException( __('Invalid login or password.'), self::EXCEPTION_INVALID_EMAIL_OR_PASSWORD ); Here are the benefits from this: With importing namespaces keyword at the first few lines of a class you actually get a nice documentation of your class dependencies. Everything that class uses is in those first few lines. It makes dependencies explicit. If something changes in the future, you would only need to change it in one place, in import declaration and the alias remains. With fully qualified namespaces you would need to find them everywhere in class and change. Less confusion if you have similar namespaces, you can give them different aliases. All major frameworks use importing/aliases over fully qualified namespaces. Let me know what you think. ... View more

Feature request from markoshust, posted on GitHub Aug 31, 2015 There are two "One or more of the Cache Types are invalidated" messages that appear when a cache clear is needed. I don't see the purpose of the modal prompting, and then when closing the modal, still seeing the alert at the top of the screen. The modal is redundant. I believe this should be removed, and stick with the "M1" way of the prompts by just displaying the message at the top of the screen. It's plenty apparent the cache needs to be cleared. Having to close the modal every time is also very cumbersome and annoying... ... View more

Feature request from ldusan84, posted on GitHub Dec 26, 2012 Currently in Magento if you create a shopping cart rule with condition that is satisfied with your current cart and if you checkout with multishipping with 2 addresses with items on those addresses that do not satisfy the condition separately, the rule is not applied. I think this is a bug since shipping should not affect the rule in my opinion and it should be fixed in Magento 2. ... View more

Feature request from ihor-sviziev, posted on GitHub Jul 17, 2014 For now in Magento 1 and Magento 2 when we editing product we have 3 scopes attributes: global, website and store view, but we have select only can select global and store view scope. As result - we have only two levels in value fallback: Global -> Website or Global -> Store view. Would be great have three levels in value fallback, like in config: Global -> Website -> Store view ... View more

Feature request from Den4ik, posted on GitHub Jul 20, 2014 Good solution integrate HTML Purifier into Magento. It help validate html code for unclosed tags. Sometimes in static blocks and pages html code not clear. ... View more

Feature request from FiveDigital, posted on GitHub Apr 16, 2014 Right now, there is not possibility to translate (or change) the routes generated for the frontend. The route to the basket is always /checkout/cart and it would be nice if we could configure or change the routes on a store view base. So that we can have /warenkorb in the German store view and /basket in the English one. Other frameworks like Symfony take the route in the templates and look up how to generate the URL for the frontend in the config (see http://symfony.com/doc/current/book/routing.html). Perhaps this could be a way for Magento too. The route name for the checkout could remain /checkout/cart but it resolves to whatever I have configured for in my store view and have a fallback to a default URL. Are there any plans to change the routing / URL behavior in Magento 2? If not, perhaps you might think of taking it into your backlog. ... View more

Feature request from 12th, posted on GitHub Mar 30, 2014 It would be good to check with the latest release from the working demo project. For example, the release was issued, the developer downloaded it and started testing it is not correct work and in this case it would be good to have a platform from which to verify functionality. ... View more

Feature request from seansan, posted on GitHub Aug 22, 2014 Request for the ability. That when you have a grouped or bundle of products based on configurable products and when the simple product attribute identifier is the same: that you only have to choose it once So. When you buy a bundle of tshirts. (Where tshirt is configurable product. And per size is simple) that you only have to select the size drop down once - and this counts for all the configurable products in the bundle or group http://magento.stackexchange.com/questions/5002/multiple-configurable-products-as-a-bundle ... View more

Feature request from ihor-sviziev, posted on GitHub Jul 04, 2013 For now we have 3 variants configuration scope: default website store view I think we need add new scope betwean website and store view - store_group. For example: we have one magento website with 2 stores(2 domains) + 2 mobile themes for them (+2 domains). So we created structure: store 1 store 1 desktop store view store 1 mobile store view store 2 store 2 desktop store view store 2 mobile store view For design we have next structure: desktop package default store 1 store 2 mobile package default store 1 store 2 For now we need configure for store 1 themes (Translations, skins, layout, etc.), so I need set theme value "store 1" for desktop store view and for mobile store view. If we have store_group scope we should be change theme value at store_group scope only. ... View more

Feature request from tzyganu, posted on GitHub Sep 16, 2014 I'm adding a new category in the backend, select one product and fill in a position value. After doing any action on the grid (filter, sorting, change page) the product I previously selected is still selected but the position is empty. In this example I change the sorting ... View more

Feature request from mageman, posted on GitHub Jan 13, 2016 After creating a configurable product with 1 generated associated product, saving to a new attribute set, then re-open the configured product. and click on edit configuration: There are options to add an attribute whose type is not a dropdown, i.e. yes/no or text field, but after submitting these changes, the values do not appear in the new configuration! Furthermore, the new attribute is not being added to the attribute set! It seems wrong that non-dropdown attributes cannot be added. Why is it not possible to add these types? I am recommending the following: Despite the fact that the magento manual states that only dropdown types are supported, I am requesting support for attribute types other than dropdown, rather than the removal of options that are not supported. This would make working in the admin pages a-lot easier. For example, I could have a numerical or boolean attribute that I can generate associated products for. I was hoping to have the same user experience here in many ways similar to M 1.9. ... View more

Feature request from zamboni084, posted on GitHub Jan 13, 2016 Previous and next buttons on the product page in admin. So you don't have to exit to the fist page of the catalog every time. Like this: ... View more

Feature request from miketsl, posted on GitHub Jan 17, 2016 Is it possible (easily) to make one of the attribute products the default for the base configurable product? In other words, if I have black, red, and green watches.... someone clicks on the watch product, and the product details screen automagically shows a configurable default color. Also, if someone hits "add cart" from the catalog grid, it adds the configurable default color item. ... View more

Feature request from devdesco-ceo, posted on GitHub Jan 19, 2016 I have a situation where I have custom theme (Porto, based off blank theme) installed and active, and prepackaged Luma theme is not active anywhere in my Magento stores, so no need to trigger compilation on it. BWT when I run static content compiler, both Magento/blank, Magento/luma and Smartwave/porto are being compiled. That would be fine, but I am compiling 6 locales for my multistore/multilang setup, and that takes awhile, believe me! The command I trigger: php ./bin/magento setup:static-content:deploy en_US fr_FR de_DE pt_PT es_ES it_IT What can I do to pass a command to compiler to skip compilation of Magento/luma? ... View more

Feature request from MonteShaffer, posted on GitHub Jan 18, 2016 I have noticed that the Captcha plugin is available, and I have implemented in my Magento 2 store. However, in the past, I have used much simpler Captcha plugins, and am curious why this version is considered the core, without the option to choose from one of several Captcha plugins. A little counter-intuitive to the abstraction goals of Magento 2. For example, Visual Captcha ... drag and drop an icon ... or click on an icon to prove you are a human. https://github.com/emotionLoop/visualCaptcha-PHP ... View more

Feature request from riswit, posted on GitHub Jan 22, 2016 After weeks of research, I feel here. I want to set the robots meta tags - via XML - only in a static page, not all site. what is the equivalent of this code in magento 2? < reference name="head"> < action method="setRobots">< value>NOINDEX,FOLLOW Thank you!! ... View more

Feature request from mage2pro, posted on GitHub Jan 27, 2016 An example of the UI component XML declaration: https://github.com/magento/magento2/blob/c58d2d/app/code/Magento/Ui/view/base/ui_component/etc/definition.xml#L182-L188 ... View more

Feature request from lisovski, posted on GitHub Jan 22, 2016 Right now there is no way (I'm not sure) to remove columns from CSV/XML export using UI component. It would be good to have "is_system" config attribute in UI component (see Magento 1) to define the columns you don't want to export. ... View more

Feature request from seansan, posted on GitHub Mar 29, 2016 Request: build in simple functionality to inlcude guest users (hence their email) in the check if a coupon code is already used. @sonalagr Steps to reproduce Suppose we set-up a coupon code that can only be used once Guest users can check out with 2 orders and the coupon is still valid Expected result Second order the coupon code is invalidated (client already ordered with that username OR e-mail ... Actual result User can use the coupon code again Possible solution can be a setting in the backend to decide if we do or do ot want to include the check on email address for the count of number of times a coupon has been used References http://magento.stackexchange.com/questions/4785/magento-coupon-codes-only-one-coupon-guest-customer http://magento.stackexchange.com/questions/33598/magento-coupons-limit-per-use-o-per-customer-not-working https://github.com/magento/magento2/issues/776 https://community.magento.com/t5/Admin-Configuration-Questions/Coupon-One-Time-Use-for-Guest-User/td-p/23603 https://www.reddit.com/r/Magento/comments/2yq3vb/coupon_code_limit_1_use_per_coupon_not_working/ https://ecommerce.shopify.com/c/ecommerce-marketing/t/discount-code-limit-to-1-time-per-customer-154688 ... View more