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 sshymko, posted on GitHub Jan 13, 2015 Classes Magento\Catalog\Plugin\Model\Indexer\Category\Product\Execute and Magento\Catalog\Plugin\Model\Resource\Attribute\Save implement flushing the Full Page Cache. They should belong to the Magento_PageCache module, not the Magento_Catalog . Utilization of the constant Magento\PageCache\Model\Cache\Type::TYPE_IDENTIFIER rather than literal full_page would expose that dependency on the code level. ... View more

Feature request from avoelkl, posted on GitHub Jan 27, 2015 Given that you run a big shop with a lot of payment methods, some of the payment extensions bring a lot of unneeded/unwanted payment methods with them which appear in the payment method list. Of course you can generate a list and hide them via custom xml (at least in M1), but it's not very handy. Edit: To get an idea what I mean: Currently we have a shop which has 68 payment methods in this list. These 68 payment methods are added by 10 payment extensions whereas one of them brings > 20 possible payment methods. Only 8 of the payment methods are currently activated in the shop frontend. This makes the list quite confusing. The list under Configuration > Payment Methods can get quite long so I'd like to suggest to either 1 Highlight activated Payment Methods (having "Enabled" > "Yes") 2 Put the enabled payment methods on top incl. highlighting This would require to prioritize the status "Enabled" over the defined sort order. Another addition to this could be to sort them into activated and deactivated payment methods and hide the deactivated by default. I think version 1 would already bring an improvement. ... View more

Feature request from kassner, posted on GitHub Jan 30, 2015 Hi, I'm not sure if this is widely used, but I have some clients where the shipping cost is not the same that is charged from their customers. I often see M1 shipping modules with $rate->setCost(x.xx) , but that information is not saved anywhere. Can this be added to Magento 2 at least? Should I send a pull request? Thanks! ... View more

Feature request from seansan, posted on GitHub Jan 29, 2015 Request: ability to refresh cache (and FPC) per store We have many stores. And it becomes a problem when you are building/working on store B when store A is actually live and hence static. Now when we refresh the cache or all other related (like FPC) then it affects ALL stores ... this is a shame. It would be great if a store swticher or store selector could be added to throw away or relaod cache only for 1 specific store (dont know if this is possible) ... View more

Feature request from rvpatel, posted on GitHub Feb 09, 2015 Magento Customer Registration form on how to display Address field without customize like <?php $this->setShowAddressFields(true); ?> adding on before Line 56. <?php if ($block->getShowAddressFields()): ?> ... View more

Feature request from Flyingmana, posted on GitHub Mar 01, 2015 I currently have to do a plugin which replaces the Magento\Framework\App\Http->catchException() call, as plugins only work on public methods, and the protected handleDeveloperMode() directly sends the output. The current way I do this feels wrong, and I dont see another one which would work more modular, so I assume this should get improved. priority for me: low Context: I wrote a module which improves the display during errors https://github.com/Cotya/DebugModule ... View more

Feature request from seansan, posted on GitHub Mar 16, 2015 Please add option to avoid merging of cart on login of customer Many customers just do not understand Something like this https://github.com/jacquesbh/jbh_cartmerge http://stackoverflow.com/questions/5638173/how-do-i-stop-magento-merging-the-basket-on-login http://www.blog.magepsycho.com/clear-abandoned-cart-items-during-login-in-magento/ ... View more

Feature request from shirtsofholl, posted on GitHub Mar 26, 2015 Please add Magento store code to body class (as extra class) Now we have route + page-name cms-index-index cms-page-name I suggest to add webstore code (or even domain/url) and/or both cms-index-index cms-page-name store-en domain-com What does it solve? ability to set CSS per store view (so per language store-en) ability to set CSS per domain (so per domain-com) Maybe there is a better way. And there are ofcourse other methods to achieve someting like this - but it seems as a quick win ... ... View more

Feature request from avoelkl, posted on GitHub Feb 13, 2015 When working with various customer groups, it's not very handy to work with fixed ID's which are returned by getCustomerGroupId() . Working with customer group codes would be more flexible. Currently the name of the customer group is set as 'customer_group_code' in the admin. I would recommend to distinguish between name and code as the name might be something more user-friendly for backend admins whereas the code can be used for development. What are your thoughts on this? ... View more

Feature request from Pakkapao, posted on GitHub Mar 29, 2015 I'm using Adobe Acrobat v11. Store currency is THB, Thai - Baht. [Checkout Page] [PDF file] ... View more

Feature request from jason-neumann, posted on GitHub Mar 18, 2015 Currently credit memos don't store if their transaction was done online or offline. This can make it hard to tell what's happened to an order if there are multiple credit memo's applied to it. I suggest adding a column to sales_flat_creditmemo called online_refund that's a tinyint and is set to 1 if the refund is done online. This could then be added to the Credit Memo's main grid and when viewing an order and would enable quick filtering to see just the online or offline refunds. This has great benefits from the merchant standpoint because you can then easily reconcile refunds made through Paypal (or whoever your gateway is) and refunds made by cash or whatever other method. I would be willing to submit a pull request for the feature if it's something Magento is interested in. ... View more

Feature request from fr0x, posted on GitHub Feb 23, 2015 This may be fixed in Magento 2 (I dont have a current 2.x install to check but recently ran into this in a 1.6.2 install). The Manage Label / Options screen when you are editing an attribute has no limit on the number of options it displays. For one attribute, we have thousands of options. The admin screen tries to load every single one and it tends to cause the browser to crash/hang. ... View more

Feature request from kabel, posted on GitHub Jul 10, 2015 The mcrypt php extension and the underlying libmcrypt are unmaintained and there is a strong effort to remove them from the PHP core. [1] [2] This would be a good opportunity to port any password or data encryption to the better maintained openssl or password extensions. ... View more

Feature request from zbych, posted on GitHub Apr 05, 2015 Getting following error: Instance of Magento\Framework\Data\CollectionDataSourceInterface is expected, got Some\Backend\Class\Of\Model\Defined\ByMe instead. I am not sure if it is intended, if it is, and it is within the rules of core functionality, then please cancel this issue and sorry for bothering. I am just not sure if blocks can accept only objects that inherits the Collection interface. ... View more

Feature request from joh-klein, posted on GitHub Apr 16, 2015 The current region codes for Germany seem not to be widely known (a quick Google search didn't reveal a source for them). And some others seem to be impractical but most importantly will probably hinder exchanging addresses with other systems. I could provide a PR with the current data for regions from Wikipedia for these 13 countries (US, CA, DE, AT, CH, ES, FR, RO, FI, EE, LV, LT, BR). Right now I lean towards adding another column for backwards compatibility. Quick link to relevant source code: https://github.com/magento/magento2/blob/develop/app/code/Magento/Directory/Setup/InstallData.php#L300 ... View more

Feature request from CRYX2, posted on GitHub Jul 15, 2015 Hello everyone, I was trying version 1.0 beta and I noticed that it is still the old editor of Magento 1. I think that the best solution for ecommerce in 2015 is to be able to use a much more advanced editor and also known by various types of users who normally use a website (Copywriter, customers, etc ...). CKEditor can use and create many different plugins, which allow all supporters to be able to create new plugin fully integrated into Magento same. ... View more

Feature request from erikhansen, posted on GitHub Jul 13, 2015 I've been working with Magento 2 for the past couple of months. There have several times where I've tried to find what constant to use for the backend area and have been distracted by an inappropriate constant. The lib/internal/Magento/Framework/App/Area.php file contains these constants: class Area implements \Magento\Framework\App\AreaInterface { const AREA_GLOBAL = 'global'; const AREA_FRONTEND = 'frontend'; const AREA_ADMIN = 'admin'; If a developer is casually browsing the code, they may think that \Magento\Framework\App\Area::AREA_ADMIN is the appropriate constant to use to refer to the backend/adminhtml area. However this is another constant in a different class that is the appropriate constant to use when referring to the backend area: \Magento\Backend\App\Area\FrontNameResolver::AREA_CODE (the value of this constant is adminhtml ) To avoid this confusion for developers, I would recommend moving the backend constant into the \Magento\Framework\App\Area class and then add clear comments describing how the AREA_ADMIN constant differs from the AREA_ADMINHTML (or AREA_BACKEND , depending on what you decide to call it) constant. ... View more

Feature request from mage2pro, posted on GitHub Nov 13, 2015 For example, displaying the SKU to the customers would be unnecessary for some Virtual products (software, support, repair, consulting). ... View more