Tobias Forkel

Class not found in AbstractFactory

Today I had some trouble with removing a module on Magento2 and its custom product attributes. After removing the code of Mageplaza_Seo I was not able to edit products, categories or even checkout anymore.

Fatal error: Uncaught Error: Class 'Mageplaza\Seo\Model\Source\Robots' not found in /home/www/client/src/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php:93 Stack trace: #0
/home/www/client/src/vendor/magento/framework/ObjectManager/Factory/Compiled.php(88): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Mageplaza\\Seo\\M...', Array) #1
/home/www/client/src/vendor/magento/framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Compiled->create('Mageplaza\\Seo\\M...', Array) #2
/home/www/client/src/vendor/magento/framework/Validator/UniversalFactory.php(36): Magento\Framework\ObjectManager\ObjectManager->create('Mageplaza\\Seo\\M...', Array) #3
/home/www/client/src/vendor/magento/module-eav/Model/Entity/Attribute/AbstractAttribute.php(551): Magento\Framework\Validator\UniversalFactory->create('\\Mageplaza\\Seo\\...') #4
/home/www/client/src/vendor/magento/module-catalog/Mode in /home/www/client/src/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 93

Fatal error: Uncaught Error: Class 'Mageplaza\Seo\Model\Source\Robots' not found in /home/www/client/src/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php:93 Stack trace: #0

/home/www/client/src/vendor/magento/framework/ObjectManager/Factory/Compiled.php(88): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Mageplaza\\Seo\\M...', Array) #1

/home/www/client/src/vendor/magento/framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Compiled->create('Mageplaza\\Seo\\M...', Array) #2

/home/www/client/src/vendor/magento/framework/Validator/UniversalFactory.php(36): Magento\Framework\ObjectManager\ObjectManager->create('Mageplaza\\Seo\\M...', Array) #3

/home/www/client/src/vendor/magento/module-eav/Model/Entity/Attribute/AbstractAttribute.php(551): Magento\Framework\Validator\UniversalFactory->create('\\Mageplaza\\Seo\\...') #4

/home/www/client/src/vendor/magento/module-catalog/Mode in /home/www/client/src/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 93

The reason was an attribute called mp_meta_robots which was still pointing to the class \Mageplaza\Seo\Model\Source\Robots. I found the attribute by checking the table eav_attribute as follows.

mysql> SELECT * FROM eav_attribute WHERE source_model LIKE '%Mageplaza%'; 
+--------------+----------------+----------------+-----------------+---------------+--------------+---------------+----------------+----------------+----------------+----------------+------------------------------------+-------------+-----------------+---------------+-----------+------------------------+
| attribute_id | entity_type_id | attribute_code | attribute_model | backend_model | backend_type | backend_table | frontend_model | frontend_input | frontend_label | frontend_class | source_model                       | is_required | is_user_defined | default_value | is_unique | note                   |
+--------------+----------------+----------------+-----------------+---------------+--------------+---------------+----------------+----------------+----------------+----------------+------------------------------------+-------------+-----------------+---------------+-----------+------------------------+
|          222 |              4 | mp_meta_robots | NULL            | NULL          | varchar      | NULL          | NULL           | select         | Meta Robots    | NULL           | \Mageplaza\Seo\Model\Source\Robots |           0 |               0 | NULL          |         0 | Added by Mageplaza.com |
|          223 |              3 | mp_meta_robots | NULL            | NULL          | varchar      | NULL          | NULL           | select         | Meta Robots    | NULL           | \Mageplaza\Seo\Model\Source\Robots |           0 |               0 | NULL          |         0 | Added by Mageplaza.com |
+--------------+----------------+----------------+-----------------+---------------+--------------+---------------+----------------+----------------+----------------+----------------+------------------------------------+-------------+-----------------+---------------+-----------+------------------------+
2 rows in set (0.00 sec)

mysql> SELECT * FROM eav_attribute WHERE source_model LIKE '%Mageplaza%';

+--------------+----------------+----------------+-----------------+---------------+--------------+---------------+----------------+----------------+----------------+----------------+------------------------------------+-------------+-----------------+---------------+-----------+------------------------+

2 rows in set (0.00 sec)

Removing this via backend or MySQL has fixed the problem.

mysql> delete from eav_attribute where attribute_code = 'mp_meta_robots';
Query OK, 2 rows affected (0.01 sec)

1 2	mysql> delete from eav_attribute where attribute_code = 'mp_meta_robots'; Query OK, 2 rows affected (0.01 sec)

Update Order Status With SQL Queries in Magento2

Today I had to update order numbers which were processed already, but not updated in Magento. Here is how I changed the order status directly in the database based on the increment_id.

The first query will update the state and status on the table sales_order.

mysql> UPDATE sales_order SET state='complete', status='complete' WHERE increment_id IN (000043719,000044003,000044117,...);
Query OK, 15 rows affected (0.08 sec)
Rows matched: 16  Changed: 15  Warnings: 0

mysql> UPDATE sales_order SET state='complete', status='complete' WHERE increment_id IN (000043719,000044003,000044117,...);

Query OK, 15 rows affected (0.08 sec)

Rows matched: 16 Changed: 15 Warnings: 0

The second one will update the status in the grid view in Sales > Orders.

mysql> UPDATE sales_order_grid SET status='complete' WHERE increment_id IN (000043719,000044003,000044117,...);
Query OK, 15 rows affected (0.03 sec)
Rows matched: 16  Changed: 15  Warnings: 0

mysql> UPDATE sales_order_grid SET status='complete' WHERE increment_id IN (000043719,000044003,000044117,...);

Query OK, 15 rows affected (0.03 sec)

Rows matched: 16 Changed: 15 Warnings: 0

Cannot gather stats! Warning!stat(): stat failed

Today I imported a couple of new products with uRapidFlow in Magento 2.1.2. I ran the import with the option Action on missing image file which was set to WARNING and update image field. It worked fine, but I accidentally forgot to upload the product images.

So basically uRapidFlow added non-existing product images to the database which broke the product edit form in the admin panel.

Cannot gather stats! Warning!stat(): stat failed for /var/www/src/pub/media/catalog/product/A_217823.JPG

1	Cannot gather stats! Warning!stat(): stat failed for /var/www/src/pub/media/catalog/product/A_217823.JPG

The temporarily solution was to manipulate ./vendor/magento/module-catalog/Block/Adminhtml/Product/Helper/Form/Gallery/Content.php in vendor around line 142,143.

if (is_readable($this->_mediaConfig->getMediaPath($image['file'])))
{
    $fileHandler = $mediaDir->stat($this->_mediaConfig->getMediaPath($image['file']));
    $image['size'] = $fileHandler['size'];
}

if (is_readable($this->_mediaConfig->getMediaPath($image['file'])))

{

$fileHandler = $mediaDir->stat($this->_mediaConfig->getMediaPath($image['file']));

$image['size'] = $fileHandler['size'];

}

I basically added is_readable to check if the file exists. Not great, but at least I was able to edit products again and proceed with a permanent fix.

Algolia and Undefined index: store_id

Today I have setup the Algolia Queue Runner ( algolia_queue_runner ) which was working fine for all projects I have worked with before. However, today it was different. The Algolia Queue Runner didn’t work at all. Here is what happened every time when the cronjob was running.

$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner
Algolia Search Queue Runner indexer process unknown error:
Notice: Undefined index: store_id in /var/www/src/vendor/algolia/algoliasearch-magento-2/Model/Queue.php on line 163

$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner

Algolia Search Queue Runner indexer process unknown error:

Notice: Undefined index: store_id in /var/www/src/vendor/algolia/algoliasearch-magento-2/Model/Queue.php on line 163

The problem was, one of the store views in Stores > Settings > All Stores was disabled for some reason. After enabling the store view, the problem was fixed.

$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner
Algolia Search Queue Runner index has been rebuilt successfully in 00:00:00

1 2	$ php /var/www/src/bin/magento indexer:reindex algolia_queue_runner Algolia Search Queue Runner index has been rebuilt successfully in 00:00:00

Captcha Test For Your Contact Form

The following PHP script allows you to test your contact form captcha integration in Magento. If you receive any email after executing this script, you have to review your captcha integration.

<?php

$url = '{base_url}/contacts/index/post/';

$fields = array(
    'name' => urlencode('Bad spam test'),
    'email' => urlencode('somebody@gmail.com'),
    'state' => urlencode('Any State'),
    'postcode' => urlencode(''),
    'telephone' => urlencode(''),
    'comment' => urlencode('Bad spam test'),
    'recaptcha-verification-1' => urlencode('checked'),
);

$query = http_build_query($fields);

$ch = curl_init();
curl_setopt($ch,CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch,CURLOPT_URL, $url);
curl_setopt($ch,CURLOPT_POST, count($fields));
curl_setopt($ch,CURLOPT_POSTFIELDS, $query);

$result = curl_exec($ch);

curl_close($ch);

?>

<?php

$url = '{base_url}/contacts/index/post/';

$fields = array(

'name' => urlencode('Bad spam test'),

'email' => urlencode('somebody@gmail.com'),

'state' => urlencode('Any State'),

'postcode' => urlencode(''),

'telephone' => urlencode(''),

'comment' => urlencode('Bad spam test'),

'recaptcha-verification-1' => urlencode('checked'),

);

$query = http_build_query($fields);

$ch = curl_init();

curl_setopt($ch,CURLOPT_FOLLOWLOCATION, 1);

curl_setopt($ch,CURLOPT_URL, $url);

curl_setopt($ch,CURLOPT_POST, count($fields));

curl_setopt($ch,CURLOPT_POSTFIELDS, $query);

$result = curl_exec($ch);

curl_close($ch);

You may need to add, remove or rename fields in the $field array. Don’t forget to replace {base_url} with your actual URL.

Broken Admin Panel after SUPEE-8788

After the installation of patch SUPEE-8788 in Magento 1.9.0.1 I have experienced a broken product edit form in Catalog > Manage Products > { select any product } > Edit Product. Every time when I tried to edit a product it was logging the following error message.

2016/11/04 19:52:04 [error] 16030#16030: *14543 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Undefined class constant 'XML_NODE_PRODUCT_MAX_DIMENSION' in /var/www/{project.com}/src/app/design/adminhtml/default/default/template/catalog/product/helper/gallery.phtml on line 111" while reading response header from upstream, client: 115.70.205.114, server: {project.com}, request: "GET /index.php/admin/catalog_product/edit/id/549/key/2648665fef72a346f08657ca178f5a51/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "{project.com}", referrer: "http://{project.com}/index.php/admin/catalog_product/index/key/4cd6b694401f474c72d0dbd9d639e651/"

2016/11/04 19:52:04 [error] 16030#16030: *14543 FastCGI sent in stderr: "PHP message: PHP Fatal error: Undefined class constant 'XML_NODE_PRODUCT_MAX_DIMENSION' in /var/www/{project.com}/src/app/design/adminhtml/default/default/template/catalog/product/helper/gallery.phtml on line 111" while reading response header from upstream, client: 115.70.205.114, server: {project.com}, request: "GET /index.php/admin/catalog_product/edit/id/549/key/2648665fef72a346f08657ca178f5a51/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "{project.com}", referrer: "http://{project.com}/index.php/admin/catalog_product/index/key/4cd6b694401f474c72d0dbd9d639e651/"

I have found a community extension in my project which was causing the problem by rewriting the complete class Mage_Catalog_Helper_Image. With diff I was able to identify all changes which I needed to copy from core to the community extension.

diff app/code/community/{Module_Name}/Catalog/Helper/Image.php app/code/core/Mage/Catalog/Helper/Image.php

1	diff app/code/community/{Module_Name}/Catalog/Helper/Image.php app/code/core/Mage/Catalog/Helper/Image.php

I just added the missing constant

const XML_NODE_PRODUCT_MAX_DIMENSION = 'catalog/product_image/max_dimension';

1	const XML_NODE_PRODUCT_MAX_DIMENSION = 'catalog/product_image/max_dimension';

and updated the method validateUploadFile().

public function validateUploadFile($filePath) {

1	public function validateUploadFile($filePath) {

Delete Quote For Specific Customer In Magento2

Sometimes a quote can be linked with product id’s which doesn’t exists anymore. In some cases it can cause broken MySQL joins. Here is how you can flush the quote for a specific customer in Magento2.

mysql> DELETE FROM quote WHERE customer_email = 'customer@gmail.com';

1	mysql> DELETE FROM quote WHERE customer_email = 'customer@gmail.com';

Remove the WHERE clause to flush the quote for all customers.

AWS RDS – You Need (at least one of) The SUPER Privilege(s)

Today I had the opportunity to move a local Magento database to an Amazon RDS. Based on the well-documented article Creating a DB Instance Running the MySQL Database Engine I was optimistic to finish the migration pretty soon. But as you know, there is always something that goes wrong.

After creating the database instance class ( db.m3.large ) I have decided to proceed with some test imports before I change any database credentials in Magento.

$ mysql -h customer.1xcpdspit6hz.ap-southeast-2.rds.amazonaws.com -u customer -p
$ source ~/project_20161014_1135.sql

1 2	$ mysql -h customer.1xcpdspit6hz.ap-southeast-2.rds.amazonaws.com -u customer -p $ source ~/project_20161014_1135.sql

Good decision because the first import didn’t run through.

ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
Query OK, 0 rows affected (0.01 sec)

1 2	ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable) Query OK, 0 rows affected (0.01 sec)

I was able to fix the problem by adding the missing parameter log_bin_trust_function_creators as explained here. Before the next import I had to delete the database and create a new one.

ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER privilege(s) for this operation
Query OK, 0 rows affected (0.00 sec)

1 2	ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER privilege(s) for this operation Query OK, 0 rows affected (0.00 sec)

Unfortunately there was another problem with a DEFINER which tried to create a trigger as a different user. On Amazon RDS only a user with SUPER privileges can do that. Therefore, I had to remove the DEFINER from the MySQL schema you see below.

$ sed -i 's/DEFINER=[^*]*\*/\*/g' project_20161014_1135_toimport.sql

1	$ sed -i 's/DEFINER=[^]\/\/g' project_20161014_1135_toimport.sql

That’s it. Now I was able to import my DB on Amazon RDS without errors.

Find Missing Or Not Readable Product Image Files

With the following script you can detect missing or not readable image files, based on your product collection. Good before project launch or after product imports.

<?php
/**
 * Find missing or not readable product image files in Magento1.
 * Run this file via command line ( php fmpif.php ) or open it in your web browser.
 *
 * @copyright   Copyright (c) 2016 Tobias Forkel (http://www.tobiasforkel.de)
 * @license     http://opensource.org/licenses/osl-3.0.php Open Software License (OSL 3.0)
 */

require_once 'app/Mage.php';
Mage::app();

// Collection of all products
$products = Mage::getModel('catalog/product')->getCollection();

// Get absolute path to media folder
$media = Mage::getBaseDir('media');

// Count missing files
$i = 0;

foreach ($products as $_product)
{
    $product = Mage::getModel('catalog/product')->load($_product->getId());

    foreach ($product->getMediaGalleryImages() as $image)
    {
        $file = $media . '/catalog/product' . $image['file'];

        if (!is_readable($file))
        {
            $i++;
            echo sprintf('The image file (%s) from product SKU number (%s) doesn\'t exists or is not readable.', $file, $_product->getSku());
        }
    }
}

if ($i == 0)
{
    echo 'All good!';
}

?>

<?php

/**

* Find missing or not readable product image files in Magento1.

* Run this file via command line ( php fmpif.php ) or open it in your web browser.

* @license http://opensource.org/licenses/osl-3.0.php Open Software License (OSL 3.0)

require_once 'app/Mage.php';

Mage::app();

// Collection of all products

$products = Mage::getModel('catalog/product')->getCollection();

// Get absolute path to media folder

$media = Mage::getBaseDir('media');

// Count missing files

$i = 0;

foreach ($products as $_product)

{

$product = Mage::getModel('catalog/product')->load($_product->getId());

foreach ($product->getMediaGalleryImages() as $image)

{

$file = $media . '/catalog/product' . $image['file'];

if (!is_readable($file))

{

$i++;

echo sprintf('The image file (%s) from product SKU number (%s) doesn\'t exists or is not readable.', $file, $_product->getSku());

}

if ($i == 0)

{

echo 'All good!';

}

Find the Gist here.

Automatically Update The Year In The Footer

In most of the projects that I am working on, it is still common practice to have the current year of the copyright text stored in System > Configuration > General > Design > Footer.

&copy; 2015 Magento Demo Store. All Rights Reserved.

1	© 2015 Magento Demo Store. All Rights Reserved.

That means, every year somebody has to change the year manually. This is very time consuming, especially if you have to manage ten, twenty or more clients. Here is a quick example of how you can make it dynamic.

1. Set a custom string such as {YEAR}

Edit your footer in System > Configuration > General > Design > Footer and place the {YEAR} somewhere.

&copy; {YEAR} Magento Demo Store. All Rights Reserved.

1	© {YEAR} Magento Demo Store. All Rights Reserved.

2. Replace the {YEAR}

Edit your footer.phtml in your package and replace getCopyright as shown below. For the year I am using Mage::getModel(‘core/date’) to have the correct timezone included.

<div class="footer-container">
    <div class="footer">
        <?php echo $this->getChildHtml() ?>
        <p class="bugs"><?php echo $this->__('Help Us to Keep Magento Healthy') ?> - <a href="http://www.magentocommerce.com/bug-tracking" onclick="this.target='_blank'"><strong><?php echo $this->__('Report All Bugs') ?></strong></a> <?php echo $this->__('(ver. %s)', Mage::getVersion()) ?></p>
        <address><?php echo str_replace('{YEAR}', Mage::getModel('core/date')->date('Y'), $this->getCopyright()); ?></address>
    </div>
</div>

<?php echo $this->getChildHtml() ?>

<p class="bugs"><?php echo $this->__('Help Us to Keep Magento Healthy') ?> - <a href="http://www.magentocommerce.com/bug-tracking" onclick="this.target='_blank'"><strong><?php echo $this->__('Report All Bugs') ?></strong></a> <?php echo $this->__('(ver. %s)', Mage::getVersion()) ?></p>

<address><?php echo str_replace('{YEAR}', Mage::getModel('core/date')->date('Y'), $this->getCopyright()); ?></address>

</div>

File: ./app/design/frontend/{package}/default/template/page/html/footer.phtml