Uwe Jäger

Currently I use something like this in our manual fixtures: ``` contact: class: Website\ContentBundle\Document\Page locales: en: metaTitle: "Contact - Test" metaDescription: "Contact - Test" de: metaTitle: "Kontakt - Test" metaDescription:...

I did a quick research and unfortunately the different Doctrine behaviours (ORM) feature different APIs and differ again from PHPCR-ODM. I will look into the processors stuff, maybe that can...

Unfortunately the processors have no knowledge of the original fixture data, so this doesn't seem to help. Maybe we can introduce an other syntax like ``` metaTitle:de: Titel ``` or...

What we need for phpcr odm in the end is something like this: ``` foreach ($locales as $locale => $value) { $page->setMetaTitle($value); $page->set ... // another translated field $manager->bindTranslation($page, $locale);...

For doing this we still have the translations issue and maybe image loading although I'm not sure we have images in the fixtures ...

The document seems to be fairly new (compared to the rest in the wiki). Doing it in Jackrabbit (if the api is exposed via davex ...) will not work for...

Could this be done differently? We would like to store the complete interaction in the database for humans to read. Also, since here pop is not implemented for all memory...

Instead of actually pruning the messages we could keep the indices of the messages in the buffer to use.

I just realized that for my use case I should also persist the summary of the chat and mark all the messages that have been summarized. Looks like custom ChatMessageHistory...

Just spent some time finding out why LockStoreSchemaListener does not work in 6.4 before coming here. Is there a chance the existing PR will get merged into 6.4 (or will...