Now that we are using black for formatting the code, most python files are using double quotes. However, zest.releaser seems to overwrite these quotes when updating the version number, and so this needs to be manually fixed each time we prepare a release. zest.releaser 6.22.1 fixes support for this when using __version__, however it's not trivial to have this attribute set as a single source. See PEP 396 and the single-sourcing package version number documentation for more info.

.

Summary

Create tests for object modified, object parent modified and the "Preserve modification date" configuration

Requirements

• Create framework for running tests
• Create test for ensuring the content rule action is triggered when the triggering event is set to 'object modified'
• Create test for ensuring the content rule action is triggered when the triggering event is set to 'object parents modified'
• Create test for ensuring that when the "Preserve modification date" option is enabled, the setfield action does not alter the date of the affected object
• Wire up travis

Problems Encountered

Importing content rules before object creation results in unwanted action triggering as object creation results in ObjectModifiedEvent being emitted. Content rules should be imported after content creation to alleviate this.

So triggering on one object always triggers for everything in the site? That seems really dangerous to me.
collective.contentrule.parentchild solves the case of updating children etc better and without having to reimplement all conditions.

<type 'exceptions.TypeError'>, 'NoneType' object has no attribute '__getitem__'
i
Mostly likely where it tries to get the workflow state. https://github.com/collective/collective.contentrules.setfield/blob/master/collective/contentrules/setfield/action.py#L189.

Given you can get the workflow state using obj.restrictedTraverse('@@plone_context_state').workflow_state() in a script, I don't think you need this.

Commit beb7822 introduces a bug in contentrules.setfield.handlers Line 19, where creating a new site throws an AttributeError before the site is successfully created.

Updating to the master branch's latest commit, 8edaedb does not solve the issue.

Steps to reproduce

1. Setup buildout with this package installed
2. Create a new Plone site
3. Enter the site information and press "Create Plone Site"

Expected Result

The new Plone site is created and the welcome page appears

Current Result

A site error occurs with the following error:
Error Type: AttributeError
Error Value: getFolderContents

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