Showing ideas with label API.
Show all ideas
I am suggesting the Magento team creates their own solution that is an alternative to MySQL & ElasticSearch. Elasticsearch is complicated to setup, and customers must pay for "Gold" or "Platinum" service levels to enable security for it.... If the Magento team creates their own implementation then it can be setup with ease like most other core modules... The search data can be loaded into memory and refreshed with cron jobs. ElasticSearch is very frustrating. Why is MySQL searching being deprecated?
... View more
We have a real big Problem with the REST API because the API doesn't provide GET for Payment- and Shipping-Methods, defined in the Parameters of the Shop. After Hours and Hours of searching we've found Infos about getting this Informations by using Carts, but that's not the Way we need to do it. As Info of Background, we are developing an additional Software for an ERP-Product to syncronize Data between an ERP and for Example a Webshop. Before the Sync happens, we call on both sides to get the needed Infos for mapping them. Without Payments and Shippings we can't get this done completly and the Customer will get wrong created Items in the ERP. That's a real big Problem for us. We've created an addtional Module for Meganto 2 which delivers the missing Infos we need, but this is not the best Way because some Servers/Webspaces doesn't support Commands executed by PHP, so we can't install the Module automatically. What we need in Short Description: GET -> Shipping-Methods (all, defined and viewable in Magento 2 Backend) GET -> Payment-Methods (all, defined and viewable in Magento 2 Backend) Please, if possible, implement this to the REST Api. It will help us a lot. Thx
... View more
Status:
New
Submitted on
06-05-2019
05:16 AM
Submitted by
antonioeternalparquet_antonioeternalparquet
on
06-05-2019
05:16 AM
Hello, I am running a server with plesk installed with the latest version 17.8.11 . The magento package for plesk is version 2.1.0, I would like to install the latest version 2.3.1 but the plesk support said that this version is not supported. When the aps package will be upgraded with the latest magento version? Thanks for your answer.
... View more
For PWA we should maintain separate Repository. It should contain apis,models,resource models etc. it should not contain front end controllers,layouts,blocks ,routes etc. in this way our focus only about apis. if any one wants to implement PWA they will download/clone this Repository.
... View more
See more ideas labeled with:
-
API
Hi, For all developers In magento when setting a new store up, there is too many configuration that we do according to each developer requirement. For example, i always enable imagick compressen, set flat category to yes, set asynchronous to sales, set product to decrease from stock in pending state, set to show how many items left when reaches 5, set admin lifetime session ......etc There is too many configuration that you cant count we always tune our magento system accordingly. So why every time i need to setup a fresh copy i need to reconfigure the system again and again this takes time and time is money :). My Feature request is that to make an option where we can export magento configuration categories from Sales, General, Catalog, system .... and all there sub categories, and export them to a single file. While in import, i select the file i exported earlier and import the whole configuration or selective configuration, for example i only want to import the Sales category configuration. But you must take into consideration that a configuration file must be compatible with all versions of magento old and future. This is basicly my idea, Also if this idea can be applied to export third party extensions configuration. Because Advanced extensions requires many configuration especially seo tool kits. Using the import with a single click i can configure the whole extension. Also the extension developers can create a configuration settings files to give for extension buyers to configure there extension easily.
... View more
See more ideas labeled with:
I found that the product attribute option is missing something, we are not able to edit the label of them because we don't have any api to update them, we can only add new one to the list or remove one. That is not a good thing since if we are using the options on certain product we cannot just delete it and create a new one, go on each product and change it. It would be nice that we can change the label of some option even if it's one at a time. Thank you.
... View more
See more ideas labeled with:
-
API
Issue Currently there is no simple way to check what quote item was just added to the cart. This causes issues for module developers who need to work out what item was added to the cart for a custom module. Possible Solution Right now we have: $this->checkoutSession->getLastAddedProductId(); To get the last added product however there is no way to fetch the item id. A possible solution is to give us a saved session for getLastAddedItemId for example: $this->checkoutSession->getLastAddedItemId();
... View more
See more ideas labeled with:
-
API
-
checkout
-
extensions
Firebase Push Notification module: This module is very frequently used with mobile applications. We can provide features listed below: Admin area to configure firebase authentication key. Rest API to save device token when someone gets logged-in with mobile application. Send push notification to mobile devices on various events like new order, order status change, abandoned cart etc. Send bulk notifications for newsletters and marketing campaigns. Save the list of notifications sent to customers and allow resend the notifications. I have already prepared a sample module and planing to publish it on Magento Marketplace.
... View more
See more ideas labeled with:
Using the Order API in either SOAP or REST mode with XML returns the payment's `additional_information` in an unidentified list, an array of strings without keys: <additionalInformation>
<item>0</item>
<item/>
<item/>
<item>Credit Card</item>
<item>1</item>
... These values are fairly useless and should be identified with something like this: <additionalInformation>
<save>0</save>
<acceptjs_key/>
<acceptjs_value/>
<method_title>Credit Card</method_title>
<response_code>1</response_code>
... The keys are being stripped by the Magento\Framework\Reflection\DataObjectProcessor, though I don't think that is the real cause as I was not able to change the way this data is sent.
... View more
See more ideas labeled with:
-
API
-
payments
Hi, Currently it is only possible to choose either GTM Or Universal Analytics in Magento backend and it will only render one or another on store fronts. One of our customers wanted both of these together on frontend and we commented the condition check at ga.phtml file to accomplish this. If possible and is conceptually correct, please make this feature avaialble in future magento versions. Thanks and regards, Manaf
... View more
See more ideas labeled with:
-
API
-
extensions
There is no REST API exposed for adding a Catalog Price Rule. I verified this with the EE support team. There are APIs available for adding special pricing and Cart Price rules, so why not for the Catalog one? Thanks
... View more
See more ideas labeled with:
-
API
We use the salesShipOrder method to post shipping information to Magento2 from our fulfillment software. We're able to successfully create the shipment (along with carrier information, tracking numbers, customer notification), however there is not a way to indicate a shipment date (createdAt) for the package. When the post is made, it uses the current date/time as the shipment date, not the actual date/time that the package was shipped. We began using the salesShipOrder method over the salesShipmentRepository method to combat the Magento2 bug where order status is not properly updated. However this new method does not include the essential element for shipment date.
... View more
When working with products regarding store context, there is inconsistency among Quote, Order and Invoice and Shipment items regarding the getProduct() method. The best implementation as of 2.1.7 is Magento\Quote\Model\Quote\Item\AbstractItem.php, where it supplies store id in the context of the quotation. I suggest that the model of Order and Invoice should follow such practise when getting product from underlying items, since developer expects a certain level of API consistency. I can make PRs if everyone agrees.
... View more
I know there are endpoints for both fetching an address by id and deleting one by id. Listed below: (customerAddressRepositoryV1) as listed here http://devdocs.magento.com/swagger/index_20.html#/ 1) To get a address Endpoint: /V1/customers/addresses/{addressId} Method: GET 2) To delete a address Endpoint: /V1/addresses/{addressId} Method: DELETE The issue with either of them is that they are not accessible by customer token. They seem to only work with Admin Token Authentication. If a customer adds multiple addresses and selects a specific one to fetch entire details or delete it, it should be allowed from his customer access. Please suggest.
... View more
See more ideas labeled with:
-
API
The suggestion is to establish a pattern of adding the following code to deprecated functions: // This is just an example. Write whatever -- something to point people in the right direction.
$sMessage = 'save() has been deprecated in favour of using the usage of repositorties, and the deferral of persistence to the persistence layer. See https://h.dev.magento.com/repositories for further details'
@trigger_error($sMessage, E_USER_DEPRECATED); This can be introduced harmlessly to the stack, and does not actually change any error behaviour, or make the deprecated methods more fragile. However the error handler indicated by set_error_handler() will be called; allowing the surfacing of the deprecated methods. This is useful in a couple of ways: Tests can stub the error handler such that it propagates these error messages and fails tests. This clearly indicates that the code is no longer valid. The error handling function can be modified such that in developer mode these errors are surfaced to the user, and either halt execution or are simply logged to the debug log State of "known violations" can be tracked (perhaps simply with a try_catch in tests, with a skip or the like). This means that any new code must either violate the deprecation intentionally (picked up in review) or fail tests (picked up in CI) This pattern has been previously established by Symfony[2][3] and appears to work as expected there. Such work will allow enforcement of deprecation; something that has proved problematic in the past (particularly in code review where it's not apparent that used functions are deprecated) [1] http://uk.php.net/manual/en/language.operators.errorcontrol.php [2] https://twitter.com/andrewhowdencom/status/900675010641133571 [3] https://github.com/symfony/class-loader/blob/b94aa5c3608cd53444fc4c7a2a506d163eb4a8f3/MapClassLoader.php#L14
... View more
See more ideas labeled with:
-
API
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
See more ideas labeled with:
-
API
Magento 2 REST API get website_ids for product Please provide additional GET REST API method on catalogProductWebsiteLinkRepositoryV1 to allow us to retrieve the website_ids for an sku. Or instead include the website_ids for an sku in catalogProductRepositoryV1 get /V1/products/{sku}
... View more
See more ideas labeled with:
-
API
-
developer
Hi, I've see as of April 7, 2017 that Magento is rolling out a B2B Cloud for the Enterprise edition. I wonder if this is being considered, or some iteration, for the Community edition? I think this would be a great addition.
... View more
See more ideas labeled with:
-
API
-
CMS
-
extensions
-
platform
Currently the rest API doesn't send a websiteId attribute when you request a product.This would be really usefull for developers.
... View more
Mag V2 is missing the magentoInfo method that is available in Mag V1 APIs. Please add this to Mag V2 REST and SOAP APIs. It is necessary for feature validation when writing third party integrations.
... View more
See more ideas labeled with:
-
API
-
developer