Magento 2.x Feature Requests and Improvements

Feature request from amenk, posted on GitHub Sep 29, 2015 When installing a new theme, I would add it to dev/tools/grunt/configs/themes.js (according to http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/css-topics/css_debug.html#grunt_prereq) But this file is in the standard git ignore and would be overwritten when doing a composer update (if Magento is installed via composer) How can we fix this? Maybe an additional file custom_themes.js which is included if it exists? ... View more

Feature request from adragus-inviqa, posted on GitHub Apr 18, 2016 https://gist.github.com/adragus-inviqa/8c2496312760c122aefb390c66bf2419 That's a one liner copied from a response source and pretty-printed into 45587 lines. :trollface: I hope you agree that those countries desperately need a single global object. ... View more

Feature request from zolthan, posted on GitHub Apr 14, 2016 Steps to reproduce Create a grouped product and assign it to a category Create a Simple Product Add some tier prices to the Simple Product Assign the Simple Product to the Grouped Product Go to the category in the frontend Expected result The displayed price of the grouped product should be the minimal possible price. ie. the minimal tier price. Actual result The displayed price is the minmal normal price of the assigned simple products. The tier prices are not evaluated. ... View more

Feature request from joshdifabio, posted on GitHub Apr 11, 2016 Products can be uniquely identified by their SKUs, which have meaning to a business, but for categories there is no such business attribute in Magento; categories can only be identified by their integer ID, which has no business meaning. In Magento 1, this poses issues when attempting to integrate Magento categories with other platforms, for example Akeneo, because there is no way of relating the Magento category with the category in the other platform. From what I can see, this is still the case in Magento 2. So, I guess my question is this: Given a third party system which maintains category data in a format something like [code, name, parent_code, ...] , how can we use the Magento 2 API to create and later update and delete categories using the provided code as a unique identifier? If this isn't possible, then I think it needs to be. Most medium to large retailers have business identifiers for customers, categories, orders and many other things, not just products. ... View more

Feature request from Lewiscowles1986, posted on GitHub Oct 13, 2015 It's fantastic that you can take backups in Magento 2 for the three different areas, I have some suggestions I believe would make this more professional solution Ability to backup automatically to a schedule (not just when installing plug-ins) Default to exclude media from system backups Default to put system into maintenance mode during backup Ability to launch all three backups with formatting string "%Y-%m-%d %H%i backup db" "%Y-%m-%d %H%i backup sys" "%Y-%m-%d %H%i backup uploads" ... View more

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 devhn, posted on GitHub Jun 14, 2016 Steps to reproduce Install Magento 2.0.7 from community branch. Open any product page and copy it's URL to Google Structured Data testing tool Expected result Price property should be recognized. Actual result Price property is not valid (the property XXX € is not a valid price specification). Screenshoot for reference ... 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 seansan, posted on GitHub Nov 07, 2014 Please find our language switcher improvement for Magento 2 below. I think this is how it should work. And if you dont want to loose current method then we can create a backend config option that allows both methods PLease find full transcript here: http://magento.stackexchange.com/questions/42950/magento-multistore-languages-getting-the-locale-language-name-in-store-selector <!-- LANGUAGES BOF --> <?php if(count($this->getStores())>1): ?> <?php $stores = array(); $_current = null; $languages = Zend_Locale::getTranslationList('language', Mage::app()->getLocale()->getLocaleCode()); foreach ($this->getStores() as $_lang) { $_selected = $_selected_option = $_language_name = ''; $_language_code = substr(Mage::getStoreConfig('general/locale/code', $_lang->getId()),0,2); if (isset($languages[$_language_code])) {$_language_name = $languages[$_language_code];} $parts = explode('(', $_language_name); $_language_name = trim($parts[0]); if ( ($_lang->getId() == $this->getCurrentStoreId()) ) { $_current = $_lang; $_current_lang = $_language_name; $_selected = ' class="selected"'; $_selected_option = ' selected="selected"'; } // $stores[] = '<li'. $_selected .'><a style="background-image:url(\''. $this->getSkinUrl('images/flags/'.$_lang->getCode().'.png') .'\');" href="'. $_lang->getCurrentUrl() .'">'. $this->htmlEscape($_lang->getName()) .'</a></li>'; $stores[] = '<li'. $_selected .'><a style="background-image:url(\''. $this->getSkinUrl('images/flags/'.$_language_code.'.png') .'\');" href="'. $_lang->getCurrentUrl() .'">'. $this->htmlEscape($_language_name) .'</a></li>'; $select_stores[] = '<option '.$_selected_option.' value="'. $_lang->getCurrentUrl() .'">'. $this->htmlEscape($_lang->getName()) .'</option>'; } ?> <div class="header-switch language-switch"> <span><?php echo $this->__('Your Language:') ?> <span class="current"><?php echo $this->htmlEscape($_current_lang); ?></span> </span> <div class="header-dropdown"> <ul><?php echo implode('', $stores); ?></ul> </div> </div> ... View more

Feature request from seansan, posted on GitHub Dec 01, 2014 Add configuration setting to "no include default CMS page to sitemap" Set default CMS page in backend settings as homepage (in this case /homepage) This site domain is myshop.com Sitemap should contain myshop.com and not also myshop.com/hompage if the configuration setting (do not include default CMS page to sitemap is enabled) ... 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 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 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 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 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 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 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 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