Magento 2.x Feature Requests and Improvements

I have big issue in magento 2 backend. When editing product which has custom options with different prices. After saving the product custom options price is changing automaticaly: My magento version is Magento CE 2.1 Example "custom option 1" price is 1500.00 After save: Expected result: custom option price should be 1500.00 Actual result: custom option price is 1.00 Is there any solution for this issiue? ... View more

Feature request from markoshust, posted on GitHub Sep 07, 2015 There is no documentation (or reference to other documentation) on implementing date & time selectors from the admin pattern library: http://devdocs.magento.com/guides/v2.0/pattern-library/getting-user-input/date_time_selector/date_time_selector.html ... View more

Feature request from mage2pro, posted on GitHub Jan 07, 2016 https://mage2.pro/t/196 Related to: https://github.com/magento/magento2/issues/2314, https://github.com/magento/magento2/issues/2359, https://github.com/magento/magento2/issues/2012 ... View more

Feature request from ezequielalba, posted on GitHub Jan 19, 2016 I'm getting this issue after run grunt exec:<theme> , this shows up: Processed Area: frontend, Locale: en_US, Theme: Ids/prueba, File type: less. >> [Magento\Framework\Exception\FileSystemException] >> Cannot create a symlink for "/usr/local/devs/magento2/htdocs/vendor/magento/theme-frontend-blank/web/css/source/_reset.less" and place it to "/usr/local/devs/magento2/htdocs/pub/static/frontend/Ids/prueba/en_US/css/source/_reset.less" Warning!file_get_contents(/usr/local/devs/magento2/htdocs/var/cache//mage-tags/mage---e39_INTERCEPTION): failed to open stream: No such file or directory >> dev:source-theme:deploy [--type="..."] [--locale="..."] [--area="..."] [--theme="..."] [file1] ... [fileN] >> Exited with code: 1. Warning: Task "exec:prueba" failed. Use --force to continue. And after i run grunt refresh , shows the same after it cleans all the paths. Now, running the command for the bin/magento dev:source-theme:deploy got this: Processed Area: frontend, Locale: en_US, Theme: Magento/luma, File type: less. [Magento\Framework\Exception\FileSystemException] Cannot create a symlink for "/usr/local/devs/magento2/htdocs/vendor/magento/theme-frontend-blank/web/css/source/_reset.less" and place it to "/usr/local/devs/mage nto2/htdocs/pub/static/frontend/Magento/luma/en_US/css/source/_reset.less" dev:source-theme:deploy [--type="..."] [--locale="..."] [--area="..."] [--theme="..."] [file1] ... [fileN] I was triyng to fix this by following a lot of instructions on other issues already, nothing worked. Any ideas why this might be happening? I have a VM configured running of Ubuntu 14.04.3 LTS , and have node 5.4.1 with npm 3.3.12 Update of the issue: If a run the bin/magento static:deploy and after that i run grunt less:theme it gives no errors, but when watching isnt detecting the changes in the .less files of the theme. ... View more

Feature request from will-b, posted on GitHub Oct 25, 2015 type="text/javascript" is not needed for script tags any more. http://www.w3.org/TR/html5/scripting-1.html app/code/Magento/Developer/Model/View/Page/Config/ClientSideLessCompilation/Renderer.php line 307 $attributes = ' type="text/javascript" ' . trim($attributes); ... View more

Feature request from tzyganu, posted on GitHub Jul 06, 2016 The class \Magento\Eav\Model\Entity\Attribute has as a dependency an instance of \Magento\Catalog\Model\Product\ReservedAttributeList . This is wrong in my opinion. Besides the fact that it introduces a circular dependency because EAV module now depends on the Catalog module and the Catalog module already depends on the EAV module. But this circular dependency is not the main problem here (others might disagree). The main problem is that the Catalog Product is not the only EAV entity in the application. There are also Categories, Customers and Customer addresses. This means that when I add an attribute for these entities Magento checks if there is a getter for that attribute name in the product model class. This also restricts me when creating my own EAV entity to have attributes like price (and others). I think the dependecy \Magento\Catalog\Model\Product\ReservedAttributeList should be replace with an interface ReservedAttributeListInterface that should reside in the EAV module with a single method isReservedAttribute and I can specify via di.xml the implementation used as dependency for each class that extends \Magento\Eav\Model\Entity\Attribute . ... View more

Feature request from TommyKolkman, posted on GitHub Aug 24, 2016 Magento widgets strip special characters like a "+". If I add something like: {{widget type="Elephant\CFTextAndImage\Block\Widget\CFTextAndImage" language="nl_nl" title_default="++Hallo++"}} The plusses are stripped. Now, in this case that's not that much of a problem, but in some cases we use base64 values there. When the base64 value has a plus, the value is instantly corrupted. I've tried to track it down and came to the conclusion that there is a problem with the following file: https://github.com/magento/magento2/blob/develop/lib/internal/Magento/Framework/Filter/Template.php The problem is in the tokenizer. /** * Return associative array of parameters. * * @param string $value raw parameters * @return array */ protected function getParameters($value) { $tokenizer = new Template\Tokenizer\Parameter(); $tokenizer->setString($value); $params = $tokenizer->tokenize(); foreach ($params as $key => $value) { if (substr($value, 0, 1) === '$') { $params[$key] = $this->getVariable(substr($value, 1), null); } } return $params; } The $value, before added to the tokenizer is still correct. Afterwards, however, it's missing the plusses. Now, I've tried writing up my own replacement for the tokenizer as quick fix, but that won't do. Can you guys fix this? Temp fix (via di.xml of course): // $params = $tokenizer->tokenize(); $params = array(); $count = 0; $widget_values = explode( '"', $value ); $param_key = ''; foreach( $widget_values as $widget_value ){ if( $count == 2 ){ $count = 0; } if( $count == 0 ){ // It's a key $param_key = trim( rtrim( $widget_value, '=' ) ); } else { // It's a value $params[ $param_key ] = trim( $widget_value ); } $count++; } ... View more

Feature request from adragus-inviqa, posted on GitHub Jul 17, 2016 php bin/magento Magento CLI version 2.1.0 On previous versions, we've been told to use setup:di:compile-multi-tenant instead of setup:di:compile . K. Now we're told to get back to using setup:di:compile . Ugh, fine. But whilst you were fixing (?) setup:di:compile , we've gotten accustomed to setup:di:compile-multi-tenant 's various and useful CLI options, which - yep - setup:di:compile does not have. And now that setup:di:compile-multi-tenant is gone, we're left with no.. option: php bin/magento help setup:di:compile Usage: setup:di:compile Options: --help (-h) Display this help message --quiet (-q) Do not output any message --verbose (-v|vv|vvv) Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug --version (-V) Display this application version --ansi Force ANSI output --no-ansi Disable ANSI output --no-interaction (-n) Do not ask any interactive question One of the more useful options which is now kaput was --exclude-pattern . That allowed us to omit certain files which we didn't want compiled, ofc. But now we're stuck with whatever you thought it was good for your scenarios. Can we get setup:di:compile to be as flexible as multi-tenant was? If not the same, at least allow us to inject our own exclude patterns. PS: I hope I won't be asked "Can you give me an example of a scenario in which you need to exclude something?". Just trust me on this one, mkay? ... View more

Feature request from Ctucker9233, posted on GitHub May 23, 2016 Steps to reproduce Fresh install of Magento 2 from CPanel Create 2nd root category with subcategories Create 2nd website, store and store view Note: At this point I could visit my base url and see no categories (I didn't add and categories to the default root category) then go to my new url which didn't have styles applied to it and see my categories and subcategories. Apply magento blank theme to new store view Expected result New url has selected theme applied and catalog navigation shows categories with subcategories Actual result New url shows the default theme (luma) and catalog navigation does not appear (remember, no subcategories in the default root category) ... View more

Feature request from fooman, posted on GitHub Apr 19, 2016 Expected result When a new Magento 2.x version is released a merchant can upgrade immediately Actual result When a new Magento 2.x version is released a merchant needs to wait for extension providers/ SIs to assess what changes have made it into this release Currently it seems the only time a module's version number can change is when the Magento 2 project releases. From an external developer's stand point a better approach would be for the modules to change their version number the moment a version number affecting change is merged into develop. This allows an external developer to follow development between releases without having to wait until the final avalanche of version number increases on release day and then having to play catch up with all changes in a short period of time. As a further suggestion the following policy would help extension developers prepare for an upcoming release: At the end of the penultimate sprint before release a Release Candidate is tagged (or earlier). From there until final release only patch level fixes are allowed on the Magento module level (if a fix is required that is breaking a new Release Candidate would be added). ... View more

Feature request from dnadle, posted on GitHub Aug 11, 2016 Preconditions Magento 2.1.0 Steps to reproduce Add a product attribute with multiple select input type and define several options (values). Choose a sku set some values for the attribute. GET the sku with /V1/products/{sku} Wrap the returned JSON body with { "product": <JSON GET result> }. PUT the sku with /V1/products/{sku} Edit the JSON body and set the attribute value to [] (empty array). PUT the sku again. Expected result The unchanged results of a GET should PUT without errors. A multi select attribute with a single option with id "123" selected should be sent as ["123"]. Multiple options selected should look like ["123","456"]. Putting a an empty array should clear all the selected options for the attribute. Actual result Putting an unchanged GET returns errors on the multiselect attribute: { "message": "Error occurred during \"custom_attributes\" processing. Attribute \"occasion\" has invalid value. Invalid type for value: \"string\". Expected Type: \"string[]\"." } If the attribute has a single option, it is sent as "123", not ["123"]. If the attribute has multiple options, it is sent as "123,456", not ["123","456"]. Putting an empty array does not remove whatever options are selected. ... 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 heldchen, posted on GitHub Sep 08, 2016 Preconditions CE 2.1.1 Steps to reproduce try to customise the address format in the mail footer Expected result you can customise the address format in the mail footer, for example putting the zip code in front of the city, as used in some European countries Actual result you cannot (easily) customise the address format as it is hardcoded: /** * Format address in a specific way * * @param DataObject $storeInfo * @param string $type * @return string */ public function format(DataObject $storeInfo, $type = 'html') { $this->eventManager->dispatch('store_address_format', ['type' => $type, 'store_info' => $storeInfo]); $address = $this->filterManager->template( "{{var name}}\n{{var street_line1}}\n{{depend street_line2}}{{var street_line2}}\n{{/depend}}" . "{{var city}}, {{var region}} {{var postcode}},\n{{var country}}", ['variables' => $storeInfo->getData()] ); if ($type == 'html') { $address = nl2br($address); } return $address; } sure, we could use an interceptor and completely forgo the current implementation, but really? at the least please add the template string into the event so it could be manipulated in an observer... ... View more

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 tstamplis, posted on GitHub Sep 08, 2016 Because Mangento (2.1.0 in this case) does $0 card authorizations on payflow pro now for credit card transactions, it is costing merchants .30 cents PER card authorization, on top of the .30 cent authorization attached to the actual sale. This adds up to hundreds of dollars per month in additional fees just because of this new way Magento handles payflo pro integration. I would request the ability to disable this "feature" so merchants that do not want to increase their processing fees for the sake of this method of authorization have the option to opt out. ... View more

Idea: Admin Functionality to remove decimals on price globally on the site (like prestashop, opencart) Example of a thousand 1.000     This will affect how magento works globally, in some countries is not necessary decimals and others is even ilegal. ... 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 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