Magento 2.x Feature Requests and Improvements

Feature request from ruby10, posted on GitHub Jun 21, 2016 Hi there, I have an issue regarding setting fields in invoice create API POST "V1/invoices" with payload { "entity": { "base_discount_tax_compensation_amount": null, "base_shipping_discount_tax_compensation_amnt": null, "discount_tax_compensation_amount": null, "order_id": 58, "shipping_discount_tax_compensation_amount": 0, "total_qty": 2, "grand_total": 155, "subtotal": 150, "items": [ { "base_discount_tax_compensation_amount": null, "discount_tax_compensation_amount": null, "order_item_id": 74, "sku": null, "qty": 56, "row_total": 150, "tax_amount": 152, "discount_amount": 23, "price": 154 } ] } } Here I am setting fields "grand_total", "subtotal" on body level and fields "qty", "row_total", "tax_amount", "discount_amount" inside items array. As a API user, I am expected to pass Magento API with orderId, Items object array with order_item_id and qty, shipping cost ( again validation where this cost should be less then order shipping cost ) , but if I just provide these fields , they are displayed as '0' in invoice created on admin panel ... View more

Feature request from karanbhomiagit, posted on GitHub Jun 29, 2016 Steps to reproduce Install Magento from develop branch. Try creating a simple product by making a call to REST API POST /V1/products. [Example] { "product": { "sku": "atoi-item", "name": "atoi-item", "status": "1", "type_id": "simple", "visibility": "4", "attribute_set_id": "4", "price": "3", "custom_attributes": [ { "attribute_code": "description", "value": "descreeeeeeption" }, { "attribute_code": "category_ids", "value": [ "1", "2" ] } ] } } I get a response : Status code 400. Body : { "message": "Unable to save product" } Expected result Error message in the response body should be more specific. There are so many field values that are required to be set on the request JSON, there is no way for the person making the request to identify where the request went wrong. Actual result [Example] Error message appears: "Unable to save product". ... View more

Feature request from flancer64, posted on GitHub Jun 15, 2016 Hello, there is protected property "select" in AbstractSearchResult that is never used /** * @var \Magento\Framework\DB\Select */ protected $select; ... and there is 'query' property in the constructor that is not defined: public function __construct( \Magento\Framework\DB\QueryInterface $query, ... ) { $this->query = $query; ... } I suppose this code: /** * @var \Magento\Framework\DB\Query */ protected $query; should be instead of 'select' property. ... View more

Feature request from basselalaraaj, posted on GitHub Jul 26, 2016 fixes #5805 ... View more

Feature request from adlogic, posted on GitHub Jun 24, 2016 Steps to reproduce $trigger = $triggerFactory->create(); $trigger->setTable('some_table'); $trigger->setTime(Trigger::TIME_BEFORE); $trigger->setEvent(Trigger::EVENT_INSERT); $trigger->setName('some_trigger'); $trigger->addStatement('/* dummy */'); $setup->getConnection()->createTrigger($trigger); Expected result Trigger is successfully created. Actual result [PDOException] SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ';END' at line 13 More info Magento generates following query: CREATE TRIGGER some_trigger BEFORE INSERT ON some_table FOR EACH ROW BEGIN /* dummy */; END So, ::addStatement should use some heuristics for auto-adding semicolon after each statement, or doesn't add it at all. ... View more

Feature request from dzotic9, posted on GitHub Jun 16, 2016 Steps to reproduce Magento CE 2.0.7 + sample data App server nginx+php-fpm, Varnish for FPC default.vcl file - http://pastebin.ru/gsQnLUh0 Expected result Page should be cached with all resources Actual result Cached only static resources, html not cached. Same requests (main page or same search requests) go to app server ... View more

Feature request from Corefix, posted on GitHub Aug 05, 2016 A problem will occur when you are adding any success message and the quickly changing page, fx adding a product to cart and then going to another page before the 3 seconds pass. This is especially true when dealing with production mode sites with all cache enable. I'm not a Javascript wizard so not sure any time is needed at all. But it should definitely be decreased. If their have been any thoughts on why this is 3 seconds I would love to know it. ... View more

Feature request from fooman, posted on GitHub Aug 05, 2016 UI Components are not easy to use - for an intro see http://alanstorm.com/magento_2_introducing_ui_components ... View more

Feature request from allanpaiste, posted on GitHub Aug 04, 2016 Currently it's not possible to create an 'image' EAV attribute for category as the code in many places has been hardcoded to talk only with attribute that is explicitly been named 'image'. This PR addresses that problem by steering the code towards more generic approach to the whole situation by detecting all matching attributes via backendModel check. Related issue: https://github.com/magento/magento2/issues/5438 ... View more

Feature request from dvynograd, posted on GitHub Aug 07, 2016 This PR is fixing the issue that happens due to crashes during merging xml layout updates for widgets. STEP TO REPRODUCE Create a new widget. Specify the next settings: Type: CMS Page Link (Can be any widget which has user filling fields in widget the option section). Design Package/Theme: Magento LUMA Assign to Store Views: All store view. Layout Updates: Add Layout Update -> Display on -> All pages. Widget Options: Anchor Custom Text: “ Anchor Custom Title: “ Save a widget, clear the cache and open any page on the frontend. E.R. See new link added to a page. A.R. Exception is appeared (see 1133837156634.txt ) Note The issue is reproducible for any html character. This problem was fixed by adding CDATA in xml source. But also there is a second case with special character see 1.xml.txt That part of issue was fixed by changing filter to ENT_DISALLOWED in htmlspecialchars function. ... View more

Feature request from sjovanig, posted on GitHub Aug 10, 2016 ... View more

Feature request from meng-tian, posted on GitHub Aug 12, 2016 The REST endpoint of product list is: http://<magento_host>/rest/<store_code>/V1/products It is intuitive to think the result of this endpoint should be filtered by <store_code> . For instance, specifying store code default should return products in default store; specifying store code all should return all products. However, in Magento 2.0.8, specifying different store code return the same result. This issue also apply to Magento 2.1.0 (#5723). This pull request will take <store_code> into consideration when retrieving products. A plugin is enabled only for web services areas. The plugin is not enabled for global dependency injection configuration as it may affect users in other areas, e.g., front store. Note: this pull request depends on #6095. ... View more

Feature request from meng-tian, posted on GitHub Aug 10, 2016 The current implementation of \Magento\Catalog\Model\ProductRepository::getList does not allow filter products by stores. When specify store_id filter in $searchCriteria , an exception throws Invalid attribute name: store_id . This pull request adds support for store filtering by using the \Magento\Catalog\Model\ResourceModel\Product\Collection::addStoreFilter method. ... View more

Feature request from springimport, posted on GitHub Aug 08, 2016 What about add Additional info section in new issue template? Example. Additional info Q A Magento version 2.1.0 PHP version 7 x64 Operating system Windows 10 x64 ... View more

Feature request from ednacool, posted on GitHub Aug 04, 2016 Special Price From Date to Date not coming on configurable products at backhand i wanna show deal price via this but unfortunately this is not coming Magento ver 2.1.0 ... View more

Feature request from paales, posted on GitHub Aug 15, 2016 Preconditions Magento 2.1 Steps to reproduce Run bin/magento setup:upgrade Expected result It only shows what it actually modifies Actual result It shows the names of all modules, making it hard to pick anything up what has changed. ... View more

Feature request from elioermini, posted on GitHub Aug 17, 2016 I think would be useful to have like in M1 the method streamOpen() . There is no other way to initialise the field $_streamHandler of the class File. Other methods in the class File rely on the initialisation of $_streamHandler and having it null I suppose that leaves the class just possible to use only extending it. ... View more

Feature request from techteamus, posted on GitHub Aug 14, 2016 Affected version: Community 2.1.0 During test deployments of my Magento 2 setup I continually ran into problems if I used a language other than en_US. After running the setup and a 'bin/magento setup:static-content:deploy en_GB' the front end files would display just fine but the admin interface was missing all the CSS etc. I eventually traced the problem back to how the initial admin user is created. Regardless of what language is chosen during setup the admin user is always setup with the interface locale as en_US. To me this seems counter intuitive, the initial admin user should be configured with the same language as the store configuration. Changing the admin user interface locale to en_GB in the database (not recommended) solves the problem instantly and the admin interface displays as expected. If the initial admin user was correctly configured this would have saved me time and I have no doubt other people are trudging around in circles try to resolve what looks like a complex issue but is in fact a simple configuration problem. ... View more

Feature request from sumihiro, posted on GitHub Aug 22, 2016 I want to use Text Swatch Attribute with long text. But Default Store View value cannot be saved correctly. It will be shrink. Preconditions I'm using Magento2.1.0, and MySQL 5.6.30. Steps to reproduce Create new Attribute, and select Text Swatch. Set long text to Default Store View in Manage Swatch. Like: "01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 " Save Attribute. Expected result Default Store View value is saved full length. Actual result Value is shrink. Like: "012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234" May be, it is caused by limitation of max varchar length (255) of MySQL. mysql> desc eav_attribute_option_value; +-----------+----------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-----------+----------------------+------+-----+---------+----------------+ | value_id | int(10) unsigned | NO | PRI | NULL | auto_increment | | option_id | int(10) unsigned | NO | MUL | 0 | | | store_id | smallint(5) unsigned | NO | MUL | 0 | | | value | varchar(255) | YES | | NULL | | +-----------+----------------------+------+-----+---------+----------------+ 4 rows in set (0.00 sec) How to save value correctly? ... View more