Note, I did not bother configuring Elasticsearch during this test because it runs fine out the box. Then went through the motions of installed and running Elasticsearch. Then installed JDK 11 sudo apt install openjdk-11-jdk -y This is because I’m about to download some files. I moved to the Super Admin home directory. But I swapped out the following version numbers (that latest supported version at the time of doing this): Then a quick restart for the changes to take affect sudo systemctl restart apache2Įssentially, I used the documentation from one of my older posts. Then updated the configuration file, changing all 4 values: sudo vi /etc/php/7.4/apache2/php.ini Then switched from PHP 7.3 to 7.4 sudo update-alternatives -config php I installed PHP 7.4 and all required modules sudo apt install php7.4 libapache2-mod-php7.4 php7.4-mysql php7.4-soap php7.4-bcmath php7.4-xml php7.4-mbstring php7.4-gd php7.4-common php7.4-cli php7.4-curl php7.4-intl php7.4-zip php7.4-mbstring php7.4-gettext zip unzip -y Then I had to set the swapfile again (as the this is reset on reboot) sudo fallocate -l 4G /swapfile & sudo chmod 600 /swapfile & sudo mkswap /swapfile & sudo swapon /swapfileĪt this point, Magento 2.3.7-p3 or greater requires composer 2.x. sudo do-release-upgrade -yĪfter the server restarted, I logged in as Admin I did this because I needed access to the latest repositories so that I could install PHP and upgrade MySQL. 2.2 Preparing the work space (again)Įxited from Magento User back to Super Admin exit This was a little more technical, because a variety of applications needed installing/upgrading and configuring (e.g. Now it was time to attempt changing branches. composer require-commerce magento/product-community-edition 2.3.7-p3 -no-update -interactive-root-conflicts This was a really helpful tag and solved many issues. Note the -interactive-root-conflicts tag that I used. Rm -rf var/cache/* var/page_cache/* generated/code/* Then flushed the caches and ran Setup Upgrade redis-cli FLUSHALL ![]() Ran composer update php -d memory_limit=4G /usr/local/bin/composer update However, in one of the steps coming up, I’m forced to downgrade it to 1.0. What’s interesting here is that the Magento Docs state that if you run PHP 7.3 or greater, then you need to install version 2.0 of this module. So, I did it one at a time until no errors display during composer update.Īdded the composer plugin require magento/composer-root-update-plugin ~2.0 -no-update I didn’t want to change everything just in case. So, I referenced composer.json for v2.3 on the Magento GitHub and swapped the version numbers for what I found there. ![]() The reason I determined these 2 files were a problem, was because each time I ran composer update, it would have an issue with these lines. "magento/magento2-functional-testing-framework": "2.3.9", (changed from ^2.7) Manually updateded composer.json due to PHP conflict issues vi composer.json and updated 2 entries. Switched to Magento User and navigated to Magento Root Directoy sudo su magento sudo chown -R magento:apache /var/www/html/ Set a 4G swapfile, because my sandbox server memory isn’t great sudo fallocate -l 4G /swapfile & sudo chmod 600 /swapfile & sudo mkswap /swapfile & sudo swapon /swapfileįigured I’d make sure the Magento folder ownership was correct. Logged in as Super Admin (not magento user) Upgrading Magento 2.3.5 > 2.3.7-p3 1.1 Preparing the work space So rather than jump straight from 2.3.5 to 2.4.4, I’d instead go from 2.3.5 to 2.3.7-p3 to 2.4.4. This time around, I figured I’d tackle the upgrade in stages.
0 Comments
Leave a Reply. |