Closed (outdated)
Project:
Administrative pages
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 Feb 2012 at 20:39 UTC
Updated:
16 Jan 2017 at 18:24 UTC
Jump to comment: Most recent
Comments
Comment #1
casey commentedYou could use panels or something like that, so you have 2 different paths to access those nodes (e.g. panel with path "content-overlay/nodetype1/*"). Then you could add that path to the list of administrative pages.
Comment #2
IWasBornToWin commentedSounds like a plan. I will try it.
Just noticed in user settings [since permissions must allow authenticated user to view overlay] an authenticated user can check or uncheck whether to use overlay. Not sure I want them to or that many will know what it means, particularly during sign up. Anyway to hide that? I will open this in a new issue if you want me to?
Comment #3
Blooniverse commented@IWasBornToWin#2: This setting belongs to the D7 core (overlay core module). There is no direct link to 'Administrative Pages'.
Comment #4
IWasBornToWin commentedThis may be useful for future reference. I already had CSS Injector module installed, So I just made a quick injection for the user/*/edit page and inserted this code.
#edit-overlay-control {display: none; }
It hides the whole thing!
Comment #5
kurkuma commentedShould this be closed since it is non relevant for the module functionality?
Comment #6
casey commentedI agree