Download & Extend

Taking over the /galleries URL

Project:Node Gallery
Version:6.x-3.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

This is a remarkable module. The administrative workflow alone makes it a must for my clients. I just wish it didn't have to take over the /galleries URL.

I'm having a problem with "View display to use at /galleries" being a global setting because it (seemingly unnecessarily) prevents Panel's pages or other custom page content from from being able to use the /galleries URL.

Is there really a need to forcibly take over the /galleries URL only to turn around and provide a list of views to use for its content? After all, the most familiar way to specify a View's page display (or Panel's Page) to live at a specific url is to change the path in the views/panels UI. In other words, if I want the Page display "Galleries Teaser List" (from the node_gallery_gallery_summaries view) to be displayed at /galleries, all I have to do is edit the view and change the Path for this particular display from 'node_galleries' to 'galleries' and save. Or, if I wanted to use the "Galleries Cover Grid" page display from that same view, all I have to do is change that display's path from "node_galleries_grid" to "galleries".

It seems like not only would this be a more familiar way of assigning URL to a view (seriously, it took me an hour to figure where /galleries was coming from), it is also more compatible with Panels style pages.

Comments

#1

Valid point. FWIW, the /galleries hardcode was an artifact from 1.0, before any views integration. I'll see what we can do. I'm extremely strapped for time, so any patches (from anyone) would be hugely welcomed.

#2

This would be nice to fix, but there are other things involved such as breadcrumbs. Configuring a view to use a path is not going to make breadcrumbs work.