Disable clickable headers in custom view
Hi YaleSites team,
This request is a follow-up question on work I did with the help of Josue.
The “Publications” section of my YaleSite has two subsections that display publications by year: Articles and Chapters. To do so, I created a separate basic page for each year of publications, with the year as title, and tagged them as articles or chapters. Then, I created a custom view for articles and one for chapters, which display only the basic pages tagged as articles or chapters, respectively.
The only problem with this approach is that the basic pages are not hierarchically nested under /publications/articles and /publications/chapters, so when the headers are clicked (i.e., the basic page is opened outside of the custom view), the navigation sidebar goes away and the breadcrumbs are off. See here for an example. I tried forcing the URL of the basic pages to be hierarchically organized (e.g., publications/articles/2015) but this does not resolve the issue.
For that reason, I would like to simply remove the links for the basic pages’ headers, as they are unnecessary anyway. As such, the custom views for articles and chapters would still list the relevant basic pages, each with the publication year as header. But without clickable headers, visitors to the site won’t be able to enter the basic pages from the custom view. To my knowledge, this constitutes the easiest workaround for the described issue.
Request: How can I disable the links from the basic page headers (2015, 2014, etc.) in my two custom views for articles and chapters?
Thank you very much!
Fabian
Hi Fabian,
I ‘d be glad to assist you with you issue, can you please provide me with access my Netid mk858.
Thanks,
Hi Marwa,
You should have admin rights now. Thanks for your help!
Fabian
PS: If you can think of a way to address this issue without disabling the links in the headers, I’d be open for suggestions.
Hi Fabian,
You are all set, I changed both views for “Articles” and “Chapters” pages. The Format setting is set to show: as “Fields” rather than “Content”, then I added your content type fields.
Thanks,
Thanks for your help!
You are very welcome, happy to help.