Hi
how do I keep the existing data been overwrite I select NONE at MAPS to Column ?
| Comment | File | Size | Author |
|---|---|---|---|
| #20 | Ubercart product after.png | 138.8 KB | Strompf |
| #20 | Ubercart product before.png | 148.13 KB | Strompf |
| #16 | save-fields-on-update-874422-15.patch | 10.49 KB | bcn |
Comments
Comment #1
enzipher commentedHi,
If you don't map the field, e.g. select "none", then the existing data should be kept intact.
Cheers
Comment #2
johnking commentedHi,
I did select "none" and it deleted all my existing data, like Taxonomy, pictures... . how do I let the module treat blank row means no change, skip and continue
thanks
Comment #3
pjclaro commentedHi,
The same thing happened to me and lost all my images.
How can I just let blank rows or missing rows ignore the field and keep its value?
Thanks.
Comment #4
ikeigenwijs commentedsubscribe
Comment #5
imrubio22 commentedsubscribe
Comment #6
coolestdude1 commentedbump :)
Comment #7
coolestdude1 commentedcck fields are a little strange as to how they deal with the iterations of the rows I will keep this post open as even I am still not aware of a way to keep the data. Seems to me like an if statement needs to be added as null is actually being treated as the data even tho you told it to skip. On possible current work around is to not map that column but then your future imports wont have that data at all so I think this needs to be talked out a little more with merlin ill try and find him on irc.
Comment #8
designate commentedsubscribe
Comment #9
fantom84 commentedsubscibe
Comment #10
joshua.howell commentedsubscibe
Comment #11
topdillon commentedsubscribe
Comment #12
elliotcapelo commentedsubscribe
Comment #13
Stan.Ezersky commentedI have the same error.
subscribe
Comment #14
vonn.new commentedIs there any movement on this issue? When I update a node, I lose all the data from my existing cck fields. I've been digging in the code, but I haven't found a solution.
Comment #15
bcn commentedSee the following comment
Comment #16
bcn commentedAttached patch attempts to allow for field values to be retained on updates. Testing is needed, and various field types might not work.
Comment #17
Enemy commentedGood job!
It works!
Comment #18
coolestdude1 commentedImplemented patch from #16 in dev release. Please go and check it out. From my testing it is working, but my testing is pretty simple compared to the hundreds of ways that this module can be used soooo I need all parties to test this bad boy out. Let me know if we can release and everyone is happy.
I will leave it as needs review for now because that is correct for this stage of development. If anyone finds issues push back to 'Needs work'.
Bcn, the only thing I improved upon was the text formatting for code readability which looks like you did some as well. Thanks bud :)
Comment #19
pvanerk commentedHi,
I downloaded the 6.x-1.x-dev version (from: https://drupal.org/node/797150/releas) but the patch was not applied to this version. Which dev release did you mean in your post?
Comment #20
Strompf commentedUsed this patch for updating Übercart products. Finally, prices don't get reset to zero.
However, taxonomical information is still lost, which is exactly why I want to update products, rather than import them all over again. Anyone any ideas how I can fix this?