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

Tier prices being deleted after products being sent. #57

Closed
Santiagoebizmarts opened this issue Sep 7, 2016 · 10 comments
Closed

Tier prices being deleted after products being sent. #57

Santiagoebizmarts opened this issue Sep 7, 2016 · 10 comments
Assignees
Milestone

Comments

@Santiagoebizmarts
Copy link
Contributor

No description provided.

@jorgb90
Copy link

jorgb90 commented Sep 14, 2016

Just downloaded Master 1.1.1 and this fix isn't included.. Added it myself to products.php but again lost tier prices because of that :(

@delarosajv
Copy link

What a mess...

i've lost it too :(

@jorgb90 have found another issue? i'm still having problems with the sync and maybe the last update miss another fix..

@Santiagoebizmarts
Copy link
Contributor Author

Hello @jorgb90 and @delarosajv,

Are you sure you have the latest version 1.1.1? This works okay for me. The fix is at this line.

When loading the product all the attributes such as tier prices and dropdowns are loaded and then saved properly later in the code.
In case you do have the latest version 1.1.1 please tell me what version of Magento do you have installed for me to test it.

@jorgb90
Copy link

jorgb90 commented Sep 20, 2016

@Santiagoebizmarts Ah ok so you have made another fix for the issue. We are using Magento 1.9.2.4 by adding this fix manually again in Products.php it worked..

@Santiagoebizmarts
Copy link
Contributor Author

@jorgb90 ,

The other fix is included in version 1.1.1 and works okay for me.
What version of Magento are you using?
Do you have any customizations on your products?

@jorgb90
Copy link

jorgb90 commented Nov 10, 2016

@Santiagoebizmarts

This is still not solved! When reset somehow fails every attribute is set back to is default value and tier prices will be removed. It only works when the reset does its job correctly..

Magento 1.9.3.0 and no we do not have any customizations.

@CMeldgaard
Copy link

I also have this issue. Doesn't the version miss the $product->getTierPrice(); in model>api>products.php

This was the fix i got for an earlier version.

@Santiagoebizmarts
Copy link
Contributor Author

Santiagoebizmarts commented Nov 16, 2016

When loading each product here, it should also load the tier prices.
I guess we can add this if it keeps happening on some installations.

@GeekMediaDK, @jorgb90: Please give the steps to reproduce this with the latest version 1.1.2.

@CMeldgaard
Copy link

CMeldgaard commented Nov 23, 2016

@Santiagoebizmarts
I've just deleted all my local errors, which keep stacking up:

  • We were unable to process the request. An order with the provided ID already exists in the account.
  • We were unable to process the request. A product with the provided ID already exists in the account.
  • A product with the provided ID does not exist in the account for this list.
  • customer : Required fields were not provided: id / customer.id : Schema describes string, NULL found instead
  • CGROUP : Value must be one of: General, Wholesale, Retailer, tilbud, NOT LOGGED IN (not Dansk forbruger)

And not it just dropped 200 tier prices!!! So there is not pattern to it, because is synced 844 products without any problems, and then i just deleted the local errors which then deleted 200 tier prices. Could this happen, if someone reindexes during syncronisation?

And i've just inserted $product->getTierPrice(); in the products.php before all product->save()

On a sidenote, those errors are they returned from mailchimp, or are they a part of the application, especially the CGROUP error is a big problem if one need to destinct between different customer groups based on language.

@Santiagoebizmarts
Copy link
Contributor Author

Hello,
I've added the getTierPrice function to avoid this particular scenarios.
You can see the solution in the commit referenced above.

Thanks for your feedback.

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

No branches or pull requests

6 participants