Hi. I'm using an asset lineage (%asset_lineage_linked%) to display Search results. However, when the search hits a Word or PDF file, I get an warning message saying "Unable to find an lineage for the URL…" (it still shows the search result).
The files are stored in an Asset Listing Page with a valid URL. I suspect this may have something to do with the fact that it is serving the files directly from Apache.
Is there a way to stop this warning showing – or better yet, show the proper lineage "files > file_name"?
Thanks,
David C
This has already been submitted as a bug: http://bugs.matrix.squiz.net/view_bug.php?bug_id=804
Basically the response is that we cant work out a lineage for a File assets that is served by Apache because the URL does not show where it is located. We could change the asset listing to allow for this, but it would slow down lineage generation for everything else. It may be the only way to do this though.
For the mean time, you’ll cant use this keyword with File assets. You can create a new type format and define a different listing format for File assets.
Hi,
I'm having the same problem as davidc. I'm trying to fix our search so that the error doesn't keep on coming up in the logs. I know how to set up a separate format for files in an asset listing, but what about search (which is where we're using %asset_lineage% and the errors are occurring)?
It would seem to me an easy solution is to just turn that warning off for files (or have an option to do that).
It does give the right result, and I'm happy without a lineage in that case, it's just the message makes it look very messy.
You can hide errors on the frontend by changing a config option on the System Admin screen. We cant turn it off because we rely on the errors for other parts of the system.
As for the search page, you can configure a seperate result format for each type of asset as well - or at least you can in the newer version (might not be in the current stable 3.4.x).
The search page in 3.4 doesn't support different formats for different asset types (type formats), only the Asset Listing does this.
In 3.6, however, all listing functionality has been moved out to a component called the Listing Engine that supports grouping, type formats, and sorting, amongst other things. Search Page, Asset Listing, Search Listing, and the What's New page (and a few others besides) use this component, so the above functionality will be available to all these asset types.
Thanks for the info.
Just an update of this problem: the bug does not exist in version 3.5.x, 3.6.x and 3.7.x because of the introduction of the Listing Engine and the rewrite of the Search and Asset listing assets.
The bug will not be fixed in stable, but will be fixed in the next stable (3.6.0) next month.