Page 4 - Blog

By now you may know that PHP 7 has been available for quite some time now coming with a number of improvements over version 5. It may be wise to upgrade to PHP7 when running for instance a WordPress using Amazon AWS where you are responsible for any upgrades.

Also as of July 2016, Amazon officially added PHP7 to its repository so you can install it using yum. So first thing I did was create a backup image of my EC2 instance before I went on with the upgrade. Once I had my backups done and proceeded with the PHP 7 upgrade.

Here are the steps I took in order to upgrade from PHP 5.x to 7.

Login to your Linux instance and perform the regular system updates first

$ sudo yum update

Stop the running webserver

$ sudo service httpd stop

Remove any existing PHP packages

$ sudo yum remove php*

Remove old web server installs

$ sudo yum remove httpd*

Update yum package repository

$ sudo yum clean all
$ sudo yum upgrade -y

Install Apache 2.4

$ sudo yum install httpd24

Install PHP 7 packages

$

Slack is one of the most popular collaboration platforms in the world that brings all your communication together. Conversations in Slack are organized in channels. You can create channels for your teams, projects, topics, or any other purpose to keep information and conversations organized. You can search through everything that’s been posted in channels or your messages. Slack also allows you to talk with your teammates over audio or video calls and share documents, images, videos, and other files.

Slack is not an open-source application and it is not included in the Ubuntu repositories.

This tutorial explains how to install Slack on Ubuntu 18.04. The same instructions apply for Ubuntu 16.04 and any other Debian based distribution, including Debian, Kubuntu, Linux Mint and Elementary OS.

Prerequisites

The user you are logged in as must have sudo privileges to be able to install packages.

Installing Slack on Ubuntu

1. Download Slack

Open your terminal either by using the Ctrl+Alt+T

The topic today is one of the popular errors you will meet. As if the error message shows “An error has happened during application run. See exception log for details” in Magento 2 when you have uploaded Magento CE latest version and want to install it on your server, so what should you do? Here is the right solution for you.

How to resolve: “An error has happened during application run. See exception log for details”

Please open the .htaccess from the root and comment out the first line:

SetEnv MAGE_MODE developer

On your system, if you have installed multiple versions of PHP (eg PHP 7.1 and PHP 5.6 both). PHP 7.1 is running as default PHP for Apache and CLI. For any requirement, you need to use PHP 5.6. Then you don’t need to remove PHP 7.1. You can simply switch your PHP version to default used for Apache and command line.

For example, your server has PHP 7.1 and PHP 5.6 both version’s installed. Now following example will help you to switch between both versions.

From PHP 5.6 => PHP 7.1

Default PHP 5.6 is set on your system and you need to switch to PHP 7.1. Run the following commands to switch for Apache and command line.

Apache:-

$ sudo a2dismod php5.6
$ sudo a2enmod php7.1
$ sudo service apache2 restart

Command Line:-

$ sudo update-alternatives --set php /usr/bin/php7.1
$ sudo update-alternatives --set phar /usr/bin/phar7.1
$ sudo update-alternatives --set phar.phar /usr/bin/phar.phar7.1

From PHP 7.1 => PHP 5.6

Default PHP 7.1 is set on your system and you need to switch to PHP 5.6.

• Delete the Module folder from {folder path}\app\code
• Remove module entry from below tables core_config_data & setup_module

• Run command

  {magento project root path}>{php path}\php bin/magento setup:upgrade => Setup Upgrade

  {magento project root path}>{php path}\php bin/magento cache:flush => Clear Cache

Depending on your configuration it may also be unecessary. If you are in default or dev mode you do not need it.

You just need it on production mode

From command line and from your Magento root path:

php bin/magento setup:di:compile

P.S: After installing your module make sure you ran:

php bin/magento setup:upgrade

Install PHPUnit

Installing PHPUnit package on Ubuntu 16.04 (Xenial Xerus) is as easy as running the following command on the terminal:

sudo apt-get update
sudo apt-get install phpunit

Updating/Upgrading to Magento 2.1.0 (via composer)

composer require magento/product-community-edition 2.1.0 --no-update

composer update

rm -rf var/di var/generation

sudo chmod -R 777 var/

php bin/magento cache:clean

php bin/magento cache:flush

php bin/magento setup:upgrade

php bin/magento setup:di:compile

php bin/magento indexer:reindex

After upgrade, check your Magento version with the following command:

php bin/magento --version

Magento CLI version 2.1.0

If you are installing new Ubuntu 16.04 LTS or upgrading/Downgrade from your older Ubuntu installation then you will get an error like “phpMyAdmin – Error – The mbstring extension is missing. Please check your PHP configuration”. This error can happen on browser for your phpmyadmin access after installation or upgrade to Ubuntu 16.04.

just run these command

sudo apt-get install phpmyadmin php-mbstring php-gettext

sudo service apache2 restart

Integrity constraint violation: 1062 Duplicate entry ‘4-Images’ for key ‘EAV_ATTRIBUTE_GROUP_ATTRIBUTE_SET_ID_ATTRIBUTE_GROUP_NAME’, query was: UPDATE `eav_attribute_group` SET `attribute_group_name` = ? WHERE (`attribute_group_id`=10)

This particular error presented itself while upgrading from Magento 2.0.2 to Magento 2.1.x and stops the upgrade process. We’ve discovered the issue is related to old data from the previous Magento 1.9.x installation. In order to over come this error, you’ll need to delete a row from the database.

Run the following MySQL query to find and delete the offending attribute.

delete from eav_attribute_group WHERE attribute_group_name = 'Images';

After that then you can attempt to run the upgrade command again and the issue should be resolved.

We understand not everyone can be a MySQL / Magento 2 expert so if you’re faced with a similar issue and stuck between an upgrade feel free to contact us to assist with your problem.