I've created this PR because i had problems running yarn run webpack after yarn install --production was executed. Now is able to run yarn run webpack in all environments "dev" & "prod" avoiding the dependencies requirements problems.

This ensures best practice of commiting the composer.lock file otherwise every installation of the project can result on a different set of dependencies.

I'm not sure if the right branch is master but I can update the fix if any other branch is desired instead.

The DirectoryIndex app.php in the .htaccess file requires the dir mod, without the mod you get an Error 500.

There is also an issue with the es docker, or a missing config on the fpm docker for the xpack installed by default that needs fixing.

This is already what akeneo/pim-community-dev accepts, so no BC-break.

Setting PHP to 7.2 and more can lead to confusion if people try to install it, assuming it can work with PHP 7.3 or 7.4, when it doesn't and is not even installable.

This already leads to a mistake on Bitnami setup: they seems to propose Akeneo 3.2 with PHP 7.3, and of course it doesn't work. A discussion was started about that on SUG.

My PHP 7.1 executable is named php7.1, not php, which is my 7.0 version.

Use instead @php in the composer.json scripts to use the same executable as the one is currently running

This PR comes from @masmlar in the repository https://github.com/akeneo/pim-community-dev The file has moved in the next branches, so we have to bring back here.

Complete description of the PR here : https://github.com/akeneo/pim-community-dev/pull/5159

| Q | A | | --- | --- | | Review and 2 GTM | No |

This PR add missing lines in the web/app.php file that we forgot to add when we upgrade from sf2.3 to sf2.7. If this line is not added it doesn't work with the APC cache.

A side note: When reading the Upgrade document in the pim-community-standard repository, the first section "Catalog Bundle & Component" may be misleading: It talks about the files in pim-community-dev like f.ex. the config.yml which have a different content than described in the pim-community-standard repository.

In order to not have anymore to move and adapt migration scripts from dev to std for each releases, we decided to create a pre-update-cmd script for composer which will copy upgrades/ folder from dev to std. So we have to repatriate all the upgrades/ folder in dev. Then, do the composer script in the dev version. Linked to : https://github.com/akeneo/pim-community-dev/pull/3955

Fixes cases where product normalized values are not sync with the file info table:

db.pim_catalog_product.aggregate([
    {$match: {_id: ObjectId("55d3ef54db4c5dda148d2d82")}}, 
    {$unwind: "$values"}, 
    {$match: {"values.media": {$exists: true}}}, 
    {$project: {"values": 1, "normalizedData.image": 1}}
]).pretty();

{
    "_id" : ObjectId("55d3ef54db4c5dda148d2d82"),
    "normalizedData" : {
        "image" : {
            "id" : NumberLong(1658),
            "key" : "e/9/6/1/e96189b7afd9f923ef81fe712e24d717113a9935_55d3ef51eaaed_ruk901r600ww00_image___1439952721_zf_r600_glam.jpg",
            "originalFilename" : "zf-r600-glam.jpg"
        }
    },
    "values" : {
        "_id" : ObjectId("55d3ef54db4c5dda148d2d99"),
        "assetIds" : [ ],
        "attribute" : NumberLong(421),
        "entity" : DBRef("pim_catalog_product", ObjectId("55d3ef54db4c5dda148d2d82"), "hills_sit_test"),
        "media" : NumberLong(1658),
        "optionIds" : [ ],
        "prices" : [ ]
    }
}

mysql> select * from akeneo_file_storage_file_info where id = 1658\G;
*************************** 1. row ***************************
               id: 1658
         file_key: 3/2/8/f/328f15d3cf9a34a9e1da6fb59f640fbf8b27af8e_55d3ef51eaaed_ruk901r600ww00_image___1439952721_zf_r600_glam.jpg
original_filename: 55d3ef51eaaed-ruk901r600ww00-image---1439952721-zf-r600-glam.jpg
        mime_type: image/jpeg
             size: 145895
        extension: jpg
             hash: 92c0df558c7eb059aacce43bc783daddcd2918c5
          storage: catalogStorage
1 row in set (0.00 sec)

running vendor/akeneo/pim-community-dev/std-build/install-required-files.sh on post-create-project-cmd will break composer create-project --no-install.

https://getcomposer.org/doc/03-cli.md#create-project

running scripts with create-project should only occur if they are already present with the composer.json files main project, without dependencies.

this patch will allow for:

1. composer create-project & later composer update
2. composer create-project --no-install & later composer install & later composer update

CI might need changes, but docs otherwise should not need changes because create-project by default does install.