If I enable asset caching in CiviCRM everything works fine. If I disable it, the administration menu is gone from the top to a list that's beneath the page content and a lot of JS is broken too.
The reason for the broken JS (and maybe the broken CSS too), is (at least for some scripts) that in the files that are on my installation in /sites/default/files/css/ and /sites/default/files/js/ is somewhere in the middle of the JS code (and the css code) some PHP code, namely:
<?php /** * @file * The PHP page that serves all page requests on a Drupal installation. * * The routines here dispatch control to the appropriate handler, which then * prints the appropriate page. * * All Drupal code is released under the GNU General Public License. * See COPYRIGHT.txt and LICENSE.txt. */ /** * Root directory of Drupal installation. */ define('DRUPAL_ROOT', getcwd()); require_once DRUPAL_ROOT . '/includes/bootstrap.inc'; drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL); menu_execute_active_handler(); ;
When asset caching is enabled, there are different css and js files used, that are beneath the "image uplod url". And they seem to work properly.
I would like to disable asset caching, because I want to provide the images from a different server, so that they are loaded faster, to save bandwidth to our CiviCRM server and to have not so much load on the server, which has a lot of work, when sending mailings with images, tracking links and providing petitions by CiviCRM.
That asset caching is making use of the image uploud url, is imho not really intuitive, but thats a different story.
Does anybody have an idea what the reason is and how to solve this?