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
Created by: Joel Bradbury ([email protected]) on 2015/03/18 14:30:51 +0000
Votes at time of UserVoice import: 6
It’d be lovely if we could just hit $source->indexFile($path) to reindex a single item. Currently that’s protected.
In this specific use case, we have a setup where files are uploaded from external services to s3 based on user interaction.
They need to be later turned into asset models, and to get that sorted we need to reindex the external (in this case s3) source.
As we already know the exact remote path we want to be able to just call indexFile($path) on the asset source, but as it’s protected the only native route is to go via the processIndex().
This discussion was converted from issue #989 on July 13, 2021 03:55.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It’d be lovely if we could just hit $source->indexFile($path) to reindex a single item. Currently that’s protected.
In this specific use case, we have a setup where files are uploaded from external services to s3 based on user interaction.
They need to be later turned into asset models, and to get that sorted we need to reindex the external (in this case s3) source.
As we already know the exact remote path we want to be able to just call indexFile($path) on the asset source, but as it’s protected the only native route is to go via the processIndex().
Exposing indexFile() publicly would sort this.
Beta Was this translation helpful? Give feedback.
All reactions