Something changed between 1.4 and 1.5 that broke access to newly created views with 'System' displays.
I've tested this with both 1.4 and 1.5 by installing the module, cloning the 'Administration: Nodes' view and changing it's 'System path settings' to '/admin/test'. In 1.4 it works as expected, but in 1.5 that page simply takes me to the default '/admin' Administration Tasks index. If I specify a path like '/testing' I get a 404 Page Not Found response.
The default system views like 'Content' which are overridden when enabling the module work as expected.
Comments
Comment #1
damiankloip commentedHmm, this is not really meant to work.. The system display is only for replacing existing paths. We only changed access recently due to a massive sec hole. So if a menu item exists for your item, it will use it.
Why are you using the system display to create new pages?
Comment #2
aaron.silberI actually came back here to ask about that. I'm using the system display because I didn't get enough sleep last night and in a hurry to get through the first few hours of this project!
So, for anyone stumbling upon this, 'system' displays are only to override core views (which you do through the System Path Settings area in the Advanced section of views) and I should just be using a page display with a path that begins with '/admin/' if I want to make custom admin views.
Case closed — thanks for the quick response.
Comment #3
damiankloip commentedNo problem :) But it might not be a bad idea to add some path validation in the UI to enforce that?
Comment #4
damiankloip commentedComment #5
cslevy commentedLike @damiankloip said...just replaces existing path. So If you want to use custom system displays, create them, and also create some empty pages with hook_menu. Then the path will exists and the admin_views will replace them with views.
Comment #6
damienmckennaPlease try the latest Views and Admin Views module updates, let me know if the problem persists.