Closed (outdated)
Project:
Event
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2008 at 15:45 UTC
Updated:
13 Apr 2018 at 21:01 UTC
Jump to comment: Most recent
Comments
Comment #1
killes@www.drop.org commentedFor me, the normal (non admin) theme shows no matter which type of node I edit.
Comment #2
webcomm commentedI'm not sure I'm understanding you. The expected behavior is that when the user changes the admin theme to something other than the public theme, and checks the box for "Use administration theme for content editing", then that admin theme should be visible when you edit nodes of any content type. I'm getting the expected behavior in all cases except when the content type is Event-enabled.
In other words, for nodes of any content type where "Show in event calendar" is set to "All views", the Administrative theme config at /admin/settings/admin doesn't work.
Comment #3
killes@www.drop.org commentedOk, I hadn't checked the checkbox.
If I check it, then the event is shown in the admin theme.
I suspect that maybe another module plays some tricks here. Can you try to disable all extra modules besides event?
Comment #4
webcomm commentedhmm. I'm not sure what you have in mind by "extra modules." Can you clarify? This is the version of the Event module I'm using: 6.x-2.x-dev from June 15. It looks like another version was released yesterday, but I haven't upgraded.
Other than core modules, I'm using various CCK modules, ecard, FCKeditor, IMCE, Menu breadcrumb, Image attach, ImageMagick Advanced Options. The only ones that might be a factor with my Conference Calendar content type -- the only Event-enabled content type I have -- would be FCKeditor and CCK. That's what I would think. But those modules aren't causing problems with my other content types.
Let me know what you'd like me to try.
Thanks.
Comment #5
killes@www.drop.org commentedextra modules == non-core modules
I don't know which of your modules miht be doing it, but I could not reproduce this on a bare-bones test install with core and event.
Comment #6
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.