PHP / Magento Developer
If you are using Xtento in combination with an automated product importer, you may have seen the following error before.
|
1 |
Missing required argument $name of Xtento\ProductExport\Logger\Logger. |
The error message appears right after saving a product. The reason is that, at least one of your products in Products > Catalog has no Name. To fix this, you can update the name manually via MySQL queries or simply delete the products and import again correctly.
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 |
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.
|
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.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
$ 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.
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.
|
1 2 3 4 5 6 |
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.
|
1 2 3 4 5 6 7 8 |
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) |
Removing this via backend or MySQL has fixed the problem.
|
1 2 |
mysql> delete from eav_attribute where attribute_code = 'mp_meta_robots'; Query OK, 2 rows affected (0.01 sec) |
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.
|
1 2 3 |
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.
|
1 2 3 |
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 |
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.
|
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.
|
1 2 3 4 5 |
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.
Related issues:
https://github.com/magento/magento2/issues/5497
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.
|
1 2 3 |
$ 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.
|
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 |
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.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
<?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.
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.
|
1 |
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.
|
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
|
1 |
const XML_NODE_PRODUCT_MAX_DIMENSION = 'catalog/product_image/max_dimension'; |
and updated the method validateUploadFile().
|
1 |
public function validateUploadFile($filePath) { |
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.
|
1 |
mysql> DELETE FROM quote WHERE customer_email = 'customer@gmail.com'; |
Remove the WHERE clause to flush the quote for all customers.
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.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
<?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!'; } ?> |
Find the Gist here.