<p><a href="https://www.tutlinks.com/how-to-upgrade-php-to-php-8-1/">https://www.tutlinks.com/how-to-upgrade-php-to-php-8-1/</a></p><p>#updatephp #upgradephp #php8 #PHP #owasp #StayConnected #security #howto #savemyday #programming #latest #technology #composer </p>

Learn how to upgrade PHP 5.4 Projects to PHP 8.1

<UL><LI><span>Post author:</span></LI><LI><span>Reading time:</span>9 mins read</LI></UL><p>In this tutorial, you will understand how to upgrade PHP 5.x projects to latest and stable version of PHP 8.1. This post is highly expected to work for all the PHP projects starting 5.x to the 7.x as well as to the current latest stable version PHP 8.1</p><figure><img width="707" height="397" src="https://www.tutlinks.com/wp-content/uploads/2021/12/Learn-how-to-upgrade-PHP-5.4-Projects-to-PHP-8.1-TutLinks-1024x576.png" alt="Learn how to upgrade PHP 5.4 Projects to PHP 8.1 - TutLinks" srcset="https://www.tutlinks.com/wp-content/uploads/2021/12/Learn-how-to-upgrade-PHP-5.4-Projects-to-PHP-8.1-TutLinks-1024x576.png 1024w, https://www.tutlinks.com/wp-content/uploads/2021/12/Learn-how-to-upgrade-PHP-5.4-Projects-to-PHP-8.1-TutLinks-300x169.png 300w, https://www.tutlinks.com/wp-content/uploads/2021/12/Learn-how-to-upgrade-PHP-5.4-Projects-to-PHP-8.1-TutLinks-768x432.png 768w, https://www.tutlinks.com/wp-content/uploads/2021/12/Learn-how-to-upgrade-PHP-5.4-Projects-to-PHP-8.1-TutLinks-1536x864.png 1536w, https://www.tutlinks.com/wp-content/uploads/2021/12/Learn-how-to-upgrade-PHP-5.4-Projects-to-PHP-8.1-TutLinks-2048x1152.png 2048w"><figcaption dir="auto">Learn how to upgrade PHP 5.4 Projects to PHP 8.1 – TutLinks</figcaption></figure><div>
							Table Of Contents						</div><h2>Why procrastinate upgrading PHP?</h2><p>There are might be several small, medium and enterprise level Web Applications that are still running on PHP 5.4. The most not-so-convincing reasons that they are still on out-dated version of PHP could be </p><UL><LI>lack of technical expertise to upgrade PHP to a stable version in a methodical way</LI><LI>lack of understanding of what are all the areas of your legacy code base that your application is spread across</LI><LI>anticipating something will break after upgrading old PHP to latest stable version.</LI></UL><p>There could also be many other reasons, but its time for you to move on. We will now understand the impact of not upgrading to the stable version of PHP.</p><h2>What is the Impact?</h2><p dir="ltr">Upgrading your outdated PHP code to latest stable version will help you keep safe from potential security vulnerabilities creeping in to your application. According to , <a href="https://owasp.org/www-project-top-ten/2017/A9_2017-Using_Components_with_Known_Vulnerabilities" rel="noreferrer noopener" dir="ltr">A9:2017-Using Components with Known Vulnerabilities</a>, your application is vulnerable <em dir="ltr">If software is vulnerable, unsupported, or out of date</em>. It also states that,</p><BLOCKQUOTE><p>If you do not fix or upgrade the underlying platform, frameworks, and dependencies in a risk-based, timely fashion. This commonly happens in environments when patching is a monthly or quarterly task under change control, which leaves organizations open to many days or months of unnecessary exposure to fixed vulnerabilities.</p></BLOCKQUOTE><h2>Take a leap and move forward and upgrade PHP</h2><p>To answer all the aforementioned reasons and refrain from further procrastination, this short and sweet guide will help you to upgrade your PHP application to its latest stable version in a step-by-step approach.</p><p>Using this proven approach of upgrading outdated PHP to latest PHP 8.x version, you will have the following outcome:</p><UL><LI>You will be able to successfully upgrade your PHP 5.x code to stable release of PHP 8.1</LI><LI>The choice of various PHP coding standards you can choose from to upgrade such as<UL><LI>MySource, </LI><LI>PEAR, </LI><LI>PSR1, </LI><LI>PSR12, </LI><LI>PSR2, </LI><LI>Squiz, </LI><LI>Zend and </LI><LI>PHPCompatibility</LI></UL></LI><LI><UL><LI>phpcompatibility/php-compatibility</LI><LI>DealerDirect/phpcodesniffer-composer-installer</LI></UL><UL><LI>higidi/composer-phpcodesniffer-standards-plugin</LI><LI>squizlabs/php_codesniffer</LI></UL></LI><LI>The report that help you identify areas to take actions to quickly fix and regress the functionality</LI><LI>The final report with highly detailed information that includes:<UL><LI>Warnings occurring at each and every line across all files in the project</LI><LI>Erroneous syntax that is incompatible with target version of PHP along with line number, possible suggestion/alternative across all the files in the project</LI></UL></LI></UL><h2>Upgrade PHP 5.4 Projects to PHP 8.1</h2><p>With this pretext, we will proceed our tutorial to understand how to upgrade PHP 5.x project to PHP 8.1 or further future stable versions.</p><h3>Install Composer</h3><p dir="ltr">As an initial setup, we will install composer. <a href="https://getcomposer.org/doc/00-intro.md#installation-linux-unix-macos" rel="noreferrer noopener" dir="ltr">Installing composer on MacOs or *nix platforms is very straight forward</a>. But if you are following this tutorial from a Windows based OS, here is my approach.</p><p>Ensure you have PHP installed and made available as environment variable.</p><p dir="ltr">Follow the <a href="https://getcomposer.org/download/" rel="noreferrer noopener" dir="ltr">command-line installation of Composer for Windows OS</a> as specified on official composer website. Do not install <a href="https://getcomposer.org/Composer-Setup.exe" rel="noreferrer noopener" dir="ltr">Composer-Setup.exe</a>&nbsp;as it never helped me with package management on Windows OS 😅. To install composer via CLI (Command Line Interface), run the following commands from the terminal.</p><div><span>Shell</span></div><div><span>Shell</span></div><div>1</div><PRE><span role="presentation" dir="ltr">vendor\b<span dir="ltr">in</span>\phpcs.bat <span dir="ltr">-p</span> . <span dir="ltr">--standard</span><span dir="ltr">=</span>PHPCompatibility <span dir="ltr">--runtime-set</span> testVersion <span dir="ltr">7</span>.4 <span dir="ltr">--extensions</span><span dir="ltr">=</span>php <span dir="ltr">--ignore</span><span dir="ltr">=</span>*/vendor/* <span dir="ltr">--report-full</span><span dir="ltr">=</span>phpcs.txt</span></PRE><p>Explanation of various attributes</p><UL><LI><code dir="ltr">-p</code>: Indicates the path where to check the compatibility standard. A dot (.) indicates to check the current directory and all the sub directories recursively</LI><LI><code dir="ltr">--standard</code>: Accepts one of the coding standard followed. The common value is one of the available options<UL><LI>MySource</LI><LI>PEAR</LI><LI>PSR1</LI><LI>PSR12</LI><LI>PSR2</LI><LI>Squiz</LI><LI>Zend</LI><LI>PHPCompatibility</LI></UL></LI><LI><code dir="ltr">--runtime-set</code>: Accepts <em dir="ltr">testVersion</em> with the target version we want to test our code compatibility with. In our case we want to test our PHP 5.4 code base and test our code base is compatible when we upgrade our runtime to version PHP 8.1.</LI><LI><code dir="ltr">--extensions</code>: Accepts any file extensions that we want to target for the <code dir="ltr">phpcs</code> routine to test the <em dir="ltr">testVersion</em> compatibility. If you have custom template files with file extension other than <code dir="ltr">php</code> but the are filled with PHP code, then ignore this argument.</LI><LI><code dir="ltr">--ignore</code>: Accepts the directory path to ignore. Typically you may not need vendor directory as you don’t want to touch the code base of third party referenced libraries.</LI><LI><code dir="ltr">--report-full</code>: Accepts text file name to which all the resultant code upgrade analysis is dumped to.</LI></UL><h2>Patience and CPU</h2><p dir="ltr">The <code dir="ltr">phpcs</code> is a CPU intensive operation. It scans each and every line of your repository. When this report is generated on project that has .php 4434 File(s) (included the files in vendor directory but excluded them for compatibility check) the operation took approximately above 65 mins on a PC with 16 GB RAM, i7 processor with 4 CPU cores.  So to speed up memory based operation it is recommended to leave the PC and don’t do any multi tasking.</p><h2>Understanding Report</h2><p dir="ltr">The report will have the file entry only if the <code dir="ltr">phpcs</code> has identified a potential <em dir="ltr">warning </em>or <em dir="ltr">error </em>identified at a particular <em dir="ltr">line number</em> in the <em dir="ltr">php file </em>along with <em dir="ltr">detail</em>. This line level <em dir="ltr">detail</em> has instructions or suggestions on what need to be done to make it compatible with the PHP runtime we are targeting to upgrade our code base to. Other files which pass or succeed through the <code dir="ltr">phpcs</code> scan won’t be added in the report. This means that the files which are not in the report already meet the code compatibility with target version of PHP we are planning to upgrade to.</p><h3>Example of Warning from Report</h3><p>The following snippet of text gives an idea of how a sample would look like in case of warning found in a particular php file.</p><div><span>Plain Text</span></div><div>6</div><PRE><span role="presentation">     |       | invalid and will throw a fatal error since PHP 7.0</span></PRE><div>7</div><PRE><span role="presentation">----------------------------------------------------------------------</span></PRE><p>We see that the error message is so intuitive. Based on such information, we move toward fixing those syntax to be compatible with target version we are trying to comply with. </p><h2>Conclusion</h2><p>Once you are done with all the fixes, you can plan action items to regress in the workflows and functionalities. Thus you will now have a vulnerability free, up-to-date version of PHP that is both latest and stable.</p><p>If you found this tutorial helpful, please do bookmark it 🔖 (Ctrl +D) for your future reference. Also share it with your friends and colleagues who are having trouble to understand how to upgrade their outdated PHP projects to latest and stable PHP 8.x version.</p>

There are might be several small, medium and enterprise level Web Applications that are still running on PHP 5.4. The most not-so-convincing reasons that they are still on out-dated version of PHP could belack of technical expertise to upgrade PHP to a stable version in a methodical waylack of understanding of what are all the areas of your legacy code base that your application is spread acrossanticipating something will break after upgrading old PHP to latest stable version.

In this tutorial, you will understand how to upgrade PHP 5.x projects to latest and stable version of PHP 8.1.

computerscience

Computer Science

<ul><li><span>Post author: </span> </li><li><span>Reading time: </span>9 mins read </li> </ul>

<p>In this tutorial, you will understand how to upgrade PHP 5.x projects to latest and stable version of PHP 8.1. This post is highly expected to work for all the PHP projects starting 5.x to the 7.x as well as to the current latest stable version PHP 8.1 </p>

<p>There are might be several small, medium and enterprise level Web Applications that are still running on PHP 5.4. The most not-so-convincing reasons that they are still on out-dated version of PHP could be </p>

<ul><li>lack of technical expertise to upgrade PHP to a stable version in a methodical way </li><li>lack of understanding of what are all the areas of your legacy code base that your application is spread across </li><li>anticipating something will break after upgrading old PHP to latest stable version. </li> </ul>

<p>There could also be many other reasons, but its time for you to move on. We will now understand the impact of not upgrading to the stable version of PHP. </p>

<p>Upgrading your outdated PHP code to latest stable version will help you keep safe from potential security vulnerabilities creeping in to your application. According to , <a href="https://owasp.org/www-project-top-ten/2017/A9_2017-Using_Components_with_Known_Vulnerabilities">A9:2017-Using Components with Known Vulnerabilities </a>, your application is vulnerable <em>If software is vulnerable, unsupported, or out of date </em>. It also states that, </p>

<p>If you do not fix or upgrade the underlying platform, frameworks, and dependencies in a risk-based, timely fashion. This commonly happens in environments when patching is a monthly or quarterly task under change control, which leaves organizations open to many days or months of unnecessary exposure to fixed vulnerabilities. </p>

Take a leap and move forward and upgrade PHP

<p>To answer all the aforementioned reasons and refrain from further procrastination, this short and sweet guide will help you to upgrade your PHP application to its latest stable version in a step-by-step approach. </p>

<p>Using this proven approach of upgrading outdated PHP to latest PHP 8.x version, you will have the following outcome: </p>

<ul><li>You will be able to successfully upgrade your PHP 5.x code to stable release of PHP 8.1 </li><li>The choice of various PHP coding standards you can choose from to upgrade such as<ul><li>MySource, </li><li>PEAR, </li><li>PSR1, </li><li>PSR12, </li><li>PSR2, </li><li>Squiz, </li><li>Zend and </li><li>PHPCompatibility </li> </ul> </li><li><ul><li>phpcompatibility/php-compatibility </li><li>DealerDirect/phpcodesniffer-composer-installer </li> </ul><ul><li>higidi/composer-phpcodesniffer-standards-plugin </li><li>squizlabs/php_codesniffer </li> </ul> </li><li>The report that help you identify areas to take actions to quickly fix and regress the functionality </li><li>The final report with highly detailed information that includes:<ul><li>Warnings occurring at each and every line across all files in the project </li><li>Erroneous syntax that is incompatible with target version of PHP along with line number, possible suggestion/alternative across all the files in the project </li> </ul> </li> </ul>

<p>With this pretext, we will proceed our tutorial to understand how to upgrade PHP 5.x project to PHP 8.1 or further future stable versions. </p>

<p>As an initial setup, we will install composer. <a href="https://getcomposer.org/doc/00-intro.md#installation-linux-unix-macos">Installing composer on MacOs or *nix platforms is very straight forward </a>. But if you are following this tutorial from a Windows based OS, here is my approach. </p>

<p>Ensure you have PHP installed and made available as environment variable. </p>

<p>Follow the <a href="https://getcomposer.org/download/">command-line installation of Composer for Windows OS </a>as specified on official composer website. Do not install <a href="https://getcomposer.org/Composer-Setup.exe">Composer-Setup.exe </a> as it never helped me with package management on Windows OS 😅. To install composer via CLI (Command Line Interface), run the following commands from the terminal. </p>

<p>Explanation of various attributes </p>

<ul><li><code>-p </code>: Indicates the path where to check the compatibility standard. A dot (.) indicates to check the current directory and all the sub directories recursively </li><li><code>--standard </code>: Accepts one of the coding standard followed. The common value is one of the available options<ul><li>MySource </li><li>PEAR </li><li>PSR1 </li><li>PSR12 </li><li>PSR2 </li><li>Squiz </li><li>Zend </li><li>PHPCompatibility </li> </ul> </li><li><code>--runtime-set </code>: Accepts <em>testVersion </em>with the target version we want to test our code compatibility with. In our case we want to test our PHP 5.4 code base and test our code base is compatible when we upgrade our runtime to version PHP 8.1. </li><li><code>--extensions </code>: Accepts any file extensions that we want to target for the <code>phpcs </code>routine to test the <em>testVersion </em>compatibility. If you have custom template files with file extension other than <code>php </code>but the are filled with PHP code, then ignore this argument. </li><li><code>--ignore </code>: Accepts the directory path to ignore. Typically you may not need vendor directory as you don’t want to touch the code base of third party referenced libraries. </li><li><code>--report-full </code>: Accepts text file name to which all the resultant code upgrade analysis is dumped to. </li> </ul>

<p>The <code>phpcs </code>is a CPU intensive operation. It scans each and every line of your repository. When this report is generated on project that has .php 4434 File(s) (included the files in vendor directory but excluded them for compatibility check) the operation took approximately above 65 mins on a PC with 16 GB RAM, i7 processor with 4 CPU cores. So to speed up memory based operation it is recommended to leave the PC and don’t do any multi tasking. </p>

<p>The report will have the file entry only if the <code>phpcs </code>has identified a potential <em>warning </em>or <em>error </em>identified at a particular <em>line number </em>in the <em>php file </em>along with <em>detail </em>. This line level <em>detail </em>has instructions or suggestions on what need to be done to make it compatible with the PHP runtime we are targeting to upgrade our code base to. Other files which pass or succeed through the <code>phpcs </code>scan won’t be added in the report. This means that the files which are not in the report already meet the code compatibility with target version of PHP we are planning to upgrade to. </p>

<p>The following snippet of text gives an idea of how a sample would look like in case of warning found in a particular php file. </p>

<p>We see that the error message is so intuitive. Based on such information, we move toward fixing those syntax to be compatible with target version we are trying to comply with. </p>

<p>Once you are done with all the fixes, you can plan action items to regress in the workflows and functionalities. Thus you will now have a vulnerability free, up-to-date version of PHP that is both latest and stable. </p>

<p>If you found this tutorial helpful, please do bookmark it 🔖 (Ctrl +D) for your future reference. Also share it with your friends and colleagues who are having trouble to understand how to upgrade their outdated PHP projects to latest and stable PHP 8.x version. </p>

Learn how to upgrade PHP 5.4 Projects to PHP 8.1 - TutLinks

Learn how to upgrade PHP 5.4 Projects to PHP 8.1

Hyd Shah's ideas are part of this journey:

Related collections

Similar ideas