I’m working on an issue that one of our users reported with the Metadata Browse module. The user has selected several types of metadata to be browesable, and they have also selected under Site setting → Attachment link type => Media page because they liked the look of the media show pages better. As a result, they have extensively described the media, because that is the page that they are linking to.
However, there is a bug in the way that MetadataBrowse builds search parameters for media (i.e. the link that says “see all <resource_type> with this value”).
I believe it is because MedatadaBrowse is making some unsafe assumptions about the actions/views that are available on the public facing site, and so it is building the search using the pattern /s/site-slug/<controller_name><search_parameters>
. However, because there isn’t an action in Site/MediaController
to handle this (e.g. browseAction()
) the controller cant dispatch the request.
I’m looking for some advice on how to best go about patching this. I think the ideal solution would be to add a browse action and corresponding view to the Site/MediaController
in parity with the Admin/MediaController and the Item
and Itemset
site controllers.