Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Translation Translation
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • DevelopmentDevelopment
  • TranslationTranslation
  • Issues
  • #30
Closed
Open
Issue created Sep 09, 2019 by homotechsual@homotechsualDeveloper

Allow setting a custom L10n/I18n resource directory

CiviCRM Core contains some code which gets the resource directory for i18n files - at the moment this is set as a "static variable" within the function here.

It would be beneficial if we could set this properly to a directory of our choosing and would allow proper I18n support on Drupal 8 without having to place the L10n folder inside /vendor/civicrm/civicrm-core which complicates composer updates, completely breaks with composer best practices and adds an additional manual step to get going with CiviCRM and Drupal 8.

Allowing a custom setting for this would also allow us to set a sane default ([civicrm.files]/l10n)? which we can then use to "composerify" the inclusion of the L10n tarball (e.g: https://github.com/drupal-composer/drupal-l10n)

Edited Sep 28, 2019 by homotechsual
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking