Magento 2.x Feature Requests and Improvements

Feature request from azeemism, posted on GitHub Sep 02, 2016 Running php bin/magento setup:backup --code --media --db as www-data creates a *_db.sql file instead of a *_db.gz file as indicated in http://devdocs.magento.com/guides/v2.1/install-gde/install/cli/install-cli-backup.html . The backup was run while in developer mode. I have not tested under production mode, but I expect the same result. Obviously as the database sizes grows this will become a major space concern. The Restore/Rollback seems to work, but there is another major issue refer to #6460 . Preconditions: Magento 2.1.1 CE (Composer install) php bin/magento deploy:mode:set developer Mariadb root@skynet:/# dpkg -l | grep mariadb ii libmariadbclient18 10.1.16+maria-1~jessie amd64 MariaDB database client library ii mariadb-client 10.1.16+maria-1~jessie all MariaDB database client (metapackage depending on the latest version) ii mariadb-client-10.1 10.1.16+maria-1~jessie amd64 MariaDB database client binaries ii mariadb-client-core-10.1 10.1.16+maria-1~jessie amd64 MariaDB database core client binaries ii mariadb-common 10.1.16+maria-1~jessie all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf) ii mariadb-server 10.1.16+maria-1~jessie all MariaDB database server (metapackage depending on the latest version) ii mariadb-server-10.1 10.1.16+maria-1~jessie amd64 MariaDB database server binaries ii mariadb-server-core-10.1 10.1.16+maria-1~jessie amd64 MariaDB database core server files PHP 7.0: root@skynet:/# dpkg -l | grep php7 ii libapache2-mod-php7.0 7.0.9-1~dotdeb+8.1 amd64 server-side, HTML-embedded scripting language (Apache 2 module) ii php7.0 7.0.9-1~dotdeb+8.1 all server-side, HTML-embedded scripting language (metapackage) ii php7.0-cli 7.0.9-1~dotdeb+8.1 amd64 command-line interpreter for the PHP scripting language ii php7.0-common 7.0.9-1~dotdeb+8.1 amd64 documentation, examples and common module for PHP ii php7.0-curl 7.0.9-1~dotdeb+8.1 amd64 CURL module for PHP ii php7.0-fpm 7.0.9-1~dotdeb+8.1 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary) ii php7.0-gd 7.0.9-1~dotdeb+8.1 amd64 GD module for PHP ii php7.0-igbinary 1.2.1-1~2b7c703-1~dotdeb+8.2 amd64 igbinary serializer for PHP ii php7.0-imagick 3.4.2-1~dotdeb+8.2 amd64 Provides a wrapper to the ImageMagick library ii php7.0-intl 7.0.9-1~dotdeb+8.1 amd64 Internationalisation module for PHP ii php7.0-json 7.0.9-1~dotdeb+8.1 amd64 JSON module for PHP ii php7.0-mbstring 7.0.9-1~dotdeb+8.1 amd64 MBSTRING module for PHP ii php7.0-mcrypt 7.0.9-1~dotdeb+8.1 amd64 libmcrypt module for PHP ii php7.0-mysql 7.0.9-1~dotdeb+8.1 amd64 MySQL module for PHP ii php7.0-opcache 7.0.9-1~dotdeb+8.1 amd64 Zend OpCache module for PHP ii php7.0-pspell 7.0.9-1~dotdeb+8.1 amd64 pspell module for PHP ii php7.0-readline 7.0.9-1~dotdeb+8.1 amd64 readline module for PHP ii php7.0-redis 3.0.0~rc1-1~dotdeb+8.2 amd64 PHP extension for interfacing with Redis ii php7.0-soap 7.0.9-1~dotdeb+8.1 amd64 SOAP module for PHP ii php7.0-xml 7.0.9-1~dotdeb+8.1 amd64 DOM, SimpleXML, WDDX, XML, and XSL module for PHP ii php7.0-xsl 7.0.9-1~dotdeb+8.1 all XSL module for PHP (dummy) ii php7.0-zip 7.0.9-1~dotdeb+8.1 amd64 Zip module for PHP Debian root@skynet:/# cat /proc/version Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) root@skynet:/# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.5 (jessie) Release: 8.5 Codename: jessie Steps to reproduce Install magento 2.1.0 with composer Upgrade to 2.1.1 (while in developer mode) "require": { "magento/product-community-edition": "2.1.1", "composer/composer": "@beta" }, "minimum-stability": "stable", "prefer-stable": true, "repositories": [ { "type": "composer", "url": "https://repo.magento.com/" } composer update php bin/magento setup:upgrade php bin/magento setup:di:compile php bin/magento --ansi setup:static-content:deploy en_CA www-data@skynet:~/example.com/magento/2.x/2.x$ php bin/magento setup:db:status All modules are up to date. www-data@skynet:~/example.com/magento/2.x/2.x$ php bin/magento -V Magento CLI version 2.1.1 Switch to or stay in developer mode php bin/magento deploy:mode:set developer Create a backup php bin/magento setup:backup --code --media --db as www-data NOTE: Steps 1 (install 2.1.0) & 2 (upgrade) may not be required to reproduce the issue, and I also expect the same issue if a backup is run in production mode (but I have not tested with production mode). Expected results Database file created with format *_db.gz as indicated in http://devdocs.magento.com/guides/v2.1/install-gde/install/cli/install-cli-backup.html Actual results Database file creates with format *_db.sql Enabling maintenance mode Code backup is starting... Code backup filename: 1472779824_filesystem_code.tgz (The archive can be uncompressed with 7-Zip on Windows systems) Code backup path: /var/www/example.com/magento/2.x/2.x/var/backups/1472779824_filesystem_code.tgz [SUCCESS]: Code backup completed successfully. Media backup is starting... Media backup filename: 1472779824_filesystem_media.tgz (The archive can be uncompressed with 7-Zip on Windows systems) Media backup path: /var/www/example.com/magento/2.x/2.x/var/backups/1472779824_filesystem_media.tgz [SUCCESS]: Media backup completed successfully. DB backup is starting... DB backup filename: 1472779824_db.sql DB backup path: /var/www/example.com/magento/2.x/2.x/var/backups/1472779824_db.sql [SUCCESS]: DB backup completed successfully. Disabling maintenance mode www-data@skynet:~/example.com/magento/2.x/2.x$ ls -lht var/backups/ total 43M -rw-rw-r-- 1 www-data www-data 547K Sep 1 18:31 1472779824_db.sql -rw-rw-r-- 1 www-data www-data 60K Sep 1 18:31 1472779824_filesystem_media.tgz -rw-rw-r-- 1 www-data www-data 43M Sep 1 18:31 1472779824_filesystem_code.tgz 3. I do not see any errors showing up in ${webroot}/var/log/system.log. Thanks. ... View more

Feature request from senthilengg, posted on GitHub Sep 02, 2016 Preconditions Magento 2.1 PHP 5.6 , Nginx+PHP-Fpm Steps to reproduce Create a new User Role. Content --> Pages should only be allowed. Assign the role to any user. Login with the above user credential and make sure you have access to only Pages. Go to Pages Click Add New Page --> Click Content --> Click Show Hide Editor ( Press F5 or refresh the page ) Try Insert Widget --> Select Catalog Product List from drop down --> Click the + icon to select products -- > Click list icon Expected result Tiny Mce should be viewed. Product list should show up for selection. Actual result Editor not displayed. Page refreshed. ... View more

Feature request from SRaromicon, posted on GitHub Sep 25, 2014 It would be great to get an extra field for attributes, that holds the unit of an numeric / decimal attribute. Now you have to save every attribute, which has an unit like mm, oz or V, as an attribute of type varchar. In very large stores with more than 2000 attributes the varchar table becomes very large and the other tables are not used, because you need the unit of meassurement. ... View more

Feature request from paales, posted on GitHub Nov 17, 2014 In the light of the new Postgres 9.4 features: indexed JSONB, wouldn't it be awesome if Magento supported it. JSONB (brought into mainline in 9.4) -> Ideal replacement for flat tables, performance is on par (or better) than MongoDB. Flexible full-text search (brought into mainline in 8.2) -> Ideal for a simple search when SOLR is too much Multiple replication options to suit your environment and requirements Uses multi-version concurrency control, so concurrent performance rocks Fully ACID compliant (innodb is as well) Well-documented Strong access-control framework Materialized Views There are probably a 1000 more features that I can't think of, but I think you get the point. I understand Magento would like to support MySQL as well because it is more entry level and Magento has some abstract resource methods which should support other databases, but in practice Magento currently only supports MySQL. Better official support and feature integration would be awesome. ... View more

Feature request from seansan, posted on GitHub Dec 01, 2014 Would it be possible to add a config option per payment method that allows us to set and use the payment option for backend only? http://magentotoolkit.com/code/magento-admin-only-payment-method/ ... View more

Feature request from snky1987, posted on GitHub Jan 05, 2015 When I was in a sample category (201) and changed store group in a footer I received 404 error (which is correct). I think it may be useful to reset view into main view when change store group (unless there is a option to show different products under the same category depends on store group). It's not a bug but I am 99% sure that it will come back as an issue to any agency that set up Magento multi-store. ... View more

Feature request from navarr, posted on GitHub Feb 05, 2015 Suggested Labels: feature request, up for grabs Request Autocomplete is a web technology implemented in Chrome that enables very speedy entry of a customers credit card details, addresses, and more. It is very simple to implement, and would be a general improvement to Magento in all forms. More information: HTML5 Rocks page HTLM5 Rocks Demo Store (check it out!) Firefox browser implementation bug Previous Art: Magento1 Extension by the Chromium team ... View more

Feature request from kassner, posted on GitHub Feb 06, 2015 Hi, Can you guys think about merging all customer's name-related fields ( prefix , firstname , middlename , lastname and suffix ) into a single name field? I think this makes magento a more international product. Motivational literature: http://www.w3.org/International/questions/qa-personal-names http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ http://blog.jgc.org/2010/06/your-last-name-contains-invalid.html Thanks! ... View more

Feature request from airbone42, posted on GitHub Feb 09, 2015 Currently it's only possible to have one role per admin user, which is quite difficult to handle if you have multiple users which have overlapping roles. E.g. we have usually Editors and Sales people. So we need two roles. Besides that we also have people who're allowed to do both, so we already have to maintain three roles which have a very big overlap in the ressources. We always have to update all the roles if something in the ressources changes. This problem gets even bigger if you have three or four normal roles which have to be mixed up. Also the ressources which everyone should have, like the section to change the own password has to be added to every role individually instead of just having a "my account" role which you have to maintain only once and add it to every user. ... View more

Feature request from navarr, posted on GitHub Feb 27, 2015 Suggested Labels: feature request, up for grabs Email highlights allow email providers programmatic knowledge of the contents of email. This is a wonderful user experience, and one that would be beneficial in Magento's default email templates. These Highlights are currently in a standardization process, however they are already implemented in Gmail as action buttons, Inbox by Gmail (as rich data), and Google Now (as rich data). The two highlights that Magento would most benefit from are the Order and Parcel Delivery Highlights, linked here: Order Highlight Parcel Delivery Highlight ... View more

Feature request from seansan, posted on GitHub Mar 17, 2015 When one build up product reviews and a second store is opened. Then the product reviews are not enabled (selected from scope list) in the second store. This can be done manually, review per review. There should be a method to mass update product reviews to enable them in other store views. Some more information here http://magento.stackexchange.com/questions/55716/sql-to-make-product-reviews-available-in-other-store ... View more

Feature request from seansan, posted on GitHub Mar 17, 2015 It should ne able to pre-select a layered navigation filter for a category: meaning, that when opening the category page, then a layered navigation filter is already applied Suppose you sell shoes (configurable product) and you have a category stating to show all shoes in size 10 you would then create a normal shoe category (select all shoe products) then selected the (new setting) for a layered navigation pre-select filter for size 10 this way only shoes available in size 10 are shown http://magento.stackexchange.com/questions/55191/magento-set-selected-filter-in-layered-navigation ... View more

Feature request from fooman, posted on GitHub May 07, 2015 Custom Totals are a great feature of Magento. I do believe we can improve their implementation and reduce overall complexity by keeping custom totals in separate dedicated database tables similar to how we store line items. With the current structure to add a new custom total to cover base and order currency plus tax, at my last count, one has to add: 1.) 13 columns to table sales/order 2.) 4 columns to sales/invoice 3.) 4 columns to sales/creditmemo Not everyone gets this right including for example Enterprise custom totals: getData('base_' . $code) vs. sales/order::gw_card_base_price_invoiced I believe if we had the following tables sales/order_totals sales/order_invoice_totals sales/order_creditmemo_totals with the following columns: total_id parent_id code amount base_amount tax_amount base_tax_amount calculation_order and additionally for the sales/order_totals table description amount_invoiced base_amount_invoiced amount_refunded base_amount_refunded tax_amount_invoiced base_tax_amount_invoiced tax_amount_refunded base_tax_amount_refunded this would help a lot with the aim to a.) remove duplication of efforts (every custom total shouldn't need to add all these columns) b.) take away complexity of having to set up the database to reduce chances for errors Additionally to keep track of tax I think these should be linked through to the same table that we use to keep track of taxed items to allow for multiple taxes on the totals (and be able to reconstruct this later). If we don't link to the tax table we should at least add tax_percentage . ... View more

Feature request from hostep, posted on GitHub May 09, 2015 Hi This is mostly based on Magento 1 experience, but it looks like not much has changed in Magento 2 currently (testing 0.74.0-beta8). I'm not a VAT expert, I'm simply getting this from feedback we get from store owners who complain about how bad this is currently implemented in Magento 1. So with Magento 2, it would be a good idea to try to get this right from the start. Here are some suggestions, please review them, maybe there are better solutions then the ones I'm suggesting ... If you go through the checkout, you should get instant feedback when you enter a VAT number if it is valid or not, and not after you go through the whole purchase process and it is too late. With the instant feedback you can correct your VAT number before purchasing if you made a typo. We have experienced a lot of issues with the VAT API service which is currently used in Magento (= VIES VAT number validation), it happens very regularly that the API service is down or times out. So you should think about some kind of way to handle this. Maybe there are alternative API services? Maybe you can do a first preliminary check using regular expressions before going to the API service to lower the load on the service? Maybe add a switch in the backend where store owners can choose what happens when the API service is down: allow the customer to proceed, or let them try again until the API service is back up? Right now you aren't allowed to enter your country prefix in front of the VAT number, since it uses the country from your address. I believe you should clearly state this in a line of text or in a tooltip or something like that, so the customers know what to enter. Also: it makes a lot more sense to put the VAT number field after the country selector field, because it depends on that value (the same thing applies to the state/region field, but that's another issue). If others have some opinions about these issues or have other suggestions, please leave a comment, so we can try to improve how Magento 2 handles the EU VAT number validation. Credit where credit's due: most of these suggestions come from a commercial extension we used a few times in the past: https://www.geissweb.de/eu-vat-enhanced-magento-extension.html, but since the current implementation in Magento is pretty broken, we shouldn't depend on an extension to fix these bugs in Magento I believe? ... View more

Feature request from chrom, posted on GitHub May 26, 2015 extend global product search through search the pages of the blog (CMS page) ... View more

Feature request from CRYX2, posted on GitHub Jul 08, 2015 Hello to all, it think it could be very usefull creating a media library for storing and retreving all uploaded files (for example like the Drupal media module: https://www.drupal.org/project/media). It's very usefull for the users reusing an uploaded file for a product or for a custom entity (like news or blogs). ... View more

Feature request from seansan, posted on GitHub Jul 25, 2015 Request for ability to add new cart rule action - type cart id Now it is not possible to give a discount on the FIRST item only For instance we have a deal: the first T-shirt with 50% off ... (as a try out) If the cart ID can be used in a rule action then this is possible Concrete: please add cart id as a new rule type ... View more

Feature request from markoshust, posted on GitHub Jul 29, 2015 This doesn't exist in M1 but I believe it should be in M2. There are times when shipments are created by accident, or the customer calls to cancel their order. In those circumstances the shipment should be able to be deleted or canceled. ... View more

Feature request from chasteIT, posted on GitHub Sep 03, 2015 Problem: Customers use layered navigation to filter to their desired product, but if the user selects a configurable products from the category, they must select the same options again to configure the product before getting the associated simple product. Solution: Use the options selected in the layered navigation filters to pre-select configurable product options. Example: A category of Shoes (configurable product) has layered navigation filters for Size, Color, etc. In the category, a user selects filter attributes for Size10 and ColorRed to find the products with Red, Size 10 shoes. As Magento is now, the user clicks on their desired shoe to go to the configurable product page and must then select the attributes again to configure their product. We could skip this step by using the Size10 and ColorRed filtered attributes to pre-select those same attributes on the configurable product page. This improvement could go hand-in-hand with the issue: Set Configurable Product Default Configuration #1783. ... View more