Asset lineage keyword for file type assets

(Tim Davison) #1

I have noticed that the %asset_lineage% keyword is not working for file type assets that are live and public read.  My immediate take on this is that public file assets are moved the be served by apache when live (hence being served from the __data location), and seems that's right, as under construction and archived file assets are showing lineage fine.  

 

But does that mean in asset listings I can't get the lineage with this keyword? 

 

Additional Info:

Matrix v4.12

Asset listing is using 'Array of specific IDs' in a POST parameter (not sure this would make any difference).

 

Nothing else special, just trying to use %asset_lineage% in the default type format bodycopy.  All other asset types work fine, and non-published file assets.

 

Cheers

(Talk) #2

Hi Tim, as far as I know, the only way around this is to deselect 'Allow unrestricted access' on the details screen of the file assets. This will mean they are served by Matrix and will retain their lineage. You can create a trigger to enforce this setting when new files are created/published.

(Tim Davison) #3

Thanks Jeremy

 

Changing that setting is probably not going to work for us - we get too much performance boost by static files being served from apache.  Just seems odd to me to have that restriction.  I'm assuming I probably also couldn't get the lineage from the JavascriptAPI for the same reason?  

(Talk) #4

Yeah, I thought that'd be the case. I don't think getting the webpath from JS API will help you build and print the lineage as the restricted webpath is killed once the asset is published. You could try running getGeneral on a file asset ID and see what's returned.