Commit Graph
4 Commits
Author SHA1 Message Date
Pedro M. Baeza b122526666 [FIX] pad_project: avoid rewriting project on task saving
Due to the side effect on related fields that are not readonly, the value is saved
in project although not changed. Putting it readonly avoids the problem.

Fixes #26156
Closes #26171
2018-08-08 15:42:13 +02:00
Nicolas Martinelli 4badf49ad0 [FIX] pad, pad_project, note_pad: duplicate object
The duplication of a task crashes at the following:
`content = myPad.getHtml(path).get('html', '')`

The copy mechanism is quite cumbersome:
- In `copy` method, generate an URL of a pad which doesn't exist since
  `object_id` is still undefined.
- The `create` method somehow attempts to fill in the previously created
  pad thanks to `_set_pad_value`.

The logic is made simpler. The pad URL field is set as `copy=False`,
therefore the create mechanism will take care of handling the pad
creation and its synchronization.

opw-1818757
2018-03-05 08:42:11 +01:00
Yannick Tivisse d3efda05fd [FIX] (project_)pad: Don't create/copy pads on tasks that don't use them
Purpose
=======

Currently if a project doesn't use pads, the created and duplicated tasks will initialize/copy them. That could be a real issue when migrating customers if we create a task for all the existing issues, since the models have been merged.

Specification
=============

Avoid this falsy behavior. We're forced to crappy fix with a context key as the project.task model 'inherit' from pad.common.
2017-11-27 12:26:44 +01:00
Yannick Tivisse f8a1e9f6e7 [IMP] pad_project: Allow to activate or not pads on a project 2017-08-07 12:21:26 +02:00