Fix (again) activity creation when a business template replaces an existing persistent object.
With previous solution, regular reindexation activities were not given any "after_method_id", so they triggered the infamous "uid already used by path ..." log message. Instead, use new placeless activity parameter mechanism to make all activity get the new tag. This removes the need for any extra reindexation. Kudos to Sebastien for the idea. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@23472 20353a03-c40f-0410-a6d1-a30d3c3de9de
Showing
Please register or sign in to comment