CiviCRM Community Forums (archive)

Hi all,

Yesterday I upgraded Drupal from 6.20 to 6.22. Upon completion, CiviCRM 3.3.5 page layout was completely broken; the navigation menu that traverses the top of the screen was instead displayed as a mess of links down the left-hand side of the page, a problem observed in both Firefox on one machine and Firefox and Chrome on another. The dashboard suggested that JavaScript wasn't enabled, despite JavaScript confirmed as enabled on at least one of the machines.

I then decided to try upgrading to a more recent version of CiviCRM, 3.4.3, to see if that fixed the problem. Following the instructions at wiki.civicrm.org/confluence/display/CRMDOC40/Upgrade+Drupal+Sites+to+3.4, the upgrade proceeded as planned until step 8, "Run the Upgrade script". Confirming that Drupal "clean URLs" are enabled, I tried opening the URL:

http://<your_drupal_home>/civicrm/upgrade?reset=1

(replacing "<your_drupal_home>" appropriately, of course), only to receive a blank page. Checking the Drupal Status page, which informed me:

"warning: include_once(CRM/Core/Config.php) [function.include-once]: failed to open stream: No such file or directory"

and that I should check that the value of the $civicrm_root variable in drupal/sites/default/civicrm.settings.php is correct, which it is. I also confirmed that CRM/Core/Config.php exists.

Some research via Google suggested modifying the file drupal/sites/all/modules/civicrm/civicrm/install/index.php and replacing the text DIRECTORY_SEPARATOR with '/', which I did thus:

 if ( stristr( PHP_OS, 'WIN' ) ) {
    define( 'CIVICRM_DIRECTORY_SEPARATOR', '/' );
} else {
    define( 'CIVICRM_DIRECTORY_SEPARATOR', '/' );
}

given that this installation is running on a Unix-type server. Trying to run the 'upgrade' URL of step 8 now produces a "Page not found" error.

I have verified that all relevant file ownerships and permissions are correct. I have also tried deleting the templates_c folder and its contents, and recreating it - with the correct ownerships and permissions - without success.

Any suggestions as to how to proceed would be much appreciated!


Alexis.

@ Hershel:

Yes, I had cleared all caches; my apologies for not mentioning that in my original post.

However, disabling and then re-enabling the CiviCRM module worked - it allowed the upgrade process to proceed and complete, and 3.4.3 is now running.

That's the good news. The bad news is that the upgrade didn't fix the original problem; a screenshot of what I'm seeing is available at imgur.com/CChZp . That page is also taking an quite a long time to finish loading - nearly 70 seconds, compared to non-CiviCRM Drupal pages, which load up within less than 10 seconds.

Thanks for your help so far!


Alexis.

@ hershel,

No, unfortunately, asking the browser to refresh the page doesn't fix the problem; neither does selecting the "Refresh Dashboard Data" link. Additionally, I have again gone through the process of both clearing Drupal's caches and emptying the templates_c folder.

In terms of load times, I don't believe this to be a hosting issue, as, prior to upgrading Drupal from 6.20 to 6.22, CiviCRM loaded up similarly quickly to other non-CiviCRM pages on this host. The long load times have only appeared with Drupal6.22+CiviCRM3.3.5 and Drupal6.22+CiviCRM3.4.3.


Alexis.

Another update:

I've been using HttpFox to observe request/response traffic when loading up the CiviCRM dashboard. All GET requests for resources under /drupal/sites/all/modules/civicrm/ are returning a 404 response, which explains why (a) CiviCRM is taking so long to load, (b) the navigation menu layout is broken and (c) the loaded page states "Javascript must be enabled in your browser in order to use the dashboard features". The resources being requested are definitely there, and I can confirm the 404 responses are specific to CiviCRM rather than Drupal in general: the Drupal admin pages are still accessible.

Any suggestions as to what might be causing this?


Alexis.

@ hershel:

Yes indeed; but why would this be the case? That is: We had a working CiviCRM installation, upgraded from Drupal 6.20 to 6.22, and now those files aren't accessible. I did a diff on the Drupal .htaccess file between 6.20 and 6.22, and the settings are apparently identical. I've also confirmed that the ownership and permissions of the /drupal/sites/all/modules/civicrm/ directory and its subdirectories are correct. Is/are there one or more settings elsewhere that I also need to be checking?

@ hershel:

No, trying to access:

[mysite.com]/drupal/sites/all/modules/civicrm/packages/jquery/jquery.js

returns a 404.

My pleasure. Glad you got it working.