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
Mass edit - Updated At #4620
Comments
So, this might have to do with the fact that the |
After looking into it, the dates do get created in |
It seems that the MondoDB's |
Hi Matias, What do mean by "When adding values to product attributes"? Did you try to change a common product value? I tried to reproduce it on a fresh install but the |
Yes, change which ever attribute so that the product is marked for changes, thus to be persisted.
Irrelevant When doing mass edits (what ever methods that will call the As a workaround we're listening to the |
Up. The normalizer updates the "root" field updated on the fly but does not update it to the product object. So, as @mathewrapid said :
Product updated field and normalizedData.updated are always out of sync. NormalizedData is one step late. I think that the normalizer never has to do The fact is that the product has to be updated (so updated field) before normalization. |
+1 |
Hi @mathewrapid, @jlestel, @BMarrot ! FYI, this issue (PIM-6038) has been fixed in following versions,
Best regards, |
Imo. can be closed. Opinions? |
As @nidup pointed out in #4620 (comment), this has been fixed in PIM-6038. |
akeneo-pim-system-info_2016-06-16_14-41.txt
Probably the same as in #2644 (which is closed without an explanation)
When adding values to product attrbiutes via the mass-edit the versioning gets updated with the correct timestamp, but the products updated timestamp is not.
This can be verified by mass editing one product and running the
php app/console --env=prod pim:product:query '[{"field":"updated","operator":">= WITH TIME","value":"YYYY-MM-DD HH:mm:ss"}]'
This has a major impact to some export profiles that uses the EnhancedConnectors
fromLastExecution
option.Note. MongoDB is in use -> Mass edit will use
\Pim\Bundle\CatalogBundle\Doctrine\MongoDBODM\Saver\ProductSaver::saveAll
The text was updated successfully, but these errors were encountered: