Monthly Archives: August 2019

If you decided to remove Magento 2 Mautic Integration Extension, please follow the steps below. You can contact our team for a free consultation in case you have any issues with Magefan's extension.

Remove Extension Files

1. If you can find the extension files in the folder

app/code/Magefan/MauticIntegration

then remove this folder.

2. If the extension was installed via the composer and its files located in the folder

vendor/magefan/module-mautic-integration

then run composer CLI command to remove it

composer remove magefan/module-mautic-integration

Once extension files have been removed, run these Magento CLI commands:

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy

Remove Extension Data (optional)

Attention! This will clean all Mautic integration extension data and configurations.

1. Just in case

If you need to update  Magento 2 Mautic Integration Extension by Magefan, please follow the steps below.

Update using composer

If the Mautic integration module was installed via the composer (check if vendor/magefan/module-mautic-integration folder exists), then you need to run these simple CLI commands in Magento 2 directory:

composer remove magefan/module-mautic-integration
composer require magefan/module-mautic-integration ^x.x.x
# replace x.x.x with the version you want to use
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy 

Update using archive and FTP

If the Mautic integration module was installed via FTP (check if app/code/Magefan/MauticIntegration folder exists), then follow these

You can install Magento 2 Mautic Integration Extension by Magefan, using composer or archive installation methods.

Installation via composer (recommended)

Please navigate to your Magefan Account > My Downloads > Install via Composer to get the composer installation instructions.

Installation using archive and FTP

1. Download Mautic Integration Extension ZIP-Archive from magefan.com website (not GitHub or other sources).
2. Extract files.
3. Copy app and lib folder from the archive to your Magento 2 folder.
   
4. In a command line, using "cd", navigate to your Magento 2 root directory.
5. Run CLI commands:

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy

Once

Do you hate to see when your Magento 2 store is broken or is in maintenance mode while running Magento 2 deployment commands? Yes? That's great. In the next 5 minutes, we'll help you with this pain. At Magefan we've created a Linux bash script that allows you to run bin/magento setup commands without braking store, long downtime, and losing sales.

Attention! This script is deprecated, we strongly recommend to use Magento 2 Zero Downtime Deployment Extension.

To use Magento 2 zero downtime deployment please follow the steps bellow:

Some Magento extensions may be no longer in use in your store. Reasons for that can vary. Some modules become irrelevant over time or there may be some crucial functionality lacking. That's why you might want to uninstall Magento 2 extension.

There are two methods for removing modules in Magento. You can either uninstall an extension manually or via composer. Let's have a look at each of them in more detail. 

Uninstall Magento 2 Extension via Composer

To uninstall Magento 2 module located in the vendor/vendor-name/module-name folder:

1. Connect to the root folder of your Magento via SSH.

2. Find the extension you want to remove using the following command:

php bin/magento module:status

3. Disable the extension:

php bin/magento module:disable <ExtensionProvider_ExtensionName> --clear-static-content
php bin/magento setup:upgrade

4. Go to your composer.json file to find the composer name of the extension and then uninstall it:

composer remove vendor-name/module-name

5. Run setup CLI commands:

When you test your page using Facebook Sharing Debugger and get the warning "The following required properties are missing: fb:app_id",

you need to add fb:app_id meta tag to the <head> tag of your page:

<meta property="fb:app_id" content="ХХХХХХХХХХХХХХХ" />

Replace ХХХХХХХХХХХХХХХ with your Facebook App ID.