docs/backdrop/index.md

@@ -5,9 +5,13 @@
     1. [Install Backdrop](https://backdropcms.org/installation), and...
     1. [Review the CiviCRM requirements](../general/requirements.md)
 
+???+ tldr "Migrating from Drupal 7"?
+
+    If you are migrating to Backdrop from Drupal 7, see [Switch from Drupal to Backdrop](https://docs.civicrm.org/sysadmin/en/latest/misc/switching-cms/drupal-to-backdrop/) in the [System Administrator Guide](https://docs.civicrm.org/sysadmin/en/latest).
+
 ??? tldr "Alternative: Civibuild for developers"
 
-    If you plan to develop patches for CiviCRM on WordPress, then please read the [Developer Guide](https://docs.civicrm.org/dev/en/latest) for information about [Buildkit](https://docs.civicrm.org/dev/en/latest/tools/buildkit/) and [civibuild](https://docs.civicrm.org/dev/en/latest/tools/civibuild/).
+    If you plan to develop patches for CiviCRM on Backdrop, then please read the [Developer Guide](https://docs.civicrm.org/dev/en/latest) for information about [Buildkit](https://docs.civicrm.org/dev/en/latest/tools/buildkit/) and [civibuild](https://docs.civicrm.org/dev/en/latest/tools/civibuild/).
 
 <a name="directory"></a><!-- old anchor -->
 ## Get the code {:#download}
@@ -158,9 +162,9 @@ There should now be a **CiviCRM** link in your Backdrop menu. Click that link an
 
 If your MySQL database is hosted on a different machine than your web server, or if your host requires it, you can use TLS to encrypt the connection between the database and the web server.
 
-Full instructions on installing drupal are out of scope for this guide, but one method is to install into a test database first without MySQL encryption and then move the database to the live server and update settings.php to enable MySQL encryption.
+Full instructions on installing Backdrop are out of scope for this guide, but one method is to install into a test database first without MySQL encryption and then move the database to the live server and update settings.php to enable MySQL encryption.
 
-See [TLS for MySQL](../general/mysql_tls.md) for introductory concepts and the settings for the CiviCRM database. For the Drupal database you have several options for updating settings.php:
+See [TLS for MySQL](../general/mysql_tls.md) for introductory concepts and the settings for the CiviCRM database. For the Backdrop database you have several options for updating settings.php:
 
 1. The simplest, which doesn't require a client certificate, but doesn't verify the server certificate.
 
@@ -170,7 +174,7 @@ See [TLS for MySQL](../general/mysql_tls.md) for introductory concepts and the s
       array (
         'default' =>
         array (
-          'database' => 'drupal',
+          'database' => 'backdrop',
           'username' => 'dbuser',
           'password' => 'dbpassword',
           'host' => 'db435.examplehost.com',

docs/drupal7/index.md → docs/drupal/index.md

 ???+ tldr "About this document"
 
-    This guide covers standard installation of CiviCRM on an existing Drupal 7 site. It assumes that you previously completed these tasks:
+    CiviCRM follows the Drupal community's decisions around which versions of Drupal receive support. Drupal 8 and 9 are no longer supported, but Drupal 7 until Jan 5, 2025 and Drupal 10 are supported.
 
-    1. [Install Drupal 7](https://www.drupal.org/docs/7/install), and...
-    1. [Review the CiviCRM requirements](../general/requirements.md)
+    This guide covers standard installation of CiviCRM on an existing Drupal site. Before starting, you must have completed these tasks:
 
-??? tldr "Alternative: Civibuild for developers"
+    1. [Installed Drupal](https://www.drupal.org/docs/installing-drupal) and...
+    1. [Reviewed the CiviCRM requirements](../general/requirements.md)
 
-    If you plan to develop patches for CiviCRM on Drupal 7, then please use the [Developer Guide](https://docs.civicrm.org/dev/en/latest) for information about [Buildkit](https://docs.civicrm.org/dev/en/latest/tools/buildkit/) and [civibuild](https://docs.civicrm.org/dev/en/latest/tools/civibuild/).
+## Get the code for Drupal 10 {:#drupal10-download}
 
-<a name="directory"></a><!-- old anchor -->
-## Get the code {:#download}
+Drupal 10 sites are typically administered with [Composer](https://getcomposer.org). Composer is a *dependency management* tool which can add, upgrade and remove software *packages* for your site.
+
+If `composer` is properly installed, then these example commands will add latest CiviCRM version to D10:
+
+```
+cd /var/www/d10.example.org
+composer config extra.enable-patching true
+composer require civicrm/civicrm-{core,packages,drupal-8}
+composer require civicrm/cli-tools
+```
+
+??? info "More detail: Enable patching"
+
+    A handful of packages used by CiviCRM require extra patch-files.
+
+    This is possible with the popular [cweagans/composer-patches](https://github.com/cweagans/composer-patches)
+    plugin. However, you must [opt-in to enable it](https://github.com/cweagans/composer-patches#allowing-patches-to-be-applied-from-dependencies).
+
+### Install CiviCRM without any translations {#drupal10-installation}
+
+To install CiviCRM without any translations we use the command line tool `cv` and we assume you already have an empty database.
+
+Change the following in the command below:
+
+* `https://d10.example.org` change this to your civicrm url
+* `database_user` change this to your database user
+* `database_pass` change this to the password of your database user
+* `civicrm_database` change this to name of your civicrm database
+
+```
+cv core:install --cms-base-url="https://d10.example.org" --db="mysql://database_user:database_pass@localhost:3306/civicrm_database"
+```
+
+### Install a translated CiviCRM {:#drupal10-i18n}
+
+To install a translated CiviCRM on Drupal 10 requires an additional step to download the translation files.
+
+Change the following in the command below:
+
+* `nl_NL` to your language, e.g. fr_FR, or nl_BE etc...
+* `https://d10.example.org` change this to your civicrm url
+* `database_user` change this to your database user
+* `database_pass` change this to the password of your database user
+* `civicrm_database` change this to name of your civicrm database
+
+```
+mkdir -p web/sites/default/files/civicrm/l10n/nl_NL/LC_MESSAGES
+curl -Lss -o web/sites/default/files/civicrm/l10n/nl_NL/LC_MESSAGES/civicrm.mo https://download.civicrm.org/civicrm-l10n-core/mo/nl_NL/civicrm.mo
+export CIVICRM_L10N_BASEDIR=/var/www/d10.example.org/web/sites/default/files/civicrm/l10n
+cv core:install --cms-base-url="https://d10.example.org" --db="mysql://database_user:database_pass@localhost:3306/civicrm_database" --lang="nl_NL"
+```
+
+
+## Get the code for Drupal 7 {:#drupal7-download}
 
 The [CiviCRM download page](https://civicrm.org/download) provides a pre-built archive for use with Drupal 7.  A
 typical archive file is ~20mb and looks like `civicrm-X.Y.Z-drupal.tar.gz`. It contains a folder named `civicrm/`.
@@ -78,11 +130,11 @@ In all cases, the final outcome should be the creation of a new folder
 DRUPAL_ROOT/sites/all/modules/civicrm
 ```
 
-## Get the translations {:#i18n}
+### Get the translations for Drupal 7 {:#drupal7-i18n}
 
 The basic CiviCRM release includes support for US English (`en_US`). To use another language or dialect, please [download and extract the translation files](../general/i18n_l10n.md).
 
-## Run the installer {:#installer}
+### Run the installer for Drupal 7 {:#drupal7-installer}
 
 The installer verifies requirements, prepares the database, and initializes the configuration file. You may run the installer through the web interface (*which is simpler*) or the command-line interface (*which has more options*).
 
@@ -108,10 +160,18 @@ The installer verifies requirements, prepares the database, and initializes the
 
     CiviCRM has a command-line administration tool, `cv`, which can perform installation. For details, see [command-line installer](../general/cli-cv.md).
 
+# Troubleshooting {:#troubleshooting}
+
+* Review the [Troubleshooting](../general/troubleshooting.md) page for help with problems you may encounter during the installation.
+
+# Post-installation {:#post-install}
+
+Recommended steps to perform after installing CiviCRM on Drupal.
+
 ## Review the permissions {:#permissions}
 
-!!! check ""
-    Note that Drupal tries to create the `/files/` directory (and make it writeable), but only when saving `admin/settings`. Same holds for `/temp` directory, and a `/uploads/` directory in the CiviCRM module root. On a brand-new Drupal install, this directory may be missing. Even on an existing installation, if file permissions are not set properly, the directory may be missing. If enabling the **CiviCRM** module generates errors regarding the files directory, you must create it (writeable) manually.
+!!! note ""
+    Drupal will create the `/files/` directory (and make it writeable), but only when saving `admin/settings`. Same holds for `/temp` directory, and a `/uploads/` directory in the CiviCRM module root. On a brand-new Drupal install, this directory may be missing. Even on an existing installation, if file permissions are not set properly, the directory may be missing. If enabling the **CiviCRM** module generates errors regarding the files directory, you must create it (writeable) manually.
 
 * Go to the CiviCRM dashboard to see the CiviCRM menus:
 `https://example.org/civicrm` (or `https://example.org/index.php?q=civicrm` if you don't have Clean URLs enabled)
@@ -119,6 +179,7 @@ The installer verifies requirements, prepares the database, and initializes the
 * Go to **Administer » User management » Permissions**
 
 * Verify that the Roles that you want to have access to CiviCRM have the appropriate permissions checked. CiviCRM is installed with a number of fixed permissions (such as "edit contacts" and "administer CiviCRM").
+
 <!-- markdownlint-disable MD046 -->
 !!! tip "Permissions for the Anonymous Role"
     Many sites want anonymous visitors to have access to certain CiviCRM functionality. These permissions are enabled during installation for the Anonymous role. You should review them and modify if needed based on your requirements:
@@ -146,7 +207,7 @@ When CiviCRM is installed on top of an existing Drupal site, a special CiviCRM A
 
 ## Review the checklist {:#checklist}
 
-The **Configuration Checklist** provides a convenient way to work through the settings that need to be reviewed and configured for a new site. You can link to this checklist from the installation success page AND you can visit it at any time from **Administer** » **Administration Console** » **Configuration Checklist**.
+The **Configuration Checklist** provides a convenient way to work through the settings that need to be reviewed and configured for a new site. You can link to this checklist from the installation success page and you can visit it at any time from **Administer** » **Administration Console** » **Configuration Checklist**.
 
 ## Test-drive CiviCRM {:#test-drive}
 
@@ -225,7 +286,13 @@ See [TLS for MySQL](../general/mysql_tls.md) for introductory concepts and the s
     ),
     ```
 
-### Troubleshooting {:#troubleshooting}
+### Integration modules {:#integration-modules}
 
-* Review the [Troubleshooting](../general/troubleshooting.md) page for help with problems you may encounter during the installation.
-* To check compatibility with other Drupal modules see: [Drupal modules incompatible with CiviCRM](https://docs.civicrm.org/sysadmin/en/latest/integration/drupal/incompatibilities/)
+__Webform CiviCRM module__
+
+* [Webform project page on drupal.org](https://www.drupal.org/project/webform_civicrm)
+* [Webform documentation on civicrm.org](https://docs.civicrm.org/webform-civicrm/en/latest)
+
+__CiviCRM Entity module__
+
+* [Project page on Drupal.org](https://www.drupal.org/project/civicrm_entity)

docs/general/cli-cv.md

@@ -6,7 +6,7 @@
 
     1. Install a supported CMS
     1. [Review the CiviCRM requirements](../general/requirements.md)
-    1. Download the CiviCRM code. (See "*Get the code*" for [Backdrop](../backdrop/index.md#download), [Drupal 7](../drupal7/index.md#download), [Drupal 8](../drupal8/index.md#download), [Drupal 9](../drupal8/index.md#download), or [WordPress](../wordpress/index.md#download)).
+    1. Download the CiviCRM code. (See "*Get the code*" for [Backdrop](../backdrop/index.md#download), [WordPress](../wordpress/index.md#download) or [Drupal](../drupal/index.md)).
 
 ??? tldr "Limitations"
 
@@ -120,6 +120,17 @@ There are several available options for the installer. Expand the topics below f
 
     __Note__: At time of writing, the sample data is only supported in the default locale, `en_US`.
 
+??? info "Option: Admin User (Standalone)"
+
+    ```
+    cv core:install ... -m extras.adminUser=USERNAME \
+      -m extras.adminPass=SECRET \
+      -m extras.adminEmail=ME@EXAMPLE.COM
+    ```
+
+    When installing CiviCRM Standalone, you should specify the credentials for the first administrative user.
+    If omitted, the credentials will be auto-generated and stored in the CiviCRM log.
+
 ??? info "Option: Verbose output"
 
     ```bash
@@ -158,6 +169,9 @@ The installer may report a problem. Some common ones are:
     The PHP or MySQL configuration may require an update - e.g. to expand the PHP memory limit, to enable a PHP extension, or to enlarge a MySQL buffer.
     Common issues are discussed in the [Requirements](requirements.md).
 
+??? "Error: Call to undefined method Drupal::entityManager"
+    This error appears installing with the `--user` option under Drupal 9. Avoid this error simply by not using the `--user` option.
+
 For common problems, you can simply fix the problem and re-run the installer.
 
 For unusual problems, be sure to enable verbose output (`-v` or `-vv`). It may also help to [inspect the model, plugins, or requirements](https://docs.civicrm.org/dev/en/latest/framework/setup/getting-started/).

docs/general/i18n_l10n.md

-## Coming Soon
+## Using CivCRM in a language other than US-English
+
+CiviCRM uses US English by default but supports translation into a wide range of other languages with varying degrees of completeness.
 
 !!! note ""
-    This page is a placeholder for content being migrated in from the old Wiki.
+    If you want to help out with translations visit the [translation documentation](https://lab.civicrm.org/dev/translation/wikis).
+
+To enable use of CiviCRM in a new language translation you need to
+
+* download the translation files
+* install them in the appropriate directory
+* select the language in the Language settings
+
+The exact instructions on how to download and install the translations files differ between platforms:
+
+* [Backdrop](../backdrop/index.md#i18n)
+* [Drupal 9](../drupal/index.md#drupal9-i18n)
+* [Drupal 7](../drupal/index.md#drupal7-i18n)
+* [Joomla](../joomla/index.md#i18n)
+* [Wordpress](../wordpress/index.md#i18n)
+
+## Changing the default CiviCRM language after installation
+
+Once you have installed the translation files, you can change the language used by CiviCRM:
+
+* Go to **Administer > Localization > Languages, Currency, Location**
+* Select the new default language.
+* Update the default currency, money formatting options, default country, etc.
+
+You will also probably want to update the date and time formats:
+
+* Go to **Administer > Localization > Date Formats**
+
+Finally, you may notice that many other options in CiviCRM will not be correctly translated:
+
+* Individual prefixes (Mrs, M, etc)
+* Gender options (M, F, other)
+* Address Location Types
+* Some fieldsets in the "Edit Contact" screen
+
+These are known in CiviCRM as Option Values, and there are many of these.
+
+To avoid having to change every single setting, you can install the following extension: [fixoptiontranslations](https://lab.civicrm.org/extensions/fixoptiontranslations). Once the extension is enabled, all options will be translated. The extension can then be uninstalled and removed.
+
+## Updating translation files
+
+The easiest way to update your translations regularly is to use the [l10n update](https://github.com/cividesk/com.cividesk.l10n.update/) extension: 
+
+The "l10n update" extension will do a daily check to update the translation files for CiviCRM core, as well as for extensions. Every night, around 2 AM (North American Eastern Time), the CiviCRM website packages updated translation files. These are available at the following address: `https://download.civicrm.org/civicrm-l10n-core/mo/xx_XX/civicrm.mo` where `xx_XX` is an ISO language code corresponding to one CiviCRM has published translations for.
+
+For example, for Spanish CiviCRM core:
+
+```sh
+wget https://download.civicrm.org/civicrm-l10n-core/mo/es_ES/civicrm.mo
+```
+
+For the CDN Tax Receipts extension in Canadian French:
+
+```sh
+wget https://download.civicrm.org/civicrm-l10n-extensions/mo/cdntaxreceipts/fr_CA/cdntaxreceipts.mo
+```
+
+## Storing translation files in another directory
+
+By default, CiviCRM looks in `[civicrm.root]/l10n` for translation files. Since CiviCRM 5.23, there is a new setting available to store those files in another directory. This can be convenient when files are updated regularly, or when using the l10nupdate extension, which requires the files to be web-writable. More information, see [PR15408](https://github.com/civicrm/civicrm-core/pull/15408). As of this writing, this setting only applies to core translations, not extensions.
+
+## Native gettext
+
+`gettext` is the mechanism by which strings are translated. By default, CiviCRM uses the PHP-Gettext implementation. This implementation can cause a 20-30% performance loss.
+
+Since CiviCRM 4.2, it is possible to use native `gettext`. This may require some changes to your hosting environment and is therefore recommended mainly for sites hosted on dedicated environments (VPS or dedicated server, it may not work on shared hosting).
+
+To enable it:
+
+* PHP must have `gettext` support compiled in (it usually is the case, see `phpinfo()` for more information). Debian and Ubuntu include it by default.
+* The operating system must have the locale enabled. For example, on Linux-based systems, this is in `/etc/locale.gen`, or by typing this command:
+
+```sh
+locale -a
+```
+
+Debian/Ubuntu systems can enable locales by typing:
+
+```sh
+dpkg-reconfigure locales
+```
+
+!!! note
+    The "UTF-8" variant of the locale must be enabled. For example: "fr_FR.UTF-8".
+
+Apache or PHP-FPM must be restarted after adding a new locale. Finally, uncomment the following in civicrm.settings.php:
+
+```php
+define('CIVICRM_GETTEXT_NATIVE', 1);
+```

docs/general/troubleshooting.md

@@ -71,14 +71,18 @@ If you get this error on a new Drupal/CiviCRM installation, you may have skipped
 
 If you see this error, you may need to modify the session.save_handler method for your site. Check with your hosting provider for the recommended way to do this.
 
-### WordPress menus are wrong
+### Page doesn't reload and spinner shows when tryibng to re-create triggers, eventually showing "DB Error: unknown error"
 
-Try [rebuilding the WordPress menus](#rebuild-wp-menus).
+There can be multiple reasons for this, but they usually relate to MySQL user or connection issues. Check the MySQL user exists, and that it can log in to the database from the server accessing MySQL with the password in civicrm.settings.php. You may want to check logs then. A solution on some systems with MySQL binary logging is to add log_bin_trust_function_creators = 1 to the mysqld config file.
 
 ### "Your PHP version is missing zip functionality"
 
 If you get this error when installing or upgrading CiviCRM for Joomla, download and use the `civicrm-x.x.x-joomla-alt.zip` package.
 
+### WordPress menus are wrong
+
+Try [rebuilding the WordPress menus](#rebuild-wp-menus).
+
 ## Solutions
 
 ### Cleanup Caches and Update Paths {:#clear-cache}

docs/general/unicode_pdf.md

-# Using non-latin characters in PDF output
+# Using your own font or CJK characters in PDF output
 
-(This does not apply to Drupal 8/9.)
+As of CiviCRM 6.0, most unicode characters will output correctly in PDFs. But if you need CJK characters DejaVu does not contain those, so you will need to install another font file such as SimSun using the steps below.
 
-By default there are certain places in CiviCRM where PDF output does not handle non-latin characters because the unicode font files have been removed from the DOMPDF library. For example CiviCRM uses it when producing PDF copies of CiviReports, but by comparison it uses a different library for Mailing Labels.
+If you are still seeing question marks (?) in place of unicode characters, even for non-CJK characters, check that you don't have a `<font>` tag or `style` attribute in the html specifically setting a font that doesn't support unicode.
 
-Note when testing to see if you've succeeded, use letters that are entirely outside the latin alphabet, e.g. use cyrillic letters. Several letters like `ü` will work either way so aren't a good test.
+## Option A: Using web fonts
 
-??? example "Option A: Install the unicode font files for DOMPDF"
+1. In your html template add a `<link>` tag like the following, e.g. for the Noto Sans SC font: `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Noto+Sans+SC:wght@100..900">`
+1. Specify the font using CSS in the templates where you use the CJK characters. You can use the Source button in CKEditor to do this and type it directly into the HTML: e.g. `<p style="font-family: Noto Sans SC;">的</p>`
 
-    You will need to repeat these steps after each CiviCRM upgrade.
+## Option B: Storing fonts locally
 
-    1. Get the dompdf download zip file from the github repository, e.g. at https://github.com/dompdf/dompdf/releases/tag/v0.8.6.
-      * You might want to use the exact same release (github tag) that core uses. For the font it shouldn't matter, but you can find this number by looking in composer.lock in your civicrm root folder and searching for "dompdf" and look at the "version" field.
-    1. Extract the files and look in the dompdf/lib/fonts folder.
-    1. Copy all the DejaVuSans files over to your `<civicrm_root>/vendor/dompdf/dompdf/lib/fonts` folder.
-    1. Edit the `dompdf_font_family_cache.dist.php` file in the same folder and add these lines:
-    ```php
-    'dejavu sans' =>
-        [
-            'bold' => DOMPDF_DIR . '/lib/fonts/DejaVuSans-Bold',
-            'bold_italic' => DOMPDF_DIR . '/lib/fonts/DejaVuSans-BoldOblique',
-            'italic' => DOMPDF_DIR . '/lib/fonts/DejaVuSans-Oblique',
-            'normal' => DOMPDF_DIR . '/lib/fonts/DejaVuSans'
-        ],
-    'dejavu sans mono' =>
-        [
-            'bold' => DOMPDF_DIR . '/lib/fonts/DejaVuSansMono-Bold',
-            'bold_italic' => DOMPDF_DIR . '/lib/fonts/DejaVuSansMono-BoldOblique',
-            'italic' => DOMPDF_DIR . '/lib/fonts/DejaVuSansMono-Oblique',
-            'normal' => DOMPDF_DIR . '/lib/fonts/DejaVuSansMono'
-        ],
-    'dejavu serif' =>
-        [
-            'bold' => DOMPDF_DIR . '/lib/fonts/DejaVuSerif-Bold',
-            'bold_italic' => DOMPDF_DIR . '/lib/fonts/DejaVuSerif-BoldItalic',
-            'italic' => DOMPDF_DIR . '/lib/fonts/DejaVuSerif-Italic',
-            'normal' => DOMPDF_DIR . '/lib/fonts/DejaVuSerif'
-        ],
+1. While option A will cache a version of the file after the first download, it may not be available on the internet or may be a commercial font.
+1. Create a folder in a location that won't get overwritten when you upgrade, e.g. sites/default/fonts for Drupal.
+1. Copy the .ttf font file you want to use into that folder.
+1. Run `php -r 'require_once "/path/to/civicrm/vendor/autoload.php"; $f = \FontLib\Font::load("/full/path/to/the/ttf/file"); $f->parse(); $f->saveAdobeFontMetrics("/full/path/to/output/ufm/file");'`
+    * e.g. `php -r 'require_once "/var/www/sites/all/modules/civicrm/vendor/autoload.php"; $f = \FontLib\Font::load("/var/www/sites/default/fonts/simsun.ttf"); $f->parse(); $f->saveAdobeFontMetrics("/var/www/sites/default/fonts/simsun.ufm");'`
+1. Create a file in that folder called `installed-fonts.json` that looks like this:
+    ```json
+    {
+        "simsun": {
+            "normal": "simsun"
+        }
+    }
     ```
-
-??? example "Option B: Install wkhtmltopdf instead"
-
-    This may also have an advantage for reports that cause DOMPDF to run out of memory. A possible disadvantage is the output may not be exactly the same or as well tested with CiviCRM as DOMPDF since it is not the default. You only need to do this once.
-
-    1. Your operating system's package manager may already make it available to install. If not then go to https://wkhtmltopdf.org and download the file for your operating system.
-    1. Note the full path to the executable binary.
-    1. In CiviCRM go to Administer - System Settings - Misc.
-    1. A couple lines down there is a setting `Path to wkhtmltopdf executable`.
-    1. Fill it in, e.g. `/usr/local/bin/wkhtmltopdf`
-    1. Click the Save button.
+1. Visit Administer - System Settings - Misc and in the field for DOMPDF Font Folder put the full path to the font folder you created in step 2.
+1. Specify the font using CSS in the templates where you use the CJK characters. You can use the Source button in CKEditor to do this and type it directly into the HTML: e.g. `<p style="font-family: simsun;">的</p>`
+1. Note any fonts you set up here are in addition to the ones distributed with dompdf/CiviCRM. You do not need to copy those core fonts over or add entries in this json file to use them.