Installation Guide issueshttps://lab.civicrm.org/documentation/docs/installation/-/issues2024-01-19T16:55:52Zhttps://lab.civicrm.org/documentation/docs/installation/-/issues/24Outdated advice on MYSQL authentication method2024-01-19T16:55:52ZMichael McAndrewOutdated advice on MYSQL authentication methodThe installation guide says:
> * In MySQL 8 the default authentication plugin changes from `mysql_native_password` to `caching_sha2_password`. This may cause issues with your PHP layer. Fortunately you can revert this change by specifyi...The installation guide says:
> * In MySQL 8 the default authentication plugin changes from `mysql_native_password` to `caching_sha2_password`. This may cause issues with your PHP layer. Fortunately you can revert this change by specifying your chosen authentication plugin in your MySQL configuration:
>
> `[mysqld] default_authentication_plugin=mysql_native_password`
This text was introduced 3 years ago. It doesn't specify what the issue is but think it is probably out of date now since according to https://stackoverflow.com/questions/59231143/does-mysqli-have-support-for-caching-sha2-password-in-php-7-4 PHP 7.4 supports `caching_sha2_password` and we currently recommend PHP 8.1 or 8.2.
Given than 'mysql_native_password' is deprecated and will be removed in a future release of MySQL I think we should remove this text.https://lab.civicrm.org/documentation/docs/installation/-/issues/23Update end of life status of CMS2024-01-10T19:20:34Zjofranzfranz@systopia.deUpdate end of life status of CMShttps://docs.civicrm.org/installation/en/latest/drupal/#drupal9-download
@dvhirst Another suggestion for a smaller thing to fix. Make sure to assign yourself to the issue if you are planning to work on it. It would kind of be a plus to ...https://docs.civicrm.org/installation/en/latest/drupal/#drupal9-download
@dvhirst Another suggestion for a smaller thing to fix. Make sure to assign yourself to the issue if you are planning to work on it. It would kind of be a plus to note all these upcoming end of dates into a wiki or calendar
Sources:
- https://endoflife.date/drupal /joomla and so on..
- https://endoflife.date/drupal
- https://www.drupal.org/docs/getting-started/system-requirements/php-requirements
- https://hugovk.github.io/drupal-release-cycle/major.htmlhttps://lab.civicrm.org/documentation/docs/installation/-/issues/21Composer 2.x?2023-11-08T06:24:24ZEloiComposer 2.x?All of the installation instructions are in composer 1.x format, which is not useable if composer 2.x is installed.
Can we add 2.x syntax instructions (eg. "composer require civicrm/civicrm-core:~5.66 civicrm/civicrm-packages:~5.66 c...All of the installation instructions are in composer 1.x format, which is not useable if composer 2.x is installed.
Can we add 2.x syntax instructions (eg. "composer require civicrm/civicrm-core:~5.66 civicrm/civicrm-packages:~5.66 civicrm/civicrm-drupal-8:~5.66"), or is it required that everyone uses 1.x for some reason?https://lab.civicrm.org/documentation/docs/installation/-/issues/20Disable SQL mode `ONLY_FULL_GROUP_BY`2023-10-22T12:38:20ZfkohrtDisable SQL mode `ONLY_FULL_GROUP_BY`The documentation currently [recommends](https://docs.civicrm.org/installation/en/latest/general/requirements/#mysql-configuration) to disable the SQL mode `ONLY_FULL_GROUP_BY` via the following command:
```sql
SET GLOBAL sql_mode=(SELE...The documentation currently [recommends](https://docs.civicrm.org/installation/en/latest/general/requirements/#mysql-configuration) to disable the SQL mode `ONLY_FULL_GROUP_BY` via the following command:
```sql
SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY',''));
```
I have two issues with that:
1. For some reasons, it doesn't work for me, i.e. even afterwards `SELECT @@sql_mode;` shows `ONLY_FULL_GROUP_BY`.
2. According to the [linked StackOverflow answer](https://stackoverflow.com/a/36033983/895563), shouldn't it rather be `SET PERSIST sql_mode=(SELECT REPLACE(@@sql_mode,'ONLY_FULL_GROUP_BY',''));` in order to persist restarts?https://lab.civicrm.org/documentation/docs/installation/-/issues/19Update to Drupal 10 on Drupal Installation Guide (or remove 9?)2023-11-07T10:11:32ZresgaUpdate to Drupal 10 on Drupal Installation Guide (or remove 9?)Drupal 9 reaches End Of Life November 2023, [How long will Drupal 9 be supported?](https://www.drupal.org/docs/understanding-drupal/drupal-9-release-date-and-what-it-means/how-long-will-drupal-9-be-supported)
Perhaps the section at the ...Drupal 9 reaches End Of Life November 2023, [How long will Drupal 9 be supported?](https://www.drupal.org/docs/understanding-drupal/drupal-9-release-date-and-what-it-means/how-long-will-drupal-9-be-supported)
Perhaps the section at the top for the latest Drupal release (Drupal 10+) could be updated to just use "Drupal" on the Drupal Installation Guide page? https://docs.civicrm.org/installation/en/latest/drupal/
At a minimum, "Drupal 9" should be updated to "Drupal 10".https://lab.civicrm.org/documentation/docs/installation/-/issues/17It seems CV is well installed using composer2022-10-24T16:26:16ZcalbasiIt seems CV is well installed using composerIf confirmed, this warning should be removed:
https://docs.civicrm.org/installation/en/latest/drupal/#installing-commandline
Add cv to your Drupal 9 Site with: composer require civicrm/cv (composer installs of cv are currently broken f...If confirmed, this warning should be removed:
https://docs.civicrm.org/installation/en/latest/drupal/#installing-commandline
Add cv to your Drupal 9 Site with: composer require civicrm/cv (composer installs of cv are currently broken for now use the manual install steps.)https://lab.civicrm.org/documentation/docs/installation/-/issues/13Can't install CiviCRM in Drupal 9 with Composer if Drush is installed2022-11-18T11:03:02ZresgaCan't install CiviCRM in Drupal 9 with Composer if Drush is installedOne of the first things I do when starting a new Drupal 9 site, is adding Drush with Composer to be able to install Drupal.
Following the very detailed and thorough documentation page [Install CiviCRM on Drupal 8/9](https://docs.civicrm...One of the first things I do when starting a new Drupal 9 site, is adding Drush with Composer to be able to install Drupal.
Following the very detailed and thorough documentation page [Install CiviCRM on Drupal 8/9](https://docs.civicrm.org/installation/en/latest/drupal8/), I get a "Your requirements could not be resolved" error:
```
$ composer create-project drupal/recommended-project
$ cd recommended-project
$ lando init --source cwd --recipe drupal9 --webroot web --name drupal9
$ lando start
$ lando composer require drush/drush
$ lando composer config extra.enable-patching true
$ lando composer config minimum-stability dev
$ lando composer require civicrm/civicrm-{core,packages,drupal-8}
Using version ^5.44 for civicrm/civicrm-core
Using version ^5.44 for civicrm/civicrm-packages
Using version ^5.44 for civicrm/civicrm-drupal-8
./composer.json has been updated
Running composer update civicrm/civicrm-core civicrm/civicrm-packages civicrm/civicrm-drupal-8
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- civicrm/civicrm-core[5.44.0, ..., 5.45.x-dev] require symfony/finder ~3.0 || ~4.4 -> found symfony/finder[v3.0.0-BETA1, ..., 3.4.x-dev, v4.4.0-BETA1, ..., 4.4.x-dev] but the package is fixed to v5.4.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires civicrm/civicrm-core ^5.44 -> satisfiable by civicrm/civicrm-core[5.44.0, 5.44.x-dev, 5.45.x-dev].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
```
If I remove Drush with `lando composer remove drush/drush` and run the command again, CiviCRM is installed as expected. Also, if I add Drush after an older CiviCRM version has been installed (for example `5.42`) I can still update to the latest version, `5.44`. So it seems like Drush locks some version constraints too tightly, if it is installed first.https://lab.civicrm.org/documentation/docs/installation/-/issues/12Multi-Site Docs for WordPress need updating2021-08-22T14:59:58ZkcristianoMulti-Site Docs for WordPress need updatingThe docs at https://lab.civicrm.org/documentation/docs/installation/-/blob/master/docs/multisite/wordpress.md need to be updated as they do not work in many cases. They may work if the configuration is an exact copy of the docs, but ev...The docs at https://lab.civicrm.org/documentation/docs/installation/-/blob/master/docs/multisite/wordpress.md need to be updated as they do not work in many cases. They may work if the configuration is an exact copy of the docs, but even that has failed when I tested.
I have a WIP document: https://lab.civicrm.org/kcristiano/installation/-/blob/master/docs/wordpress/cvms/WordPress-Multisite-CiviCRM-Multi-Domain.md
This has been working for me when I create sites, both subdirectory and sub-domain. Domain mapping can also be done with this doc.
I need to clean it up and get it ready for merge. Adding issue here so that it is referenced while I get the PR ready.https://lab.civicrm.org/documentation/docs/installation/-/issues/10Installation documentation is currently COMPLETELY missing any information ab...2023-01-10T10:11:43Znorman.catesInstallation documentation is currently COMPLETELY missing any information about how to install the internationalisation filesWhen we go to get information on how to install the internationalisation compressed file, we are directed to:
https://docs.civicrm.org/installation/en/latest/general/i18n_l10n/
Which only says "This page is a placeholder for content be...When we go to get information on how to install the internationalisation compressed file, we are directed to:
https://docs.civicrm.org/installation/en/latest/general/i18n_l10n/
Which only says "This page is a placeholder for content being migrated in from the old Wiki."
IIRC correctly, the last time I was working with CiviCRM, the information on how to install the internationalisation files was wrong. It described the wrong folder structure. At least, for Wordpress.
I appreciate that putting wrong information up is frustrating to users, but having NO information on how to do it is even worse.
Can that information at least be copied and pasted across?
Otherwise.... no real idea where things need to gojustinfreeman (Agileware)justinfreeman (Agileware)https://lab.civicrm.org/documentation/docs/installation/-/issues/6further mysql config requirement for utf8mb4 compatibility?2020-11-22T20:57:13Zufundofurther mysql config requirement for utf8mb4 compatibility?Hi,
The innodb_ directives listed in this section for utf8mb4 compatibility weren't enough for me today:
https://docs.civicrm.org/installation/en/latest/general/requirements/#mysql-configuration
I needed the following additional optio...Hi,
The innodb_ directives listed in this section for utf8mb4 compatibility weren't enough for me today:
https://docs.civicrm.org/installation/en/latest/general/requirements/#mysql-configuration
I needed the following additional option to avoid key length limit errors when installing extensions on fresh mariadb Ver 15.1 Distrib 10.1.47-MariaDB:
`innodb_default_row_format = 'DYNAMIC'`
I don't know if this should be a requirement, or the issue is with the extensions. But maybe it could be added here?
Thanks :)https://lab.civicrm.org/documentation/docs/installation/-/issues/5Drupal 8/9 composer versioning2020-10-28T23:34:14Zluke.stewartDrupal 8/9 composer versioningIs it worth updating the composer version to not use the approximate flag.
This would make it harder to unintentionally trigger a civicrm upgrade without intending to.
Alternatively include a note explaining that this can happen under ...Is it worth updating the composer version to not use the approximate flag.
This would make it harder to unintentionally trigger a civicrm upgrade without intending to.
Alternatively include a note explaining that this can happen under some (admittedly uncommon/more extreme workflows). -> anything requiring the removal of composer.lock.https://lab.civicrm.org/documentation/docs/installation/-/issues/4D8/D9: Improve recommended l10n process2022-10-24T15:04:19ZtottenD8/D9: Improve recommended l10n process(Prompted by the discussion in https://lab.civicrm.org/documentation/docs/sysadmin/-/merge_requests/274)
On the D8/D9 install docs, there are red boxes and the workflow is awkward (e.g. manually re-download and sync files after every up...(Prompted by the discussion in https://lab.civicrm.org/documentation/docs/sysadmin/-/merge_requests/274)
On the D8/D9 install docs, there are red boxes and the workflow is awkward (e.g. manually re-download and sync files after every upgrade?!).
Unorganized braindumps:
(1) A slightly better workflow (which doesn't require patches or manual reinstalls) is to put this in the top-level `composer.json`:
```javascript
"extra": {
"downloads": {
"civi-l10n": {
"path": "vendor/civicrm/civicrm-core/l10n",
"url": "https://download.civicrm.org/civicrm-l10n-core/archives/civicrm-l10n-daily.tar.gz"
}
}
}
```
The only problem... it may cache the daily snapshot indefinitely. I guess you could add a nonce to the URL.
I almost did this for `civicrm_download_composer_d8()` but wasn't sure how to make that change in `composer.json` via bash. It'd be prettier with a CLI one-liner (`composer require foo...` or `composer download foo...`)
(2) Using the `civicrm-X.Y.Z-l10n.tar.gz` would require patches somewhere b/c the paths don't match-up right.
(3) The steps about sync'ing SQL files aren't needed. With civicrm-setup and CLI usage, it gets translations direct from `l10n/**.mo` files. (There are other use-cases which hit those SQL files - but if you use any of the current documented installers for Civi-D8/D9, they're not needed.)
(4) If there were an identifiable package (`composer require civicrm/l10n`):
* Then we could update `civicrm-asset-plugin` to wire it up. (To wit: if `civicrm/l10n` is installed, then `vendor/composer/autoload_civicrm_asset.php` could set `$civicrm_paths['civicrm.l10n']...`. Same as it does for `civicrm.packages`)
* Publishing a `civicrm/l10n` package from `lab.civicrm.org` would work - but may download slow per https://github.com/composer/packagist/issues/1126. But if the same were on Github, it should perform work alright.https://lab.civicrm.org/documentation/docs/installation/-/issues/3Styling of collapsed sections leads to not seeing they have useful info somet...2020-10-15T09:21:52ZDaveDStyling of collapsed sections leads to not seeing they have useful info sometimesSome of the collapsed accordions don't give the right user experience. I tried fiddling with the look but haven't got a complete look yet. The styling (a) has the chevron way off to the right outside your peripheral vision whereas normal...Some of the collapsed accordions don't give the right user experience. I tried fiddling with the look but haven't got a complete look yet. The styling (a) has the chevron way off to the right outside your peripheral vision whereas normally twisties are on the left, and (b) it's not obvious it's clickable, and (c) it looks like a heading. If there's a couple in a row with no text between it's not too bad, but for example this looks like a heading for the text below it, whereas there's really a whole bunch of info inside:
![Untitled](/uploads/5d689d65df3bab04dae32fbe431511d0/Untitled.gif)https://lab.civicrm.org/documentation/docs/installation/-/issues/1Illustrate clearly the required directory structures for each CMS.2023-01-09T10:38:55ZhomotechsualIllustrate clearly the required directory structures for each CMS.To prevent mis-named folders etc we should be clearer what directory structure is expected for each CMS.To prevent mis-named folders etc we should be clearer what directory structure is expected for each CMS.