Black Friday Sale Final webpconverted Hours

Magento 2 Fixes

  1. Debugging PHP Infinite loop in Magento 2

    There are situations in Magento 2 when page keeps loading and then you get 500 fatal error, memory limit, or timeout error. This is an infinite loop in the PHP code, when the same code is executed over and over again. It is related to some core Magento issues or, most likely, third party extension.

    To debug an infinite loop and find the loop entrance, please follow the steps below:

    1. Open the app/bootstrap.php file and add this code right after PHP open tag <?php in the next line

    $_SERVER['MAGE_PROFILER'] = 'html';

    2. Open the vendor/magento/framework/Profiler.php file and add this code to the beginning of "public static function start($timerName, array $tags = null)" function, e.g.

    Read more »
  2. Fix "There has been an error processing your request" issue in Magento 2

    "There has been an error processing your request" is the message you can receive when working with Magento 2.  Here is the example of this message:

    There has been an error processing your request

    Read more »
  3. schema deprecated - Error Fix Solution

    Recently we got an " schema deprecated and not supported by Google anymore. Please migrate to using types." error validating one of our website pages. The same error we got in Google Search Console. schema is deprecated and not supported by Google anymore. Please migrate to using types

    This " schema deprecated" error is related to the breadcrumbs structure data. We used "" schema for the structured data, but Google supports it no longer. 

    You may also receive this error starting from April 6, 2020, in case you haven't converted your structured data scheme from to

    Before we get to the point of how

    Read more »
  4. Warning: file_get_contents(): SSL operation failed with code 1. OpenSSL Error messages - Magento 2 Fixes

    If you use Magento 2 and get an error like this:

    Warning: file_get_contents(): SSL operation failed with code 1. OpenSSL Error messages:
    error:14095126:SSL routines:ssl3_read_n:unexpected eof while reading in vendor/google/recaptcha/src/ReCaptcha/RequestMethod/Post.php on line 72

    <pre>#1 file_get_contents() called at [vendor/google/recaptcha/src/ReCaptcha/RequestMethod/Post.php:72]
    #2 ReCaptcha\RequestMethod\Post->submit() called at [vendor/google/recaptcha/src/ReCaptcha/ReCaptcha.php:156]
    #3 ReCaptcha\ReCaptcha->verify() called at [app/code/MSP/ReCaptcha/Model/Validate.php:79]
    #4 MSP\ReCaptcha\Model\Validate->validate() called at [app/code/MSP/ReCaptcha/Observer/ReCaptchaObserver.php:93]
    #5 MSP\ReCaptcha\Observer\ReCaptchaObserver->execute() called at [vendor/magento/framework/Event/Invoker/InvokerDefault.php:72]
    #6 Magento\Framework\Event\Invoker\InvokerDefault->_callObserverMethod() called at [vendor/magento/framework/Event/Invoker/InvokerDefault.php:60]

    when trying to login to the admin panel, reset customer password, create a new customer account, etc., you can make a quick fix. To do this please follow the steps below:

    Read more »
  5. Magento 2.3 - TinyMCE 4 Toolbar / Text Color Tool Missing

    In Magento 2.3 and greater, Magento team has changed WYSIWYG editor, instead of TinyMCE 3 Magento started use TinyMCE 4.

    On the picture below, you can see Magento 2.0-2.2 TinyMCE 3  editor:

    TinyMCE 3 Magento 2 Editor

    Default Magento TinyMCE 4 editor does not include a lot of tools for example text color or text background and this can be inconvenient for the content manager.

    Magento 2 TinyMCE 4

    Read more »
  6. Magento 2 Showing Wrong Customer IP

    Sometimes instead of the real customer IP address, you can see or some other wrong customer IP in your Magento 2 Admin panel. It can be due to proxies, like Varnish, Cloudflare,, that may be enabled for your Magento 2 store.

    To solve the wrong IP address issue you need to:

    1. Create a new file in M2 directory:


    2. Paste the code:

    <?xml version="1.0"?>
    <config xmlns:xsi=""
    <type name="Magento\Framework\HTTP\PhpEnvironment\RemoteAddress">
    <argument name="alternativeHeaders" xsi:type="array">
    <item name="x-client-ip" xsi:type="string">HTTP_X_REAL_IP</item>
                    <item name="x-cf-connecting-ip"
    Read more »
  7. bin/magento Fatal error: Allowed memory size of xxxx bytes exhausted (tried to allocate xxx bytes)

    When you run Magento 2 CLI command "bin/magento ..." and get the error:

    Allowed memory size of xxxx bytes exhausted (tried to allocate xxx bytes)

    You can easily fix it using this command instead of bin/magento:

    php -dmemory_limit=-1 bin/magento ....
    Read more »
  8. Fix: Module 'Company_Module' from 'app/code/Company/Module' has been already defined in 'vendor/company/module'.

    If you have installed or updated Magento 2 extension and received the error message e.g.:

    Module 'Company_Module' from 'app/code/Company/Module' has been already defined in 'vendor/company/module'.

    this means that you have 2 versions of the extension:

    1) in the folder app/code/Company/Module
    2) in the folder vendor/company/module

    In vendor folder Magento stores all components (extensions, themes, language packages) that have been installed using Composer.

    As installing or updating extensions via Composer is preferred, you need to remove the extension folder app/code/Company/Module (please don't forget about a backup before removal) and run installation commands.

    Read more »
  9. No such entity - Fix for Magento 2

    If you receive the error message "No such entity.", "No such entity with" or "No such entity with customerId" in Magento 2, the issue usually occurred when you try to load not existing object via Magento 2 Repository Class.

    To debug this issue, please open the file


    Read more »
  10. The following modules are outdated - Fix The Issue

    When you update Magento 2, Magento extension or switching git branches on your dev environment, sometimes you can get the error:

    The following modules are outdated: Vendor_Module schema: current version - x.x.x, required version - z.z.z 

    To solve this issue, please do next:

    1. Try to get the latest extension code. Run CLI command in the Magento root directory:

    composer install

    If you get troubles with running this command, then just skip it, and move to step 2.

    2. Try to upgrade your database. Run CLI command:

    php bin/magento setup:upgrade

    Read more »
Posts loader