Moving or copying a page with task included leads to errors / misbehaviour

[lamblinc]

Steps to reproduce :

• Create a page Sandbox/Test1, insert a task in it. It will have the reference Sandbox/Test1/Tasks/Task_0 and id 1
• Copy or move the page to Sandbox/Test2, with or without children.

Expected behaviour :

• Copying : each page has its own working task - or maybe same task with same status
• Moving : the task remains functional and in the same status

Actual behaviour :

Moving the page to Sandbox/Test2 :

• Moving with children : the task from within the page will still have this Sandbox/Test1/Tasks/Task_0 reference. After moving, that page will not exist any more. Saving the page will create a task page at the specified reference but with a new id, id 2. Another issue is that Sandbox/Test2/Tasks/Task_0 will exist, with id 1, without any macro pointing to it
• Moving without children : no problem tThe task will point to this Sandbox/Test1/Tasks/Task_0 reference that was not moved and still exists)

Copying the page to Sandbox/Test2 :

• Copying with children : The macro from the copied page will point to Sandbox/Test1/Tasks/Task_0 that still exists and has id 1. Since its children were also copied, there will exist Sandbox/Test2/Tasks/Task_0 that will have the same id as Sandbox/Test1/Tasks/Task_0. This will cause a conflict when trying to click on the checkbox of a macro
• Copying without children : both Sandbox/Test1 and Sandbox/Test2 will have a macro that points to Sandbox/Test1/Tasks/Task_0, just as in the other case. No copy of it will exist. However, its not ideal, since there should exist a 1 to 1 relation between a macro and a page

[raphj]

Could storing tasks in a separate database table make this kind of issues easier to deal with?

[raphj]

Maybe related to #132?