Magento

Download Magento 1 Extensions after M1 EOL

Magento 1 extensions were removed from https://marketplace.magento.com about a month ago. According to Adobe’s recent blog posts, all extensions will be removed early August from their repository, which causes a lot of frustration on developers who are still in the middle of moving towards Magento 2 or simply need the code to translate it into Magento 2 modules.

July 7, 2020 – Removal of all M1 extension listings from marketplace.magento.com. Extension will be available on repo.magento.com until 8/6/2020.
August 6, 2020 – Removal of M1 extensions from repo.magento.com

1 2	July 7, 2020 – Removal of all M1 extension listings from marketplace.magento.com. Extension will be available on repo.magento.com until 8/6/2020. August 6, 2020 – Removal of M1 extensions from repo.magento.com

Source: https://community.magento.com/t5/Magento-DevBlog/How-Extension-Developers-Can-Prepare-for-M1-End-of-Life/ba-p/446216

We encourage Magento 1 merchants to download the Magento 1 extensions they plan to keep, since Magento 1 extensions will not be available in the Magento Marketplace after July 7, 2020, and will be removed from the Magento repository after August 6, 2020.

1	We encourage Magento 1 merchants to download the Magento 1 extensions they plan to keep, since Magento 1 extensions will not be available in the Magento Marketplace after July 7, 2020, and will be removed from the Magento repository after August 6, 2020.

Source: https://magento.com/blog/magento-news/support-magento-1-software-ends-june-30-2020

So, in order to download an M1 package, you simply have to point to a specific URL. Luckily they didn’t turn off https://connect20.magentocommerce.com yet, but I believe Magento will get rid of it very soon.

https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz

1	https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz

I’ve spent a few minutes writing a ” quick and dirty ” PHP script that downloads the most recent version of each extension in https://connect20.magentocommerce.com/community/packages.xml including package details such as name, description, and author. For example https://connect20.magentocommerce.com/community/BankPayment/1.2.0/package.xml

<?xml version="1.0"?>
<package>
    <name>BankPayment</name>
    <version>1.2.0</version>
    <stability>stable</stability>
    <license uri="http://opensource.org/licenses/osl-3.0.php">OSL</license>
    <channel>community</channel>
    <extends/>
    <summary>Vorkasse - Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</summary>
    <description>Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</description>
    <notes>IBAN ready&#xD;
Allow partial capturing&#xD;
Localization improvements</notes>
    <authors><author><name>Phoenix Media GmbH</name><user>PHOENIX</user><email>bjoern.kraus@phoenix-media.eu</email></author></authors>
    <date>2017-09-05</date>
    <time>11:08:47</time>
    <contents><target name="magecommunity"><dir name="Phoenix"><dir name="BankPayment"><dir name="Block"><dir name="Adminhtml"><file name="BankAccount.php" hash="80df5881081ded22b182ac2bde3b0a3e"/>$
    <compatible/>
    <dependencies><required><php><min>5.2.0</min><max>7.0.22</max></php><extension><name>Core</name><min/><max/></extension></required></dependencies>
</package>

<?xml version="1.0"?>

<name>BankPayment</name>

<stability>stable</stability>

<channel>community</channel>

<summary>Vorkasse - Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</summary>

<description>Bank Prepayment module which notifies the buyer to which bank account he has to transfer the money.</description>

<notes>IBAN ready

Allow partial capturing

Localization improvements</notes>

<authors><author><name>Phoenix Media GmbH</name><user>PHOENIX</user><email>bjoern.kraus@phoenix-media.eu</email></author></authors>

<contents><target name="magecommunity"><dir name="Phoenix"><dir name="BankPayment"><dir name="Block"><dir name="Adminhtml"><file name="BankAccount.php" hash="80df5881081ded22b182ac2bde3b0a3e"/>$

</package>

If you download all packages, you will end up with about 1300 extensions.

├── zoe_myzoe
│   ├── Zoe_Myzoe--package.xml
│   └── Zoe_Myzoe-.tgz
├── zoe_myzoe-1.0.0
│   ├── Zoe_Myzoe-1.0.0--package.xml
│   └── Zoe_Myzoe-1.0.0-.tgz
├── zopim_live_chat
│   ├── Zopim_Live_Chat-0.5.4-package.xml
│   └── Zopim_Live_Chat-0.5.4.tgz
└── zubibu
    ├── zubibu-1.0.0-package.xml
    └── zubibu-1.0.0.tgz

1359 directories, 2716 files

├── zoe_myzoe

│ ├── Zoe_Myzoe--package.xml

│ └── Zoe_Myzoe-.tgz

├── zoe_myzoe-1.0.0

│ ├── Zoe_Myzoe-1.0.0--package.xml

│ └── Zoe_Myzoe-1.0.0-.tgz

├── zopim_live_chat

│ ├── Zopim_Live_Chat-0.5.4-package.xml

│ └── Zopim_Live_Chat-0.5.4.tgz

└── zubibu

├── zubibu-1.0.0-package.xml

└── zubibu-1.0.0.tgz

1359 directories, 2716 files

However, it seems the packages.xml file contains a lot of extensions that are actually not available anymore, that leads to a 404.

PHP Warning:  file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/SUMOHeavy_Coupons-1.1.0.tgz): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
 in /var/www/extensions/index.php on line 41
PHP Warning:  file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/package.xml): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
 in /var/www/extensions/index.php on line 50

PHP Warning: file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/SUMOHeavy_Coupons-1.1.0.tgz): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found

in /var/www/extensions/index.php on line 41

PHP Warning: file_get_contents(https://connect20.magentocommerce.com/community/SUMOHeavy_Coupons/1.1.0/package.xml): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found

in /var/www/extensions/index.php on line 50

Another good resource is https://packages.firegento.com or http://freegento.com/ddl-magento-extension.php to download M1 extensions.

<?php
/**
 * Connect20
 *
 * @category    Connect20
 * @author      Tobias Forkel (http://tobias.forkel.me)
 * @license     http://opensource.org/licenses/osl-3.0.php Open Software License (OSL 3.0)
 */

$packagesUrl = 'https://connect20.magentocommerce.com/community/packages.xml';
$releasesUrl = 'https://connect20.magentocommerce.com/community/%extKey%/releases.xml';
$packageUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/package.xml';
$downloadUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz';
$packages = implode('/', [dirname(__FILE__), 'packages.xml']);

// Cache packages.xml file
if (!file_exists($packages)) {
    file_put_contents($packages, file_get_contents($packagesUrl));
}

$packages = simplexml_load_file($packages);

foreach ($packages as $data) {

    $extKey = (string)$data->n;
    $stable = (string)$data->r->s;
    $beta = (string)$data->r->b;

    $version = (!empty($stable)) ? $stable : $beta;

    if (empty($version)) {

        echo sprintf('Skipped ( %s )', $extKey);
        echo PHP_EOL;
        
        continue;
    }

    $folder = implode('/', [dirname(__FILE__), 'data', strtolower($extKey)]);

    // Create extension folder
    if (!file_exists($folder)) {
        mkdir($folder, 0777, true);
    }

    $download = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $downloadUrl);
    $downloadPath = implode('/', [$folder, basename($download)]);

    // Skip downloaded files
    if (file_exists($downloadPath)) {
        continue;
    }

    // Download the *.tgz file ( stable or beta )
    if (file_put_contents($downloadPath, file_get_contents($download))) {

        echo $download;
        echo PHP_EOL;
    }

    // Download content ( e.g description, author etc. ) from package.xml
    $package = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $packageUrl);

    if (file_put_contents(implode('/', [$folder, $extKey . '-' . $version . '-' . basename($package)]), file_get_contents($package))) {

        echo $package;
        echo PHP_EOL;
    }
}

?>

<?php

/**

* Connect20

* @category Connect20

* @author Tobias Forkel (http://tobias.forkel.me)

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

$packagesUrl = 'https://connect20.magentocommerce.com/community/packages.xml';

$releasesUrl = 'https://connect20.magentocommerce.com/community/%extKey%/releases.xml';

$packageUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/package.xml';

$downloadUrl = 'https://connect20.magentocommerce.com/community/%extKey%/%version%/%extKey%-%version%.tgz';

$packages = implode('/', [dirname(__FILE__), 'packages.xml']);

// Cache packages.xml file

if (!file_exists($packages)) {

file_put_contents($packages, file_get_contents($packagesUrl));

}

$packages = simplexml_load_file($packages);

foreach ($packages as $data) {

$extKey = (string)$data->n;

$stable = (string)$data->r->s;

$beta = (string)$data->r->b;

$version = (!empty($stable)) ? $stable : $beta;

if (empty($version)) {

echo sprintf('Skipped ( %s )', $extKey);

echo PHP_EOL;

continue;

}

$folder = implode('/', [dirname(__FILE__), 'data', strtolower($extKey)]);

// Create extension folder

if (!file_exists($folder)) {

mkdir($folder, 0777, true);

}

$download = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $downloadUrl);

$downloadPath = implode('/', [$folder, basename($download)]);

// Skip downloaded files

if (file_exists($downloadPath)) {

continue;

}

// Download the *.tgz file ( stable or beta )

if (file_put_contents($downloadPath, file_get_contents($download))) {

echo $download;

echo PHP_EOL;

}

// Download content ( e.g description, author etc. ) from package.xml

$package = str_replace(['%extKey%', '%version%'] ,[$extKey, $version], $packageUrl);

if (file_put_contents(implode('/', [$folder, $extKey . '-' . $version . '-' . basename($package)]), file_get_contents($package))) {

echo $package;

echo PHP_EOL;

}

Feel free to change or share the code.

Update composer.lock without updating code

Recently I had to fix a broken composer.lock but without actually updating code. I have found the composer option ” nothing ” which updates the composer.lock file only.

$ composer update nothing

1	$ composer update nothing

Once the command ran successfully, you should see a line ” Writing lock file ” in the output.

$ composer update nothing
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Writing lock file
Generating autoload files

$ composer update nothing

Loading composer repositories with package information

Updating dependencies (including require-dev)

Nothing to install or update

Writing lock file

Generating autoload files

If you have issues with dependencies you can update the composer.lock file with –ignore-platform-reqs.

$ composer update nothing --ignore-platform-reqs

1	$ composer update nothing --ignore-platform-reqs

Missing required argument $name of Xtento\ProductExport\Logger\Logger.

If you are using Xtento in combination with an automated product importer, you may have seen the following error before.

Missing required argument $name of Xtento\ProductExport\Logger\Logger.

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.

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) {

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.

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

Query to get size of database tables in MB

If your hosting environment has no database monitoring, you should be able to monitor it manually once in a while or with your own shell script to prevent rapidly growing MySQL tables, because the result of large MySQL tables ( I am talking about 2 – 10 GB with millions of rows ) are often random performance issues, especially if you are using community modules with not well written MySQL queries.

SELECT TABLE_NAME, table_rows, data_length, index_length,
round(((data_length + index_length) / 1024 / 1024),2) "Size in MB"
FROM information_schema.TABLES WHERE table_schema = "{{{YOUR_DATABASE}}}"
ORDER BY (data_length + index_length) DESC;

SELECT TABLE_NAME, table_rows, data_length, index_length,

round(((data_length + index_length) / 1024 / 1024),2) "Size in MB"

FROM information_schema.TABLES WHERE table_schema = "{{{YOUR_DATABASE}}}"

ORDER BY (data_length + index_length) DESC;

This is the output of the query.

| enterprise_logging_event                      |     122389 |    15939572 |      3270656 |      18.32 |
| catalog_product_index_eav                     |     324014 |     4212182 |     18053120 |      21.23 |
| log_visitor_info                              |     182838 |    19706548 |      3599360 |      22.23 |
| catalog_product_index_eav_idx                 |     324014 |     4522245 |     21139456 |      24.47 |
| catalog_product_entity_varchar                |     255303 |    10852180 |     15244288 |      24.89 |
| log_url                                       |     228886 |    10966704 |     15636480 |      25.37 |
| log_url_info                                  |     228886 |    80258352 |      7542784 |      83.73 |
| enterprise_logging_event_changes              |      69184 |   160619752 |      1499136 |     154.61 |
+-----------------------------------------------+------------+-------------+--------------+------------+
586 rows in set (0.05 sec)

| enterprise_logging_event | 122389 | 15939572 | 3270656 | 18.32 |

| catalog_product_index_eav | 324014 | 4212182 | 18053120 | 21.23 |

| log_visitor_info | 182838 | 19706548 | 3599360 | 22.23 |

| catalog_product_index_eav_idx | 324014 | 4522245 | 21139456 | 24.47 |

| catalog_product_entity_varchar | 255303 | 10852180 | 15244288 | 24.89 |

| log_url | 228886 | 10966704 | 15636480 | 25.37 |

| log_url_info | 228886 | 80258352 | 7542784 | 83.73 |

| enterprise_logging_event_changes | 69184 | 160619752 | 1499136 | 154.61 |

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

586 rows in set (0.05 sec)

Table is marked as crashed and should be repaired

Don’t freak out if your Magento is not working and because of the following error message.

SQLSTATE[HY000]: General error: 145 Table './magento/log_visitor_info' is marked as crashed and should be repaired

1	SQLSTATE[HY000]: General error: 145 Table './magento/log_visitor_info' is marked as crashed and should be repaired

The reason of a crashed MySQL table is mostly related to a server issue. For example:

Any kind of hard-disk failure
Sudden server reboot (power outage in hosting)
Hard server reboot (ACPI shutdown)

In most cases you can repair the affected table with a simple repair command, which comes with MySQL.

mysql> repair table log_visitor_info;
+-----------------------+--------+----------+----------+
| Table                 | Op     | Msg_type | Msg_text |
+-----------------------+--------+----------+----------+
| magento.log_visitor_info | repair | status   | OK       |
+-----------------------+--------+----------+----------+
1 row in set (0.54 sec)

mysql> repair table log_visitor_info;

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

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

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

1 row in set (0.54 sec)

This command looks pretty easy and safe, but keep in mind that you should always create a backup before you change anything in your database, because probably more MySQL tables are affected.