Magento 2 Fixes

"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:

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

This "data-vocabulary.org schema deprecated" error is related to the breadcrumbs structure data. We used "data-vocabulary.org/Breadcrumb" schema for the structured data, but Google support 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 data-vocabulary.org to schema.org.

Before we get to the point of how

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

Trace:
<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:

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:

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.

Sometimes instead of the real customer IP address, you can see 127.0.0.1 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:

app/etc/XIP/di.xml

2. Paste the code:

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">
     <type name="Magento\Framework\HTTP\PhpEnvironment\RemoteAddress">
         <arguments>
            <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" xsi:type="string">HTTP_CF_CONNECTING_IP</item>
     

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 instead of bin/magento this command:

php -dmemory_limit=-1 bin/magento ....

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.

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

vendor/magento/framework/Exception/NoSuchEntityException.php

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

If you use Magento 2.2.x and get the error like:

1 exception(s):
Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'block', attribute 'class': [facet 'pattern'] The value '\Magento\Framework\View\Element\Text\ListText' is not accepted by the pattern '[A-Z][_a-zA-Z\d]*(\\[A-Z][_a-zA-Z\d]*)*'.
Line: 1187

Element 'block', attribute 'class': '\Magento\Framework\View\Element\Text\ListText' is not a valid value of the atomic type 'blockClassType'.
Line: 1187

Please find in all *.xml layout files string

class="\

and replace it with

class="

(Remove slash from the beginning of the class attribute value)