The mysql_result in mysqli

Many of you have run into a problem when you were working on some old legacy php script that you wanted to adapt to PHP 7 where mysql_ functions no longer work (since they are deprecated).

The new PHP 7 comes with two database drivers: MySQLi and PDO. The PDO supports many different databases while MySQLi supports only MySQL.

So you probably thought, I’m just going to replace all mysql_ functions with mysqli_ and it’s done. Well, I’ve got bad news for you. It won’t! Also this way is also not safe. So take your time and learn about the changes and how you can overcome them.

How to downgrade PHP 7.4 to PHP 7.3 on VestaCP running on CentOS 7

I installed VestaCP for a clien on a new dedicated server running CentOS 7. Once you get a server or VPS with CentOS 7 by default it has no PHP installed.

After you install VestaCP using their guide for some reason you’ll end up with PHP 7.4.0RC5.

$ php -v
PHP 7.4.0RC5 (cli) (built: Oct 29 2019 08:49:19) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0-dev, Copyright (c) Zend Technologies

I didn’t like that first time I saw it and after I tried using it like that but the errors would just start popping all over the place. Even with software that VestaCP installed, like phpMyadmin:

There were also some errors with some WordPress themes and plugins and it was just not looking right and I wanted to back to stable version of PHP 7.3 but VestaCP doesn’t offer such thing out of the box, so the only way was to remove PHP 7.4 and install PHP 7.3 manually from command line.

Here are the lines you need to execute:

yum install yum-utils -y
yum-config-manager --disable remi-php5*
yum-config-manager --disable remi-php74
yum-config-manager --disable remi-test
yum-config-manager --enable remi-php73
yum remove php php-* -y
yum install roundcube phpmyadmin -y
service httpd restart

After this the you sould have PHP 7.3 up and running:

$ php -v
PHP 7.3.11 (cli) (built: Oct 22 2019 08:11:04) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.11, Copyright (c) 1998-2018 Zend Technologies

But two other problems arise: phpMyAdmina and RoundCube wembail are not working:

I went to check the config files at /etc/httpd/conf.d/ folder and I have noticed duplicate files for phpMyadmin and RoundCube: beside standard .conf files there were also .conf.rpmsave files (old ones).

So I removed these new ones (.conf) and renamed these old ones back to new ones restarted web server and everything was working again. Please make sure that you know what you’re doing here. Instead of deleting these two files you might want to just rename them or move them somewhere in case you’ll need them later. So have that in mind!

So, this is what I have done:

cd /etc/httpd/conf.d/
rm phpMyAdmin.conf
rm roundcubemail.conf
mv phpMyAdmin.conf.rpmsave phpMyAdmin.conf
mv roundcubemail.conf.rpmsave roundcubemail.conf
service httpd restart

BONUS: How to install OPCache and improve your php performance on VestaCP

OPcache improves PHP performance by storing precompiled script bytecode in shared memory, thereby removing the need for PHP to load and parse scripts on each request.

yum install php-opcache -y
service httpd restart

And now php -v confirms that OPCache is active and running:

$ php -v
PHP 7.3.11 (cli) (built: Oct 22 2019 08:11:04) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.11, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.11, Copyright (c) 1999-2018, by Zend Technologies

How to migrate private repository from BitBucket to GitHub

Last year Microsoft bought GitHub for $7.5B and shortly after that they have changed their policy on private repositories. Before, private repositories were reserved only for paying members, but since January 7th 2019 even non-paying users are allowed to have unlimited private repositories.

In case you want to migrate your private repository from BitBucket to GitHub and keep all the previous gits.

First, login to your GitHub and make a new empty private repository (do not tick “Initialize this repository with a README”). You can use any name but the best practice is to use the same name as on BitBucket.

Now let’s clone the repository from BitBucket and push it back to GitHub. Make sure to replace geektnt with your bitbucket/github username and coolproject with an actual repository name.

git clone --mirror https://bitbucket.org/geektnt/coolproject.git
cd coolproject.git
git remote set-url --push origin [email protected]:geektnt/coolproject.git
git push --mirror

After this is done you can leave the folder and remove the repository directory (since it’s not usable project as it’s cloned with –mirror parameter)

cd ..
rm -rf coolproject.git

And you can now clone it from GitHub and continue where you have stoped:

git clone [email protected]:geektnt/coolproject.git
cd coolproject
...
(make changes, add, commit, push...)

At this point you can remove old BitBucket repository if everything works at GitHub.

This way to migrate worked out amazing for me and I have moved couple of my older private projects from BitBucket to GitHub so I can have them all at one place.