Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
Drupal
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Development
  • Drupal
  • Issues
  • #129

Closed
Open
Opened Jul 28, 2020 by KarinG@KarinGMaintainer

When creating a D8 private file system e.g. /sites/default/private -> CiviCRM overrides location for templates_c specified in civicrm.settings.php file

Is this intentional? And is it necessary? I first saw this on my Pantheon test install and am now seeing it on one of Alan's hosted sites as well. Storing templates_c in the private file system [even though the civicrm.settings.php file still has the non-public files location] results in a slow page load.

This only happens if you put your private files dir in /sites/default/

On Alan's hosting we can move the private/files to the same level as web/

[$settings['file_private_path'] = $app_root . '/../private/files';

  • so CiviCRM keeps using /sites/default/files for templates_c - but on Pantheon [and likely other hosting] you may not have access to create a dir at that level.

End result is that it creates the impression that CiviCRM on D8 is very slow.

@DaveD @seamuslee @jackrabbithanna @bgm - any ideas as to why/history/intentional?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/drupal#129