[Neos] TYPO3CR nodes : lastChanged

Dominique Feyer dfeyer at ttree.ch
Tue Jan 28 16:35:51 CET 2014

You can maybe use EventSubscriber, check
TYPO3.Flow/Configuration/Testing/Settings.yaml check for "eventListeners"

ttree sarl
Dominique Feyer
TYPO3 Addict
Rue du Valentin 34 et demi
CH - 1004 Lausanne
Téléphone +41 21 312 36 35
www.ttree.ch | twitter <http://twitter.com/ttreeagency> |
Plan d'accès: http://g.co/maps/4yu6t

2014-01-28 Bernhard Schmitt <himself at nezaniel.org>

> Hi there,
> I am currently working on adding a lastChanged attribute to the NodeData
> model for general use, e.g. in RSS and XML sitemaps. While the model
> changes work fine so far, I have issues with automatic updating of the
> attribute on persistence.
> I talked to Robert about this at T3DD13 and came to the conclusion to use
> the @ORM\PrePersist annotation on an updateLastChanged method. It worked
> back then, but now (v1.0.1) the method is still called on persistence but
> seems to have no effect any more, i.e. the value isn't persisted in the
> database.
> A possible solution is to call updateLastChanged in NodeData::update, but
> the original solution seems much better to me since the NodeData::update
> method can be circumvented by directly calling NodeDataRepository::update.
> Is there any way to get the annotated version running again? Or are
> Aspects the way to go in 1.x?
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos

More information about the Neos mailing list