Magento 2.x Feature Requests and Improvements

Feature request from mynameismud, posted on GitHub Jun 20, 2017 Preconditions v2.1.3 You need a standard Paypal account You need a Payflow Pro account also NOTE: It appears that ANY two Paypal types of accounts would suffice for this test. This is a general issue with validation in Ipn.php, not an issue specific to these two methods. Steps to reproduce Enable Paypal Express Checkout and process a payment using it Disable Paypal Express Checkout Enable Payflow Pro and process a payment using it Create a credit memo for the Paypal Express Checkout payment via Magento Admin or log into paypal.com and process a refund directly there Expected result Paypal should send the IPN and it should pass validation then trigger appropriate business logic. Actual result In Ipn.php, line 110, the validation logic checks to see if the payment method is both active AND available. It seems that this should ONLY check isMethodAvailable. In cases where the merchant swaps out payment methods (in our case we changed from Paypal to Payflow Pro), the merchant still needs to be able to process reference transactions against older payments originated with the now-inactive method. It might be preferable to make the validation more specific and only perform this check against AUTH and SALE transactions. Then refunds, etc would be excluded from the check. Example from exceptions.log: [2017-06-15 23:26:36] main.CRITICAL: Exception: Method "paypal_express" is not available. in /var/www/.../vendor/magento/module-paypal/Model/Ipn.php:124 ... View more

Feature request from ldusan84, posted on GitHub Jul 12, 2017 When creating a custom grid using UI components, the "Store" column can be created like this: <column name="store_id" class="Magento\Store\Ui\Component\Listing\Column\Store"> <argument name="data" xsi:type="array"> <item name="config" xsi:type="array"> <item name="bodyTmpl" xsi:type="string">ui/grid/cells/html</item> <item name="sortable" xsi:type="boolean">false</item> <item name="label" xsi:type="string" translate="true">Store View</item> </item> </argument> </column> Where the class attribute value is the column renderer. The Magento\Store\Ui\Component\Listing\Column\Store column renderer works correctly for the cases where the entity can belong to multiple store views such cms block, cms page, etc. If you want your entity to belong to only one store view you need to use Magento\Search\Ui\Component\Listing\Column\StoreView as Magento\Store\Ui\Component\Listing\Column\Store doesn't work correctly in that case (shows blank for all store views). I think that Magento\Search\Ui\Component\Listing\Column\StoreView belongs to the Store module instead of Search module. There shouldn't be a need to have an additional dependency to Search module just to get the store view column renderer. The naming can also be improved, maybe Magento\Store\Ui\Component\Listing\Column\MultipleStoreView and Magento\Store\Ui\Component\Listing\Column\SingleStoreView Hope it makes sense. ... View more

Feature request from gputignano, posted on GitHub Aug 14, 2017 Tested on a blank installation of Magento 2.2 RC1.8. When I create a new configurable product SKU field is mandatory but I think it is mandatory only for simple products. ... View more

Magento 2 stores files on disk in the /media dir, but this makes multi-server setups more complex as this dir needs to be shared by all machines. At the same time, cloud storage is very flexible and scalable (no more running out of disk space for example). By implementing Gaufrette, a well-known file system abstraction layer from the Symfony world, we can put our media files anywhere we like, including S3, Google Cloud, FTP and countless more places. And should a developer ever need more than this, a custom file system can be developed easily too. ... View more

We always run into errors when including "additional_attributes" column because one of our custom attributes uses commas/description-type box. Changing the delimiter is not a good solution as it also means updating it on your machine. Our CSV's are usually transferred to multiple people and should always be ready to go with comma delimiters. We would like Magento 2 to use Magento 1's system of separating each attribute into it's own column. The importer isn't very useful for bulk product uploading if our most important attributes need to be omitted and we've resorted to a Firebear Importer module. Could this be something a future version of M2 fixes? This would avoid a lot of headache and make a much more readable CSV product export. ... View more

One of the biggest complaints we get from customers is the generic error message "An error occurred on the server. Please try again", that displays in the checkout when their credit card cannot be accepted. Usually there's an issue where the billing and shipping address or zip code doesn't match, so the card is not accepted.   The problem is the error message states there is "an error on the server" which leads them to believe there is something wrong with the website-when that is not the case, there is something wrong with what they've inputted. Another type of generic message like "We could not place this order, please call (store's phone number) to complete" would work infinitely better. Even better, would be a way to customize your own error message in the checkout right in the admin panel.    Overall I think this simple change would help the customer understand that the order could not be processed, but there isn't a problem with the website or server. ... View more

Google Adwords add ability to provide transaction-specific conversion values in your conversion tracking tag . See https://github.com/magento/magento2/issues/6708 ... View more

It would be very helpful if customers had the ability to write order comments when they go through the checkout process on the front end. ... View more

Our website like many, many others charges customer credit cards when they order therefore automatically creating an Invoice.  Our customers can change their order before shipment so we need ability to edit the Invoice in exactly the same way as editing an Order.   To take this one step farther, it would also be nice if the original Total Price could be tracked so that when the Invoice is edited, the delta charge/refund amount is shown and can be charged or refunded to the credit card. ... View more

See https://github.com/magento/magento2/issues/6709  Thanks ... View more

Bumped into this one yesterday. At our company we like to use semantic correct names for our attribute codes. With middle- to larger sized shops these names tend te be somewhat longer. Attribute codes in Magento 2 are not allowed to be longer than 30 characters.   Can anyone explain to me what's the reason behind this? Is there a technical one? Or is it just that someone thought at some time "30 characters ought to be enough for anyone"?   I'd really like to know. ... View more

I think we can divide Repository interfaces into multiple interfaces.so Extension providers don't need to provide implementation for all methods in interfaces. interface CustomerRepositorySaveInterface { /** * Create or update a customer. * * @param \Magento\Customer\Api\Data\CustomerInterface $customer * @param string $passwordHash * @return \Magento\Customer\Api\Data\CustomerInterface * @throws \Magento\Framework\Exception\InputException If bad input is provided * @throws \Magento\Framework\Exception\State\InputMismatchException If the provided email is already used * @throws \Magento\Framework\Exception\LocalizedException */ public function save(\Magento\Customer\Api\Data\CustomerInterface $customer, $passwordHash = null); } interface CustomerRepositoryGetInterface { /** * Retrieve customer. * * @param string $email * @param int|null $websiteId * @return \Magento\Customer\Api\Data\CustomerInterface * @throws \Magento\Framework\Exception\NoSuchEntityException If customer with the specified email does not exist. * @throws \Magento\Framework\Exception\LocalizedException */ public function get($email, $websiteId = null); /** * Get customer by customer ID. * * @param int $customerId * @return \Magento\Customer\Api\Data\CustomerInterface * @throws \Magento\Framework\Exception\NoSuchEntityException If customer with the specified ID does not exist. * @throws \Magento\Framework\Exception\LocalizedException */ public function getById($customerId); /** * Retrieve customers which match a specified criteria. * * This call returns an array of objects, but detailed information about each object’s attributes might not be * included. See http://devdocs.magento.com/codelinks/attributes.html#CustomerRepositoryInterface to determine * which call to use to get detailed information about all attributes for an object. * * @param \Magento\Framework\Api\SearchCriteriaInterface $searchCriteria * @return \Magento\Customer\Api\Data\CustomerSearchResultsInterface * @throws \Magento\Framework\Exception\LocalizedException */ public function getList(\Magento\Framework\Api\SearchCriteriaInterface $searchCriteria); } interface CustomerRepositoryDeleteInterface { /** * Delete customer. * * @param \Magento\Customer\Api\Data\CustomerInterface $customer * @return bool true on success * @throws \Magento\Framework\Exception\LocalizedException */ public function delete(\Magento\Customer\Api\Data\CustomerInterface $customer); /** * Delete customer by ID. * * @param int $customerId * @return bool true on success * @throws \Magento\Framework\Exception\NoSuchEntityException * @throws \Magento\Framework\Exception\LocalizedException */ public function deleteById($customerId); } class CustomerRepository implements \Magento\Customer\Api\CustomerRepositorySaveInterface,\Magento\Customer\Api\CustomerRepositoryGetInterface,\Magento\Customer\Api\CustomerRepositoryDeleteInterface { }   ... View more

(From https://github.com/magento/magento2/issues/7852)   Steps: Run "bin/mage module:disable Magento_Review" in a standard Magento installation Actual Result: The module can't be disabled because Magento_Customer depends on it. Expected Result: The module Magento_Review is disabled. Is it really necessary that the Customer module depends on the Review module? It's the only reason why I can't disable the Review module and a quick search for "Magento\Review" in the Customer module's codebase reveals that only a single file references a class in Review: \Magento\Customer\Block\Adminhtml\Edit\Tab\Reviews. I'm sure this can be refactored to remove the dependency, right? ... View more

https://framework.zend.com/blog/2016-06-28-zf1-eol.html   So Magento will migrate lib components to other   zf2 or doctrine etc? for example still magento using Zend_Db from zf1. ... View more

In Magento the country of Netherlands Antilles is available, when this doesn't exist anymore https://en.wikipedia.org/wiki/Netherlands_Antilles. It should be split up into Aruba (which is already there), Curacao (which is not there), Sint Maarten - note this is different to Saint Martin (which is not there). There are also 3 Municipalities (Bonaire, Sint Eustasius and Saba) which form the Caribbean Netherlands - ISO code BQ. This would also need to be added. ... View more

UPG / Secure Hosting payments gateway integration ... View more

Magento 2 allows developers test their code (unit, integration ... ). I have noticed that It is not common among developers to wirte tests (small amount questions in froums).   I think that separating programming question from test related questions would bringing testing more out and might increase its popularity.  ... View more

I need to make a discount by producto when users buy Only 10 . But the discount is also aplyed when user buys 11. How can i solve this?   ... View more

Let me give some reasons as to why you'd want to release more often than you do today: a) bugfixes take a very long time to reach mainstream, frustrating users; this is one of the many commits I've yet to see in official releases: link; currently, this is the main reason M2 gets on the bad side of people; b) because of the above, there's a continuous pressure from us - the users -, to actually ship the bugfixes; that can't be good for your health, M2 core devs; c) new features take a long time to release, making the userbase move to friggin' WP-Commerce, because boredom; d) such long release cycles means that a big amount of code is added to the mainline at once, which makes for a very unstable/dangerous upgrade process every. blasted. time; I've yet to see the developer who can't wait to upgrade the M2 codebase of an ongoing project; e) everybody's doing it, and it works for them (from the Linux kernel, to the main browsers); I'm sure it can work for M2, as well.   You've been improving, merging more community PRs. Great. But can you please release them, too?   PS: Ending on a fun note, this is the worst forum app I've seen lately. ;) ... View more