Magento 2.x Feature Requests and Improvements

Feature request from markoshust, posted on GitHub Aug 13, 2015 Here is a screenshot of a module that is in development: The deep nesting is a bit extreme and I don't think it is needed, specifically in regards to the name="children" elements. Is there any way to consolidate these by attribute rather than element, so setting something like is-child="true" accomplishes the same thing? I haven't explored the Magento 2 XML layers significantly, however I'm assuming this appears in a few different other locations as well. Anything to assist us devs debugging this very deep nesting would be helpful. ... View more

Feature request from steig, posted on GitHub Aug 18, 2015 Customer group codes are limited to 32 chars and if there is a valid reason to keep them at 32 that makes sense, but I really can't find a reason right now as to why. If they can be increased, would 64 be enough? ... 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 markoshust, posted on GitHub Sep 07, 2015 There is a flag on the ./bin/magento module:enable command: --clear-static-content Unfortunately, this only appears to be on the module-enable option. If static assets are desired to be cleared at any other time, this isn't an option. I believe there should be a new command under ./bin/magento that just clears this static content, something like: ./bin/magento cache:clear-static-content I'm not sure if static assets are considered a cached asset, so this may need some revision. Thanks! Mark ... View more

Feature request from markoshust, posted on GitHub Sep 10, 2015 Clicking on the dropdown box next to a content page shows: However, the Preview option is either named bad, or has non-existent functionality. To properly "preview" a page, there needs to be the ability to make edits to a page, save it, and publish it at a later date, so you can "preview" the page before it is published. However, you really aren't previewing anything here, as that link just shows you the page as it is already published on the frontend site. I believe there should either be full preview functionality added (ability to make edits, "preview" changes (before they are made viewable to the public), and then be able to publish the desired updates. It's possible this could be done on the content edit page without revision tracking, however if this is the case, the "preview" option should be removed from the content grid view, because it's not appropriate here. I don't think the option to view the page on the frontend website is bad, but if this is kept in, it should be renamed "View", and also open in a new window so it doesn't kick you out of the admin. ... View more

Feature request from SasiKiranK, posted on GitHub Sep 26, 2015 So far i have created the new layout called new layout inside my page_layout folder and copied the content of empty layout. and the head content coming from the root.phtml. which i am unable to overwrite. In mangento 1, i have done same using the new layout file.phtml i have removed <?php echo $this->getChildHtml('head') ?> This allows me to remove the head section. Since magento can able to create any web app. i need to create a bank page using new layout. ... View more

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 mage2pro, posted on GitHub Oct 08, 2015 What is the sense to show the customer name twice? The first block is welcome message. The second block is the customer menu. Please note that the welcome message for authenticated customers can not be changed or disabled in admin panel. ... 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 rtull, posted on GitHub Apr 04, 2016 In the "rules" interfaces in the admin panel (see Customer Segments or Promotions) selected objects show their ID, not a friendly name. This makes it very difficult in the admin to assess what values have been selected in a rules section because the IDs shown are not comprehend-able. Without loading the full selection list / grid interface, an admin user has no idea which specific items they have selected. For example, selecting a particular category as a filter criteria show the category ID, not the category name. An admin user would have no idea which category this is without loading the category selector - which both time-consuming and non-obvious. Recommend displaying admin text values instead of IDs to improve human administrator comprehension and admin speed of use. Example Screenshot: http://files.classyllama.com/c689cb8e/mage2_admin_id.png ... 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 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 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 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 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