Cannot Delete Specific Nodes #23


  • Defect
  • Invalid
Closed
Assigned to moonfann
  • tvstatic82 created this issue Jan 8, 2011

    What steps will reproduce the problem?

    With a database imported using GatherMate2_data, go to the GatherMate2 -> Maintenence configuration window. Click on Delete Specific Nodes. Select Herb Bushes, (475) Heartblossom, Deepholm and click delete.

    What is the expected output? What do you see instead?

    Expect Heartblossom nodes to be removed from Deepholm. Nothing is removed.

    What version of the product are you using?

    1.11

    Do you have an error log of what happened?

    N/A

    Please provide any additional information below.

    Debugging indicates a problem with the call to GatherMate:DeleteNodeFromZone, which passes selectedDatabase, GatherMate.nodeIDs[selectedDatabase][selectedNode], selectedZone. The selectedNode is an index number from the dropdown list (in this case 3). The field "GatherMate.nodeIDs[selectedDatabase][selectedNode]" evaluates to nil as the table "GatherMate.nodeIDs[selectedDatabase]" uses the original herb names as keys and numerical indices are not valid.

    I have also tried hard-coding this value to 459 but the nodes still will not be removed. In GatherMate:DeleteNodeFromZone, the line "local db = gmdbs[nodeType][zone]" evaluates to nil, indicating a further issue.

  • tvstatic82 added the tags New Defect Jan 8, 2011
  • tvstatic82 edited description Jan 8, 2011
  • moonfann posted a comment Jan 9, 2011

    you sure you have version 1.11 properly installed?

    as it should say: local nodeName = sortedFilter[selectedDatabase][selectedNode] nodeName = denormalizedNames[nodeName] GatherMate:DeleteNodeFromZone(selectedDatabase, GatherMate.nodeIDs[selectedDatabase][nodeName], delocalizedZones[selectedZone])

    Where we take the dropdown value and change it back to the proper name to be passed in.

  • Xinhuan removed a tag New Dec 17, 2011
  • Xinhuan added a tag Invalid Dec 17, 2011
  • Xinhuan closed issue Dec 17, 2011
  • Xinhuan posted a comment Dec 17, 2011

    Closing since the problem cannot be recreated and it has been 11 months.


To post a comment, please login or register a new account.