Le 08/08/2011 09:53, Damien Touraine a écrit :
* enhance.commonTreeDropDown.for.father.migration.patch : I don't know if it is a misunderstanding of mine, but it seems that when a node of a CommonTreeDropDown is moved inside the tree, all its children are not updated correctly. Among others, their completename fields are not updated. Their sons_cache are cleared wherever this part of the tree has not been updated. Actually, the previous version clean cache fields of all nodes, that is not optimale, I think. This overzealousness induce parents to clean sons_cache, but also ancestors_cache. So, I redefine the post_updateitem to update correctly the sons and the parents (parents before the update and after the update). Moreover, this part of the CommonTreeDropdown becomas standalone (no need to call external "out of class" function "regenerateTreeCompleteNameUnderID").
patch applied in the second version you send : https://forge.indepnet.net/projects/glpi/repository/revisions/15336 I fixed a bug on move item. On update $input['name'] is not set so completename was not compute correctly. I also fixed addslashes usage for getCompleteNameFromParents. Now GLPI manage addslashed names on $input (POST from interface) and not slashed one from DB. So we have to take into account that.
Thanks Julien _______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
