Magento 2.x Feature Requests and Improvements

Feature request from gabrielqs, posted on GitHub Jun 20, 2016 Hi, Right now, when you enable/disable a module Magento's CLI clears the cache. That's helpful but there is still a lot to be done for a module to be really enabled while in production mode, ensuring the store is in an consistent state after it finishes. For instance, these are all the steps i take when doing enabling or disabling a module in production: Activate maintenance mode Enable/disable module (clears cache automatically and static content if we use the --clear-static-content parameter) Upgrade db resources Clear generated code (/var/generation AND /var/di) Compile code Static content deploy Disable maintenance mode IMHO it would be more difficult to break things in production mode if the enable/disable process took care of all those steps. It is inconsistent, even dangerous, that it only clears the cache at this point. I know it is possible to make things easier by creating a shell script that calls all of the necessary commands, but why not to make it automatic? The process will be the same for the biggest majority of the Magento user base after all. My suggestion: Create a flag on the system configuration allowing admins to enable the automation of modules enabling/disabling process when in production mode. When enabled, instead of simply clearing the cache, the module:enable and module:disable commands would take all necessary measures to ensure the store is on a consistent state after it finishes. The whole process when automation is enabled would be similar to what i have described above. This flag would be true by default. If in any specific case an user needs a different deploy process, the flag can be set to false and then a custom process can be applied. Regards, Gabriel ... View more

Feature request from seansan, posted on GitHub Apr 04, 2013 Add canonical tag als to CMS and BLOG pages (actually all pages) Duplicate content is not very good for seo. Would be good if Magento could actually ALWAYS on every page check for the base url and use the canonical tag. We can already set the canonical tag for products and categories, but not yet for other pages. Now we see duplicate content for these pages http://magefox.com/blog/adding-canonical-url-to-cms-pages.html http://magentoportico.com/blog/website-design/add-canonical-urls-to-magento-cms-pages/ http://www.mathewporter.co.uk/magento-canonical-meta-tag-on-cms-pages/ http://www.magentocommerce.com/wiki/adding_canonical_url_to_cms_pages How about we add this to core? Magento 1.8 and/or2.0 ... View more

Feature request from seansan, posted on GitHub Jun 17, 2013 Fix default Magento font in order PDF (and filesize of 1MB +) Please have a look at the code alterations here: http://magento.stackexchange.com/questions/4812/why-is-my-invoice-pdf-1mb How about we provide a font dropdown in backend to select our own font. And default this to Helvetica? Now users can choose. (and actually choose for small PDF files) ... View more

Feature request from simonspoerri, posted on GitHub Nov 21, 2013 Currently The indexing of Attribute Values used for the product filters in the category overview only index multiselect attributes that use attribute options. If a custom source model is specified the values are not indexed and thus are not taken into account when filtering products. To fix the issue in my case I created an interface which all Source Models that should be taken into account while indexing should implement. For Attributes implementing this interface not only attribute options from the DB are indexed but also all options provided by the source model. the class in question is Mage_Catalog_Model_Resource_Product_Indexer_Eav_Source . I've overridden the _prepareMultiselectIndex Method and added the following snippet after the attribute options are loaded from 'eav/attribute_option' foreach($attrIds as $attributeId) { $attributeModel = Mage::getModel(Mage_Eav_Model_Entity::DEFAULT_ATTRIBUTE_MODEL)->load($attributeId); if($attributeModel->getSource() instanceof MyNS_MyModule_Model_Product_Attribute_Source_Interface) { $sourceModelOptions = $attributeModel->getSource()->getAllOptions(); foreach($sourceModelOptions as $o) { $options[$attributeId][$o["value"]] = true; } } } Maybe I'm misusing some principles here but I really think custom source model based multiselect attributes should be filterable as well, thus they need to be indexed... ... View more

Feature request from ihor-sviziev, posted on GitHub Dec 07, 2013 For now we using ExtJS version 1.1 Beta 1 (https://github.com/magento/magento2/blob/master/pub/lib/extjs/ext-core.js). Why we use really old lib? For now latest ExtJS version - 4.2.1! ... View more

Feature request from ihor-sviziev, posted on GitHub Apr 08, 2014 Will be great remove index.php from admin url. ... View more

Feature request from 12th, posted on GitHub Feb 22, 2014 Hello. I apologize in advance if this functionality is. I would like to make a suggestion on the routes. It is very lacking in the short address with address bar of your browser. Now addressing Magenta works of principle: http:// domain.com / module / controller / action http:// domain.com / checkout / cart / updatePost It would be great if had the opportunity to register routes for specific modules, as is done, for example, in the framework Kohana: Route::set('default', '(controller(/action(/id)))') ->defaults(array( 'controller' => 'welcome', 'action' => 'index', )); Route::set('cart', 'cart(/param1)') ->defaults(array( 'directory' => 'checkoutDirectory', 'controller' => 'cartController', 'action' => 'indexAction', )); PS: example is slightly modified in order to convey the essence And then when you click on the address: http:// domain.com / cart working out the controller http:// domain.com / checkout / cart / index ... View more

Feature request from seansan, posted on GitHub May 22, 2014 Is it possible to add a new PDF generation mechanism in Magento 2 in CORE? Maybe based on HTML -> PDF or using advanced PDF editors? Something like: http://www.aromicon.de/magento-download-extensions-modules/en/aromicon-invoice-pdf-pro.html or http://www.magentocommerce.com/magento-connect/html2pdf.html Now it is almost impossible to change anything about the PDF documents without very advanced programming and changing complex files Many thanks ... View more

Feature request from airbone42, posted on GitHub Dec 22, 2014 Hi, I'm currently playing around with the plugin interceptors. Currently the only way to handle the order of plugins is by the sortOrder attribute. Unfortunately that's very lmiited as it only accepts a hardcoded integer value. Especially if you have dependencies between different modules it's very risky to use these, as if some other module changes it's sort order your extension might break. Would Magento be interested in a solution where you could define a before or after attribute (similar to the layout blocks) to define if a plugin should be run before or after any other specific plugin? For me that would be a great solution to also handle bigger dependency chains and it's less likely to break if when the amount of plugins is growing. What drawbacks can you see in this solution? ... View more

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 Flyingmana, posted on GitHub Jan 21, 2015 see: http://docs.travis-ci.com/user/uploading-artifacts/ Reason: You run several static analyzers like for example the phpcs part. This generates a report file if it fails. It would be helpfull if people can look into this somehow, for example trough the linked travis feature. ... 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 bgalileo, posted on GitHub Jan 14, 2015 In Magento 1, there is no easy way to add a user-friendly product, category or customer selection widget to a custom form. There are ways to add the product, category, cms page and cms block chooser widgets to your form, but the process is neither well-documented nor obvious, and a customer chooser widget simply doesn't exist. Since you often need to link information with specific customers, products or categories in custom modules, it should be easy to add a form element which allows the user to select one or multiple product/category/user IDs via the corresponding grids, which are then submitted together with the form. ... 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 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 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 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 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 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