DrillSergeant

When I have situations like these, it's most of the time a different package loading order. I would compare the output of `./flow package:list --loading-order` on both systems. Mabye your...

Ok, seems not to be the source of error in your case. Nevermind, was just a shot in the dark.

@Benjamin-K We have a customer where content editors are located around the globe. So they had trouble interpreting the DateTimes they entered in the Neos backend. In our case we...

We start using the custom presets for a current project and now I am affected of this issue. I could sponsor a bugfix if anyone could do this in the...

Thanks for the work so far and for caring to fix the last known issue.

Would be good to have this done before you do a new UI-release. In our current project the editors (more than 20 of them) will start editing content by the...

@kdambekalns , I think this could help. But I also just got the budget for the implementation of the "timezone-aware datepicker". I am in contact with @kitsunet about the implementation...

@kitsunet developed for our usecase the package https://github.com/flownative/neos-extendedtimeeditor I am not sure if this PR has an influence on that.

I am also experiencing this behaviour. Our setup is: - 1 Dimension "language", 4 values: en, de, fr, es - no fallbacks Behaviour: Only nodes are indexed that are in...

With the merged PR #350 (version 7.0.3) this issue is gone in my current project.