Closed (duplicate)
Project:
CiviCRM Theme
Version:
5.x-1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2007 at 21:26 UTC
Updated:
30 May 2010 at 19:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
douggreen commentedI hadn't considered the dashboard as an admin page, but I guess that it usually is. Are there other pages you are thinking about?
I've temporarily added this as an option, but I'm not sure that I like it. Rather than commit it to CVS right now, I'm attaching it as a patch here. Feel free to try it out.
Comment #2
douggreen commentedComment #3
JuliaKM commentedThanks! That was really fast. Here are other pages that I think could be included in the admin theme:
civicrm/event?reset=1
civicrm/contact/view?reset=1&cid=(Contact Id)
civicrm/import?reset=1
civicrm/contribute?reset=1
civicrm/mailing?reset=1
civicrm/mailing/send?reset=1
civicrm/member?reset=1
civicrm/member/search?reset=1
civicrm/event?reset=1
I am just learning CiviCRM, but it seems like the pages that include "reset=1" and do not include any further text could be considered admin. Is there any easy way to force that these always be displayed with the admin theme?
Comment #4
douggreen commentedI don't think that the reset=1 is going to be the right thing to check. I was hoping that we might be able to use the user access permissions to determine what the site administrator has defined as "admin" verses available to users. But that's problematic because we really don't know which role is the "admin" role. As I said before, I'm not sure that the admin settings interface is the best choice either. But that might be the only fall-back.
I'll ask some more experienced CiviCRM user's to comment...
Comment #5
JuliaKM commentedAfter thinking about it more, I realized that the only pages that are exposed to end users are contained in the directories of contribute and event. There might be another page or two hidden in there that I have overlooked.
I modified your _civicrm_theme_get_var function to default the contact, group, import, mailing and member $arg1 variables to the admin theme. Then, for the event theme, I added a $arg2 variable and have the admin theme showing when $arg2 is empty. When $arg2 shows and is info or register, then the normal theme displays. I don't have CiviContribute set up yet, so in the meantime I tried to use similar logic to what I am doing for event.
Here's the revised function. It still needs to be cleaned up quite a bit and integrated with checkboxes under CiviCRM Theme in the menu.
Comment #6
matt2000 commentedFor an approach that allows the user to choose which paths to define as 'public', see:
http://drupal.org/node/267355
Comment #7
deviantintegral commentedI'm marking this as a duplicate of #804804: CiviCRM backend should use admin theme.