Magento2 – How to Apply MDVA-43395_EE_2.4.3-p1_v1.composer.patch

magento2security-patch

I could successfully follow the instructions to install the latest security patches on our Magento store running on community version 2.4.2. I'm not sure if patches really installed well because I find only a few files modified as the screenshot below shows. Kindly confirm if everything went well with the install.

Best Answer

waaaait, do You really keep vendor content in Your project Repo? It is not really a good idea. Vendor catalog should be added to .gtignore. You should manage packages via files compsoer.json and composer.lock. Vendor should be installed on Server with composer install command. In that case adding patches would be super simple - by adding one or two more lines to Your composer.json

HOWEVER, answering Your question, look like Patches were installed correctly. I mean, at least files related to patches were modified.

Related Solutions

Magento – Cannot see any blocks in Magento2

Yes this is expected behaviour.

Your blocks may depend on your theme.

For example if you purchase theme you may see more blocks.

Go ahead and create a block. This block can be imported using widgets in your pages(Home page for example) or even block inside another block.

Thanks

Magento2 Upgrade – How to Upgrade Magento from 2.1 to 2.2.1 with Sample Data Using Composer

Remove Magento 2.1 sample data modules:

bin/magento sampledata:remove

If you recieve an authentication error like this:

[Composer\Downloader\TransportException]                                   

The 'https://repo.magento.com/packages.json' URL required authentication.  
You must be using the interactive console to authenticate

you have to copy your stored credentials for repo.magento.com to var/composer_home because this is the composer home directory for bin/magento commands

cp ~/.composer/auth.json var/composer_home/

Specify new Magento version

For Open Source (CE):

composer require magento/product-community-edition 2.2.1 --no-update

For Commerce (EE):

composer require magento/product-enterprise-edition 2.2.1 --no-update

(Replace 2.2.1 with the current version if there's a newer one)

Update dev requirement versions

This is necessary if you use the testing tools bundled with Magento. The current required versions can be found here: https://github.com/magento/magento2/blob/2.2/composer.json#L76-L82

composer require --dev --no-update \
    phpunit/phpunit ~6.2.0 \
    squizlabs/php_codesniffer 3.0.1 \
    pdepend/pdepend 2.5.0 \
    friendsofphp/php-cs-fixer ~2.1.1 \
    lusitanian/oauth ~0.8.10 \
    sebastian/phpcpd 2.0.4
composer remove --dev --no-update \
    fabpot/php-cs-fixer \
    sjparkinson/static-review

Trigger update
```
composer update
```
Review file permissions

You might need to set the correct file permissions again, for example make bin/magento executable:
```
chmod +x bin/magento
```
And give appropiate write permissions to the new generated directory.

More info: http://devdocs.magento.com/guides/v2.2/install-gde/install/file-sys-perms-over.html

Reinstall sample data

bin/magento sampledata:deploy
bin/magento sampledata:reset

Upgrade database
```
bin/magento setup:upgrade
```
Compilations

If in production mode, also run the following compilation commands:
```
bin/magento setup:di:compile
bin/magento setup:static-content:deploy
```

Best Answer

Related Solutions

Magento – Cannot see any blocks in Magento2

Magento2 Upgrade – How to Upgrade Magento from 2.1 to 2.2.1 with Sample Data Using Composer

Related Topic