Author Topic: Move third-party libraries out of the Drupal module directory? (Read 1252 times)

TallDavid · December 04, 2010, 01:16:54 pm

It has recently come to my attention that Drupal performance improvements can be realized by moving 3^rd-party libraries out of the Drupal module directory: Move third party libraries outside the modules folder

CiviCRM uses a number of 3^rd-party libraries including CKEdit, jQuery, reCaptcha, tcpdf, etc. which are included under the ...\modules\civicrm\packages directory. Moving these libraries out of the modules folder should provide a performance increase for the entire Drupal site... even when the CiviCRM system is not actively in use.

The Drupal Libraries API provides a systematic approach to managing external libraries which might be leveraged by CiviCRM. In addition to performance, there may be other advantages to this approach. These are detailed on the Libraries API project page.

Thoughts?

Donald Lobo · December 04, 2010, 02:38:48 pm

I think this primarily applies to only one drupal url: admin/build/modules (where the directory structure is recursively traversed), and most folks dont do there a lot. however this will potentially complicate the civicrm install and upgrade scripts

would be great if you can investigate and check the viability both from an install and upgrade perspective.

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: Move third-party libraries out of the Drupal module directory? (Read 1252 times)

TallDavid

Move third-party libraries out of the Drupal module directory?

Donald Lobo

Re: Move third-party libraries out of the Drupal module directory?