Troubleshooting

Category “Default Category/abc/def/” has not been created. URL key for specified store already exists in Magento2

A new day, a new problem. While importing new products in Magento 2.1.2 via System > Data Transfer > Import something was causing the following error message.

1. Category "Default Category/abc/def/" has not been created. URL key for specified store already exists. in row(s): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

1	1. Category "Default Category/abc/def/" has not been created. URL key for specified store already exists. in row(s): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

The CSV file was 100% correct, which was making it difficult to figure out why it is causing the error. I ran few more test imports and noticed that the main category actually had an empty space at the end, which I believe was causing the whole problem.

The import ran through without any errors after removing the empty space. However, before I also removed all related URL rewrites as follows. Not sure if this was actually necessary.

mysql> DELETE FROM url_rewrite WHERE entity_type = 'category' AND request_path like '%abc/def/%';
Query OK, 6 rows affected (0.01 sec)

1 2	mysql> DELETE FROM url_rewrite WHERE entity_type = 'category' AND request_path like '%abc/def/%'; Query OK, 6 rows affected (0.01 sec)

After that I rebuilt the re-write table with https://github.com/olegkoval/magento2-regenerate_url_rewrites because for some reason the importer didn’t create the rewrite URLs.

$ php bin/magento ok:urlrewrites:regenerate
Regenerating of Url rewrites:

[Store ID: 0, Store View code: admin]:....................
....................
....................
....................
....................
....................
....................
....................
....................
....................
................URL key for specified store already exists.
....
..

$ php bin/magento ok:urlrewrites:regenerate

Regenerating of Url rewrites:

[Store ID: 0, Store View code: admin]:....................

....................

................URL key for specified store already exists.

....

After that everything was working as expected.

Create Static Block via SQL Queries in Magento2

Today I had to create a static block quickly via SQL queries because for some reason the grid in Content > Blocks didn’t work. First I created the static block itself.

INSERT INTO cms_block (title, identifier, content) VALUES ('Lorem Ipsum', 'loprem_ipsum', '<p>Lorem Ipsum is simply dummy text of the printing and typesetting industry.</p>');

1	INSERT INTO cms_block (title, identifier, content) VALUES ('Lorem Ipsum', 'loprem_ipsum', '<p>Lorem Ipsum is simply dummy text of the printing and typesetting industry.</p>');

Values for fields creation_time, update_time and is_active are not required because MySQL will add default values.

mysql> DESCRIBE cms_block;
+---------------+--------------+------+-----+-------------------+-----------------------------+
| Field         | Type         | Null | Key | Default           | Extra                       |
+---------------+--------------+------+-----+-------------------+-----------------------------+
| block_id      | smallint(6)  | NO   | PRI | NULL              | auto_increment              |
| title         | varchar(255) | NO   | MUL | NULL              |                             |
| identifier    | varchar(255) | NO   |     | NULL              |                             |
| content       | mediumtext   | YES  |     | NULL              |                             |
| creation_time | timestamp    | NO   |     | CURRENT_TIMESTAMP |                             |
| update_time   | timestamp    | NO   |     | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP |
| is_active     | smallint(6)  | NO   |     | 1                 |                             |
+---------------+--------------+------+-----+-------------------+-----------------------------+
7 rows in set (0.00 sec)

mysql> DESCRIBE cms_block;

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

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

| is_active | smallint(6) | NO | | 1 | |

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

7 rows in set (0.00 sec)

After that I created the relation between static block and the actual store.

INSERT INTO cms_block_store (block_id, store_id) VALUES (32, 0);

1	INSERT INTO cms_block_store (block_id, store_id) VALUES (32, 0);

In order to get the correct block_id you simply have to get block_id from the table cms_block.

SELECT * FROM cms_block WHERE identifier = 'lorem_ipsum';

1	SELECT * FROM cms_block WHERE identifier = 'lorem_ipsum';

In my case the block_id of my new static block was 32. That’s it.

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

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.

We’re sorry, an error has occurred while generating this email

Today, I was dealing with the following error message on one of our Magento2 production environment.

We're sorry, an error has occurred while generating this email.

1	We're sorry, an error has occurred while generating this email.

After spending 2 hours trying to find the source of the problem in our custom modules, I was able to fix the issue by disabling the core module Magento_SampleData.

$ bin/magento module:disable Magento_SampleData

1	$ bin/magento module:disable Magento_SampleData

What is this module for? This module gives you different sample data ( CMS, Catalog, Customers ) which is useful during development and testing phase. For your production environment it is not necessary and also not recommended to have it installed, as you can read here.

Reset Administrator User Password in Magento 2

Magento 2 comes with a CLI that allows you to create a new temporary administrator user within few seconds. Change to the directory where your Magento installation ( such as app or bin folder ) is located and run the following command to create a user support with password 8cd98f00b20.

php bin/magento admin:user:create --admin-user=support --admin-password=8cd98f00b20 --admin-email=support@myserver.com --admin-firstname=Firstname --admin-lastname=Lastname

1	php bin/magento admin:user:create --admin-user=support --admin-password=8cd98f00b20 --admin-email=support@myserver.com --admin-firstname=Firstname --admin-lastname=Lastname

Voilà!

Created Magento administrator user named support

1	Created Magento administrator user named support

Now you can go to System > Permissions > All Users and update other users credentials.