PHP-5.2.17 born again like Frankenstein

Started by ACKET, Jun 27, 2022, 11:33 AM

Previous topic - Next topic

ACKETTopic starter

My goal is to resurrect things written in PHP-5.2.1.17 taking in consideration that when I hit PHP-V I get

PHP 5.2.17 (cli) (built: Sep 27 2020 09:42:24)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies

i have also postgres installed so dont know if I can handle my databases with it or should I also install mysql 5.0,wont it affect postgresql or can I have both things installed and also how I configure apache configuration sheet

Please do aliby
  •  

DenPavlov

First question is why? That is, are you planning to update the code to use PHP 7 or keep it at 5.2 and if so why not start out in 7?

As for mysql and postgresql, they can be on the same server without issue as they are different services on different ports, using different binaries, etc. MariaDB and mysql on the other hand would conflict with each other.
  •  
    The following users thanked this post: ACKET

Sevad

What happens when you install the latest version of each form of software? Do you have the same problems?
With your original idea, no point in using the old versions as they are worse in performance in security. Now if there software applications out there that you liked it may be a good idea to create a new version of the software with a new name as inspiration.
Using old software, especially that old is normally not going to end up well as it is harder to find people to help you with development and the software has known security problems that have been fixed in newer versions.
  •  

jayden89

Why update PHP version if everything works?
Speed. The newer the PHP version, the faster it works. Acceleration can reach 20-30%.

Pauses in work. The older the project, the more difficult it is to find a specialist capable of finalizing it.
A banal example — everyone is surprised that the military still uses floppy disks. They missed the right moment and now the upgrade will cost them very dearly. After all, you need not only to upgrade, but also to test everything. It is quite possible that the site will not work for some time, which will lead to inconveniences or losses.

Automatic updates. Most often, if the engine is on an old version of PHP, it does not download updates. It is static, and then the moment extra users appear in the admin panel or the site starts sending spam. The first point of the solution is to update. All this can accumulate in a snowball, so it's better to update in a timely manner.
Search for a developer. You won't be able to take a random freelancer who works on the market and tell him: "Work with a ten-year project."
Search for hosting. The older PHP is, the harder it is to find hosting. Hosting providers want to update and keep their server within certain limits.
It is quite possible that one day the old version will simply not work on the updated server. Almost the same thing happened with Windows XP, which was "killed" only by the fact that browsers stopped updating on it.
  •