- Issue created by @london6339
- 🇩🇪Germany jurgenhaas Gottmadingen
Here is a brief run-down on how that could look like:
- Event: Update content entity
- Action: get field value - this stores the date value into a token
- Action: Tamper Math - this requires the eca_tamper module and allows you to add your 6 months (=15768000 seconds) to the timestamp in that token you stored the date value into
- Action: Entity load - this allows you to load an entity by properties where you can search another node by the name of your new content B. If no match is found, ECA will not continue processing. If loading the entity by property is not sufficient, you can use a view to find the matching entity
- Action: Entity set field value - you can set the field value with the calculated token value from above and save that entity
You may want to build some safe-guards into that model, otherwise the update of the second node will trigger the same model again as this is then also a content update. If your 2 contents A and B are of different type or bundle, you can limit the event by the type and/or bundle of the content B.
- Status changed to Fixed
4 months ago 6:56am 27 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.