You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just occurred a strange behavior during the initial loading/creating of the database entries.
I started with this setting Neos.MetaData.Extractor.realtimeExtraction.enabled = true, can't delete newly uploaded images and don't see any metadata in the tab.
When searching in the database, I quickly found the problem:
It does not use the live workspace to create '/assets' but my own user's.
Steps to reproduce:
new Neos system with empty database and Neos.MetaData.Extractor.realtimeExtraction.enabled = true
upload an image via the media management
try to read metadata (empty and when trying to write 'null-Exception')
try to delete the picture (should not work either)
However, if you start with Neos.MetaData.Extractor.realtimeExtraction.enabled = false initially, upload an image and then ./flow metadata:extract, all these problems do not exist, since the correct workspace is taken as the basis.
Any cool suggestions how to fix this asap?
The text was updated successfully, but these errors were encountered:
After the (slightly ugly) local rebuild of the package, I was able to drag the live-wokspace with $this->contextFactory->create();.
I then used it in the findOneByPath call and for getRootNode and solved the problem.
But I'm not very happy with this implementation because I already have a context and with this solution I just create a 'new' one😅
I have just occurred a strange behavior during the initial loading/creating of the database entries.
I started with this setting
Neos.MetaData.Extractor.realtimeExtraction.enabled = true
, can't delete newly uploaded images and don't see any metadata in the tab.When searching in the database, I quickly found the problem:
It does not use the live workspace to create '/assets' but my own user's.
Steps to reproduce:
Neos.MetaData.Extractor.realtimeExtraction.enabled = true
However, if you start with
Neos.MetaData.Extractor.realtimeExtraction.enabled = false
initially, upload an image and then./flow metadata:extract
, all these problems do not exist, since the correct workspace is taken as the basis.Any cool suggestions how to fix this asap?
The text was updated successfully, but these errors were encountered: