How to upgrade Kallyas from v3 to v4 the right way

Hello,

I’ve seen that most of the Kallyas clients are coming to the support forum asking for help after manually upgrading the theme from an old version such as v3 to the new version v4+.

Because Kallyas v4 is a major update which, by default, implies breaking changes, we strongly recommend that this upgrade should not be performed on the live website. We have tried to make the upgrade process as easy and as bug free as we could, but sometimes things don’t actually turn out as we planned – most of the times it’s the server configuration or some custom code implemented in the clients’ old themes.

If you decided to update the theme to any of the v4 versions, please take into consideration that this upgrade should first be done on a local copy of your live website in order to detect possible problems.

First of all, you need to make a full backup of your website, a database backup is also very important.

How to install the clone of your website locally:

First, you need to have a web server and make sure you can run php code. If you don’t have Apache, MySQL and PHP installed on your local computer, you can download and install WAMP(http://www.wampserver.com/en/) or XAMPP(https://www.apachefriends.org/index.html) which will isntall all these for you. Once you have the environment setup you will have to create a local website. You can do that by going to the htdocs directory where you have installed WAMP or XAMPP (usually it is /wamp/www/htdocs) and create a new directory that should be named as your domain name, for example, if your domain name is my-website.com you will create a new directory called “my-website”, and the path should be: “/wamp/www/htdocs/my-website”.

Now you’re ready to clone your website’s database. You can do that by using the Wp Migrate DB plugin (https://wordpress.org/plugins/wp-migrate-db/). Once you install and activate the plugin, you can find it in the administration menu under Tools > Migrate DB. Follow the steps and create a backup of your database. Please make sure you provide the correct paths when you create the download package. This plugin will provide you a screen where you can enter the local paths where you will install the backup, so please make sure you enter them correctly. For example, in the:

New URL field, you would add: //localhost/my-website
New file path, you would add: C:\wamp\www\htdocs\my-website

Click the “Migrate” button and download the sql dump file. It might be archived so you should extract the sql file that is inside.

Now, connect to your website through FTP and download your website’s files into “C:\wamp\www\htdocs\my-website”.

Now, use the MySQL interface from XAMPP or WAMPP (check the System tray icon) and install the sql dump you have downloaded from your website.

Once the files have completed downloading, edit the wp-config.php file and update the name of the database, user and password. Since WAMPP and XAMPP don’t setup a password for the database user, you should leave that empty. Save the config file and visit: http://localhost/my-website. At this point you should have a local working version of your live website.

Please note that before you proceed with the next steps, you should activate the Kallyas theme in case you’ve had the child theme active.

If everything worked so far, you are now ready to do the upgrade, so go to your account on the themeforest website and download the latest version of Kallyas.

Next steps:

  •  go to: C:\wamp\www\htdocs\my-website\wp-content\themes and delete the existent kallyas directory
  • extract the updated theme from the archive you ahve downloaded from themeforest into C:\wamp\www\htdocs\my-website\wp-content\themes
  • visit http://localhost/my-website/wp-admin and you will be prompted to update the theme data. Do that.

Once these steps are completed, you should now check how your website looks like after the update: http://localhost/my-website

At this point, things can go two ways, it either worked perfectly well or there will be problems, but the good part in this is that your live website will still be fully functional and you can get to work on fixing the problems on a local instance of it 🙂

 

Video Explainer:#