Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in Admin on Simple Product Pages for Second (Not Default/Main) Store #61

Open
myork24 opened this issue Apr 2, 2024 · 1 comment

Comments

@myork24
Copy link

myork24 commented Apr 2, 2024

Preconditions (*)

  1. Version 1.2.5
  2. Magento 2.4.4-p2 EE. Multiple stores in instance. The main/default store is connected to a Meta account and does not have the issue, only the second store in Magento does.

Steps to reproduce (*)

  1. In our environment, the issue can be created when going to Catalog->Products and opening the product page in the specific store view scope of the second store for simple products. The error that displays is "Client error: GET https://graph.facebook.com/v18.0/415545034329727/products?access_token=EAACxonUmtyIBO3LEFpkUhNl9lVJi9iPn0GZBxGKDP3GNIKUDZAoIWbNRVpRXvdcdCPapE5aegToaQsDJG403rDSplxR04CvVTwHLrnL2AGh019xNNSjqadkSIe4TcbDm1mkvc3UupBK3ZCCnmBNs4Oqa20rAHEsG7zWMka115MXAI9JDuy9rwkgpSnPPc6t&filter=%7B%22retailer_id%22%3A%7B%22eq%22%3A%221893%22%7D%7D&locale=en_US resulted in a 400 Bad Request response: {"error":{"message":"Unsupported get request. Object with ID '415545034329727' does not exist, cannot be loaded due to m (truncated...)" The error does not occur when viewing teh All Store Views scope for the simple products of the second store. We need to be able to access the config of the specific store view in order to make updates to the products at that level.

Expected result (*)

  1. [Screenshots, logs or description]
  2. We expect that the product config settings are displayed and available at the specific store view scope for the second store, just like they are for the All Store Views scope.

Actual result (*)

  1. [Screenshots, logs or description]
  2. See "Steps to Reproduce"

I have reached out to Meta support and after a month+ of back and forth, they did not provide any useful information for a solution. The catalog showing in the error does exist in Meta.

@sol-loup
Copy link
Contributor

sol-loup commented May 9, 2024

Hey @myork24 -- can you try an update? We resolved this in version 1.3.1, which is currenty out and available on composer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants