collective / collective/collective.contentrules.setfield
way to initialize values on rule save
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If you change the code you might want to reset the site to ensure all the values are correct. One way to achieve this is a
```
[ ] run against all matching content on next save
```
Which will reset to no again after it's saved.
The rule really has to run against all content, not using a query to bypass content. this is due to the way querysplitter works. or any other unknown condition from a plugin. You run the risk of having events specific to certain kinds of content though which then result in this being trigger on objects you don't expect.
If available should be done via async
this will have to only trigger in parts of the site where the rule is activated
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.