Status:
Investigating
Submitted on
08-30-2016
11:59 AM
Submitted by
apiuser
on
08-30-2016
11:59 AM
Feature request from Asitis, posted on GitHub Jun 13, 2016
Personally I found it a bit strange that when I click any item in a table in the backend, it opens a 'Quick Edit' in stead of the expected single-view-screen for that item (like how the WordPress admin functions).
But I can get used to it.
What I think would improve the usability tons is adding two little tweaks to the Quick Edit screen;
Add an "Edit" (and maybe "Delete") link on the right side (the same as in the "Actions" dropdown)
Bind the Enter key to the Save button for quicker inline editing
It's quite bothersome that if I want to edit or delete an item, I have to click open a submenu and if I don't click completely right the first time, I have to 'deselect' the item to get out of the Quick Edit and try again. It would be logical to add the same functionalities of the "Actions" submenu to the Quick Edit screen.
... View more
Status:
Investigating
Submitted on
08-30-2016
11:59 AM
Submitted by
apiuser
on
08-30-2016
11:59 AM
Feature request from peec, posted on GitHub Jul 19, 2016
When changing the quantity of a product from any number to 0, the state is automatically changed to Out of Stock upon saving. However, when changing an out of stock product to any number and saving, the product is still listed as Out of Stock.
Steps to reproduce
Access an active, out of stock product through Products > Catalog
Change Quantity to any number and save
Expected result
The product’s state is automatically changed to In Stock
Actual result
The product is still listed as Out of Stock despite the quantity change.
One must manually remember to also set In Stock which is a inconvenient step and not working as one would expect because the other way the state is changed.
... View more
Status:
Investigating
Submitted on
08-30-2016
11:21 AM
Submitted by
pikaminskimage
on
08-30-2016
11:21 AM
test
... View more
See more ideas labeled with:
Feature request from navarr, posted on GitHub Jun 21, 2016
Feature Request:
Rather than override the success.phtml file, add the ability to create child blocks that can add buttons to the toolbar after checkout success.
Steps to reproduce
Install Magento 2.1 (in any shape)
Decide that you want to add an additional button in the toolbar on Checkout Success
Investigate the template to see if it is looking for additional blocks
Expected result
Become overjoyed with the ability to add blocks and insert additional buttons in this very handy space (through server-side rendering) for having them
Actual result
Become saddened with the lack of such an ability, and instead add a block to appear after the success block, rendering your button awkwardly underneath the other button - or alternatively change the entire success template
... View more
Status:
Investigating
Submitted on
08-30-2016
12:04 PM
Submitted by
apiuser
on
08-30-2016
12:04 PM
Feature request from FiveDigital, posted on GitHub Apr 16, 2014
Right now, there is not possibility to translate (or change) the routes generated for the frontend. The route to the basket is always /checkout/cart and it would be nice if we could configure or change the routes on a store view base. So that we can have /warenkorb in the German store view and /basket in the English one. Other frameworks like Symfony take the route in the templates and look up how to generate the URL for the frontend in the config (see http://symfony.com/doc/current/book/routing.html). Perhaps this could be a way for Magento too. The route name for the checkout could remain /checkout/cart but it resolves to whatever I have configured for in my store view and have a fallback to a default URL.
Are there any plans to change the routing / URL behavior in Magento 2? If not, perhaps you might think of taking it into your backlog.
... View more
Feature request from chasteIT, posted on GitHub Mar 26, 2015
Can we get a Magento2 demo of the frontend and admin (with sample data) that is updated?
This would enable many people who can’t install the platform to contribute feature requests and requests for improvements. There are many frontend developers and merchants who would have great suggestions for Magento2 development, and getting those requests sooner rather than later would help Magento2 developers prioritize items, combine similar projects, etc.
Also, I think the more technically capable among us would benefit from having a functioning install for comparison purposes.
Lastly, if this demo is updated regularly, it would be a great place to showcase Magento2 progress. That is, each update could list of changes like a simplified version of Magento's release notes.
... View more
Feature request from bhagvank, posted on GitHub May 05, 2015
hi all,
This is a missing feature for creating custom classes (objects) and custom Fields. There is an extension Custom Fields but on existing objects of classes.
Dynamically from the admin panel, ability to create custom objects and custom fields.
Bhagvan Kommadi
Vice President, SyberPlace
skype: bhagvan.kommadi
... View more
Feature request from vizjerai, posted on GitHub Apr 15, 2015
I noticed that there is an option to select a website for the group prices and it would be nice to be able to set a price for all groups. That way we can set a price differently on one site vs another one.
... View more
Feature request from bubach, posted on GitHub Apr 02, 2015
Need lots more features regarding languages and currencies between stores/shops. Right now you can be forced to duplicate whole translations and massive duplication for url-redirects based on language if you want to support the same language but inside different websites. Also using USD/EUR/GBP with the same english translation can be a pain if you set up the websites/shops in certain ways.
... View more
Feature request from alankent, posted on GitHub Jan 30, 2015
The complete suite of Magento developer documentation will consist of content from multiple sources. There are guides that the documentation writing team are developing (such as at http://devdocs.magento.com), more traditional online documentation generated from PHP Doc comments, and potentially other automatically generated documentation on REST/SOAP APIs and similar.
This issue is an invitation for the community to help with the PHP Doc aspect of documentation generation. There are several aspects to this work:
Try some different tools to see which are best able to support Magento. This relates to usability of output, speed and robustness of the tool, etc.
One proposal is to not generate documentation for all classes, but instead restrict the published documentation to only those classes and methods that the Magento team recommends being used. Such classes and methods could be annotated by “@api”. As such, it is desirable for the tool to be able to use @api as a flag of what to include in the generated output. This may involve modifying an existing tool as there may be no PHP Doc generation tools today that support this functionality.
Support for official Magento branding is also important. The core team can apply this branding (most likely following the same style and themes as the current documentation site). The objective is to take into account this requirement when selecting which tool to use.
Incorporation of documentation generation into the current documentation publishing on GitHub is desirable, but not mandatory.
An interesting future question is whether content developed by tech writers and PHP generated documentation can be merged. For example, having sample code linked to from the PHP Doc, or having links from guides to PHP Doc (without hard coding URLs to a specific web site). It is desirable to generate a single set of documentation that included both PHP Doc and guides.
In general, the goal is to get something up relatively quickly and deliver a useful short term result, restricted to PHP Doc. To set expectations, it may be this tool is temporary until replaced by a more encompassing solution for all documentation.
The goal is to lower the barrier to people exploring the Magento 2 code base today. Once the PHP Doc documentation is published, a desirable side effect is to then encourage greater contribution to improve the quality of the PHP Doc comments within the code base.
... View more
Feature request from rklerck, posted on GitHub Sep 09, 2015
We've added 85000 products with rest, this takes 14 hours. This seems fair because of a request for each product. But when we remove the products all at once in the backend, it takes 28 hours!!
... View more
Feature request from matinict, posted on GitHub Aug 26, 2015
magento 2 customer address Bangladesh State/Province/District not showing as like as United States.
I add Manually on database as :
For District:
INSERT INTO directory_country_region ( country_id , code , default_name ) VALUES
('BD', 'BD-BAG', 'Bagerhat'),
('BD', 'BD-BAN', 'Bandarban'),
('BD', 'BD-BAR', 'Barguna'),
('BD', 'BD-BRI', 'Barisal'),
('BD', 'BD-BHO', 'Bhola'),
('BD', 'BD-BOG', 'Bogra'),
('BD', 'BD-BRA', 'Brahmanbaria'),
('BD', 'BD-CHA', 'Chandpur'),
('BD', 'BD-CHI', 'Chittagong'),
('BD', 'BD-CHU', 'Chuadanga'),
('BD', 'BD-COM', 'Comilla'),
('BD', 'BD-COX', 'Coxs Bazar'),
('BD', 'BD-DHA', 'Dhaka'),
('BD', 'BD-DIN', 'Dinajpur'),
('BD', 'BD-FAR', 'Faridpur'),
('BD', 'BD-FEN', 'Feni'),
('BD', 'BD-GAI', 'Gaibandha'),
('BD', 'BD-GAZ', 'Gazipur'),
('BD', 'BD-GOP', 'Gopalganj'),
('BD', 'BD-HAB', 'Habiganj'),
('BD', 'BD-JAM', 'Jamalpur'),
('BD', 'BD-JES', 'Jessore'),
('BD', 'BD-JHA', 'Jhalokati'),
('BD', 'BD-JHE', 'Jhenaidah'),
('BD', 'BD-JOY', 'Joypurhat'),
('BD', 'BD-KHA', 'Khagrachhari'),
('BD', 'BD-KHU', 'Khulna'),
('BD', 'BD-KIS', 'Kishoreganj'),
('BD', 'BD-KUR', 'Kurigram'),
('BD', 'BD-KUS', 'Kushtia'),
('BD', 'BD-LAK', 'Lakshmipur'),
('BD', 'BD-LAL', 'Lalmonirhat '),
('BD', 'BD-MAD', 'Madaripur'),
('BD', 'BD-MAG', 'Magura'),
('BD', 'BD-MAN', 'Manikganj'),
('BD', 'BD-MEH', 'Meherpur'),
('BD', 'BD-MOU', 'Moulvibazar'),
('BD', 'BD-MUN', 'Munshiganj'),
('BD', 'BD-MYM', 'Mymensingh'),
('BD', 'BD-NAO', 'Naogaon'),
('BD', 'BD-NAR', 'Narail'),
('BD', 'BD-NRG', 'Narayanganj'),
('BD', 'BD-NRS', 'Narsingdi'),
('BD', 'BD-NAT', 'Natore'),
('BD', 'BD-NAW', 'Nawabganj'),
('BD', 'BD-NET', 'Netrakona'),
('BD', 'BD-NIL', 'Nilphamari '),
('BD', 'BD-NOA', 'Noakhali'),
('BD', 'BD-PAB', 'Pabna'),
('BD', 'BD-PAN', 'Panchagarh'),
('BD', 'BD-PAT', 'Patuakhali'),
('BD', 'BD-PIR', 'Pirojpur'),
('BD', 'BD-RAJ', 'Rajbari'),
('BD', 'BD-RJB', 'Rajshahi'),
('BD', 'BD-RAN', 'Rangamati'),
('BD', 'BD-RNP', 'Rangpur'),
('BD', 'BD-SAT', 'Satkhira'),
('BD', 'BD-SHA', 'Shariatpur'),
('BD', 'BD-SHE', 'Sherpur'),
('BD', 'BD-SIR', 'Sirajganj'),
('BD', 'BD-SUN', 'Sunamganj'),
('BD', 'BD-SYL', 'Sylhet'),
('BD', 'BD-TAN', 'Tangail'),
('BD', 'BD-THA', 'Thakurgaon');
INSERT INTO directory_country_region_name ( locale , region_id , name )
SELECT 'en_US', tmp.region_id, tmp.default_name FROM directory_country_region
AS tmp WHERE tmp.country_id='BD';
... View more
Feature request from airbone42, posted on GitHub Feb 16, 2015
Hi,
I just stumbled over the createObject function which has a massive switch to decide how an object should be created, depending on the amount of arguments.
switch (count($args)) {
case 1:
return new $type($args[0]);
case 2:
return new $type($args[0], $args[1]);
case 3:
return new $type($args[0], $args[1], $args[2]);
case 4:
return new $type($args[0], $args[1], $args[2], $args[3]);
case 5:
return new $type($args[0], $args[1], $args[2], $args[3], $args[4]);
case 6:
return new $type($args[0], $args[1], $args[2], $args[3], $args[4], $args[5]);
case 7:
return new $type($args[0], $args[1], $args[2], $args[3], $args[4], $args[5], $args[6]);
case 8:
return new $type($args[0], $args[1], $args[2], $args[3], $args[4], $args[5], $args[6], $args[7]);
case 9:
return new $type(
$args[0], $args[1], $args[2], $args[3], $args[4], $args[5], $args[6], $args[7], $args[8]
);
case 10:
return new $type(
$args[0], $args[1], $args[2], $args[3], $args[4], $args[5], $args[6], $args[7], $args[8], $args[9]
);
case 11:
return new $type(
$args[0],
$args[1],
$args[2],
$args[3],
$args[4],
$args[5],
$args[6],
$args[7],
$args[8],
$args[9],
$args[10]
);
case 12:
return new $type(
$args[0],
$args[1],
$args[2],
$args[3],
$args[4],
$args[5],
$args[6],
$args[7],
$args[8],
$args[9],
$args[10],
$args[11]
);
case 13:
return new $type(
$args[0],
$args[1],
$args[2],
$args[3],
$args[4],
$args[5],
$args[6],
$args[7],
$args[8],
$args[9],
$args[10],
$args[11],
$args[12]
);
case 14:
return new $type(
$args[0],
$args[1],
$args[2],
$args[3],
$args[4],
$args[5],
$args[6],
$args[7],
$args[8],
$args[9],
$args[10],
$args[11],
$args[12],
$args[13]
);
case 15:
return new $type(
$args[0],
$args[1],
$args[2],
$args[3],
$args[4],
$args[5],
$args[6],
$args[7],
$args[8],
$args[9],
$args[10],
$args[11],
$args[12],
$args[13],
$args[14]
);
default:
$reflection = new \ReflectionClass($type);
return $reflection->newInstanceArgs($args);
}
So PHP 5.6 added a new operator, also named the splat operator in other languages to unpack arguments, so whenever you decide to change the min. version to 5.6 this massive switch could be replaced by this simple line:
return new $type(...$args);
... View more
Feature request from markoshust, posted on GitHub Sep 10, 2015
If you go to Admin > Reports > Customers > New, and just click Refresh, it appears to show all dates from 1/1/01 to present.
It shows a row for each date, whether or not there is data for this date. Since I only have one customer record:
it is showing me 5477 unneeded rows. I believe this page would render a lot quicker and be easier to read if it just showed you the rows that have data. It may also be a good idea to default the "Refresh" button to a tighter time span, such as YTD.
... View more
Feature request from Flyingmana, posted on GitHub Sep 20, 2015
while we already have an Interface for Blocks ( BlockInterface ), there is still a place, which enforces usage of the abstract Block class ( \Magento\Framework\View\Element\AbstractBlock ).
https://github.com/magento/magento2/blob/develop/lib/internal/Magento/Framework/View/Layout/Generator/Block.php#L261-L265
While its not a problem to extend from there, I think it is not necessary for all Blocks
... View more
Feature request from wojtekn, posted on GitHub Sep 21, 2015
There is a class \Magento\Catalog\Setup\CategorySetup which takes care of setup for catalog_product and catalog_category entities.
This name is confusing and better name would be CatalogSetup .
... View more
Feature request from mage2pro, posted on GitHub Sep 21, 2015
The dropdown «Page Layout» on admin category page is untranslatable due to Magento 2 core bug:
My fix: https://mage2.pro/t/74
... View more
Feature request from mage2pro, posted on GitHub Sep 22, 2015
You can translate order statuses manually in «Stores» → «Order Status» admin section.
But it is inconvenient because:
you must do it manullay for each new Magento installation
it works for a single language but does not work for multistore Magento installation with multiple languages.
My fix for automatical translation: https://mage2.pro/t/76
... View more
Feature request from mage2pro, posted on GitHub Sep 19, 2015
See https://github.com/magento/magento2/blob/444e252d40b3a5d5cca3468a9819743af8ed3513/app/code/Magento/Backend/view/adminhtml/templates/widget/grid.phtml#L54-L56
https://github.com/magento/magento2/blob/444e252d40b3a5d5cca3468a9819743af8ed3513/app/code/Magento/Backend/view/adminhtml/templates/widget/grid/extended.phtml#L65-L67
Surely Magento 2 must distinguish the singular and plural cases.
... View more
Feature request from markoshust, posted on GitHub Dec 09, 2015
Current action:
I can click Submit Order without selecting a shipping method.
Desired action:
I should not be able to click Submit Order until a shipping method is selected.
Additional Notes:
If a shipping method is selected, I do receive an error after the form submission that a shipping method wasn't selected. However, this is undesired as it requires a full page refresh and resubmission.
v2.0.0
... View more