Shortcut issue caused by CSS caching [#1861304]

Shortcut bar doesn't display properly in CiviCRM. It seems to be caused by CSS caching and related to running CiviCRM from the profiles directory, but not sure why.

Comment	File	Size	Author
#4	menu.css_.txt	6.51 KB	kreynen
#2	css_caching_on.png	72.18 KB	kreynen
#2	css_caching_off.png	167.75 KB	kreynen

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

sadashiv CreditAttribution: sadashiv commented 7 December 2012 at 18:37

Do you mean that the civicrm menu bar is not visible? if no, please provide a screenshot, if yes then try menu rebuild of civicrm. http://mysite.com/civicrm/menu/rebuild and refresh the page after that (assuming clean urls is enabled).

Hth,
Sadashiv.

Comment #2

kreynen CreditAttribution: kreynen commented 7 December 2012 at 19:50

File	Size
css_caching_off.png	167.75 KB
css_caching_on.png	72.18 KB

This is true for the this distribution and http://drupal.org/project/civicrm_starterkit so I think it's yet another issue that stems from running CiviCRM from profiles/[profile]/modules instead of sites/all/modules. This Drupal's shortcut bar, not CiviCRM's menu... but only in the /civicrm path.

The steps to reproduce are easy. After installing either distro, turn on CSS caching in admin/config/development/performance

Comment #3

kreynen CreditAttribution: kreynen commented 30 January 2013 at 16:28

We're seeing this again at MNN, but it isn't consistent across all sites using Drupal and CiviCRM and/or an install profile. Starting to pull together related issues to find a real fix...

#745416: Civicrm does not add the @import to the page and the page will not load css in ie
Drupal: load civicrm.css using drupal_add_css()
Strange CSS error on upgrade to 4.2.6

Comment #4

kreynen CreditAttribution: kreynen commented 8 July 2013 at 15:55

File	Size
menu.css_.txt	6.51 KB

While looking at a CSS caching issue completely unrelated to CiviCRM, I found this...

#881132: CSS Optimization breaks with non-UTF-8 .css files

That finally pointed me in the right direction to find the root cause of the this issue too. The patch that re-adds /profiles/civicrm_starterkit/modules/civicrm/packages/jquery/css/menu.css or /profiles/cm_starterkit_[LEVEL]/modules/civicrm/packages/jquery/css/menu.css back to CiviCRM had an error which caused the file to end the .css prematurely with an open bracket. When aggregating the CSS, Drupal then ignores a lot of CSS that comes after that. Ideally Drupal would log the fact that it found non-compliant CSS while aggregating the files, but instead it just leaves the CSS out of the cache file it creates. The issue with the patch has been fixed in the 2.x branches of the Starter Kits that include CiviCRM 4.3.4, but you can also replace the menu.css with the attached CSS if you aren't at a point you can upgrade CiviCRM.