Closed (fixed)
Project:
Open Atrium
Version:
7.x-2.43
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Jul 2015 at 03:13 UTC
Updated:
12 Aug 2015 at 12:54 UTC
Jump to comment: Most recent
Comments
Comment #1
andrimont commentedIt seems that panopoly_theme or one of modules linked to are the trouble maker. I can use the overlay of CiviCRM normally after the following extensions had been be disabled: panopoly_theme, panopoly_admin, oa_layouts, oa_discussion, oa_events, oa_events_import, oa_files, oa_permissions, oa_worktracker, oa_worktracker_duedate
It seems that there is a conflict between one of these modules (panopoly_theme, panopoly_admin, oa_layouts, oa_discussion, oa_events, oa_events_import, oa_files, oa_permissions, oa_worktracker, oa_worktracker_duedate) and CiviCRM.
As soon as panopoly_theme is enabled, there is a conflict with civicrm.module as you can see in this drush command :
The following extensions will be enabled: panopoly_theme
Do you really want to continue? (y/n): y
array_shift() expects parameter 1 to be array, string given civicrm.module:66 [warning]
array_shift() expects parameter 1 to be array, string given civicrm.module:67 [warning]
[…]
panopoly_theme was enabled successfully.
Then it is impossible to use CiviCRM.
Comment #2
jakeschlachter commentedThis issue is caused by a fix recently committed to the media module and picked up by Open Atrium. (In media, they were trying to fix a problem when opening the media browser in a Ctools dialog.)
The actual issue is a CSS z-index error, where .ui-front is being defined by both media module and CiviCRM. In media, they just changed their z-index to be !important, which is preventing CiviCRM from overriding it with an inline style. The net result is that the CiviCRM dialog boxes are placed "below" the active z-index, and it's impossible to click them.
The right place to fix this is probably the related issue in media, or perhaps CiviCRM. In the meantime, I got CiviCRM working again by hacking /profiles/openatrium/modules/contrib/media/css/media.css and removing the !important property from the .ui-front selector. (Note that this is a lousy long-term fix, and will be undone the next time you upgrade open atrium.)
Comment #3
jakeschlachter commentedComment #4
mpotter commentedThis is definitel something that should be posted over in the Media module issue queue. Nothing we can do about it in Atrium.