Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle auto-save #61

Closed
limenet opened this issue Mar 14, 2024 · 0 comments · Fixed by #62
Closed

Handle auto-save #61

limenet opened this issue Mar 14, 2024 · 0 comments · Fixed by #62
Assignees

Comments

@limenet
Copy link
Member

limenet commented Mar 14, 2024

Currently, a Pimcore autosave triggers an element refresh. This can be seen as both a bug and a feature. Solutions:

  1. Introduce a Symfony Config option for assets / data objects / documents to disable that feature (default is enable for BC reasons)
  2. Offer tagged interfaces with a supports strategy to provide custom logic

For simplicity reasons, option 1 will be implemented. If advanced logic is needed, a project can define a listener with a higher priority than what's defined in \Valantic\ElasticaBridgeBundle\EventListener\Pimcore\ChangeListener::getSubscribedEvents and call \Valantic\ElasticaBridgeBundle\EventListener\Pimcore\ChangeListener::disableListener.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant