Closed (fixed)
Project:
Amazon associate tools
Version:
4.7.x-1.x-dev
Component:
User interface
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
15 May 2006 at 11:25 UTC
Updated:
9 Jun 2006 at 17:54 UTC
I seem unable to edit amazon_node nodes, it keeps yelling about the item already existing since it doesn't seem able to discriminate between adding a new item and editing an old. I propose a check is made whether the amazon item exists and if it does, it is overwritten.
Comments
Comment #1
Prometheus6 commentedAre you working with version 4.7? The only thing you can edit is the book's rating. That's intentional, because amazon_node nodes should have nothing but data from Amazon.com.
Before I mark this 'by design," though, is there a reason I shouldn't?
Comment #2
solipsist commentedUsing 4.7 yes. I tried to change the taxonomy term, that should be possible, shouldn't it?
Comment #3
Prometheus6 commentedYes, and is so on my systems, both php4 and php5. I'm not running release candidates, though.
If you have a url where I can see this problem, email me.
Comment #4
solipsist commentedI do, but thing was it happens when you click preview. I hadn't set previewing to optional so I was forced to preview, and trying to preview it caused the term selection to reset. Can you get that behavior to repeat?
Comment #5
Prometheus6 commentedNo, I can't.
You know what? I want you to email me a copy of the 4.6 and 4.7 versions of the module you're running. Right now, the ASIN field in the 4.6 version is manditory (check the form_textfield() call in amazon_form() );
in 4.7 it always was.
And I'm just not having the problems you are. I need to see exactly what you're working with.
Comment #6
Prometheus6 commentedOkay, I duplicated the problem...kind of by accident, but I can do it at will. I think it qualifies as critical.
Comment #7
solipsist commentedOk, good to hear that! Thanks for taking your time looking into it.
Comment #8
Prometheus6 commentedOkay, try a fresh download. I'll wait for your response before setting this as fixed, of course.
Comment #9
Prometheus6 commentedComment #10
solipsist commentedI haven´t had time to look at this yet but I will.
Comment #11
Prometheus6 commented