Hello, I'm running Magento 2.3.6 with PHP 7.3. I have tried making sure the module is enabled. Other commands show up and work just fine. Any advice for me?

When the backend_type of an attribute changes (eg, from varchar to text), Magento will not clean up / migrate the data from the old table automatically. Extensions should do this as part of changing the backend_type, but not all extensions follow best practices. This pull request updates the SQL used to identify orphaned data to also detect data in the 'wrong' table.

When running bin/magento eav:media:remove-unused --dry-run, I see that the tool wants to remove placeholder images:

## WOULD REMOVE: /placeholder/default/photo-coming-soon3.jpg ##
## WOULD REMOVE: /placeholder/default/photo-coming-soon3_1.jpg ##
## WOULD REMOVE: /placeholder/default/photo-coming-soon3_2.jpg ##
## WOULD REMOVE: /placeholder/default/photo-coming-soon3_3.jpg ##

I would think we'd want to skip these, correct? Since they are referenced in core_config_data? If you agree, we can modify the console command class to skip /placeholder like you do /cache, as seen in \Hackathon\EAVCleaner\Console\Command\RemoveUnusedMediaCommand::execute:

    private function isInCachePath(?string $file): bool
    {
        return strpos($file, '/cache') !== false;
    }

If this makes sense to you, I can submit a PR, if needed.

When I ran: bin/magento eav:attributes:remove-unused --dry-run

I receive:

In Mysql.php line 599:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'ee.catalog_product_entity_static' doesn't exist, query was:
SELECT COUNT(*) FROM catalog_product_entity_static WHERE attribute_id = ?

In Mysql.php line 110:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'ee.catalog_product_entity_static' doesn't exist, query was:
SELECT COUNT(*) FROM catalog_product_entity_static WHERE attribute_id = ?

In Mysql.php line 91:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'ee.catalog_product_entity_static' doesn't exist

Hi, I ran it with --dry-run mode but it showed that it will delete all photos, not just those that are not in catalog_product_entity_media_gallery.

Magento 2.4.3-p1

The command "eav:attributes:remove-unused" does not show any images to be deleted. This is because Magento does not delete the deleted products from the catalog_product_entity_media_gallery table. The table now has more than 20000 entries, even though our store only has just under 4000 products. I found a similar error description here: https://magento.stackexchange.com/questions/238244/magento2-manage-and-understand-images-of-deleted-products-behavior

I am using Magento 2.3.7p3.

Does anyone have an idea what this is due to?

I added eav:media:remove-unused command to a cron due to how my Magento site adds products, it syncs up images nightly and wipes all product images with new ones. Magento leaves the old images on the hard disk so I want it to be cleaned up daily.

I added eav:media:remove-unused to a cron but because of the prompt I don't think it runs - I amended the vendor file to do this which works for me but am scared of it being overwritten in the future - hence the feature request! Otherwise I'll make a plugin to properly extend it.

protected function configure()
    {
        $this
            ->setName('eav:media:remove-unused')
            ->setDescription('Remove unused product images')
            ->addOption('dry-run')
			->addOption('force');
    }

  public function execute(InputInterface $input, OutputInterface $output): void
   {
       $fileSize   = 0;
       $countFiles = 0;
       $isDryRun   = $input->getOption('dry-run');
       $isForce   = $input->getOption('force');

       if (!$isDryRun && $input->isInteractive() && !$isForce) {

Adding a --force command would be useful for those who want this in a cron.

When reviewing this module for suitability and quality, I noticed a performance issue in the eav:attributes:restore-use-default-value command. When dealing with small databases, this inefficiency does not cost significantly; however, when working with large databases, this is causing significant delay within each loop iteration. This pull request resolves this inefficiency, allowing the command to run more quickly on all database sizes.

I recommend reviewing this with 'ignore white-space' enabled. I have tested this on Magento v2.4.3-p1.

When using a database prefix, the commands in this module do not work. This change allows the same to work. I've tested this on Magento version 2.4.3 with db/table_prefix set in app/etc/env.php

When running bin/magento eav:attributes:restore-use-default-value on a website with a large catalogue, PHP ran out of memory. This is because the command attempted to load all values into memory, however as only one row is processed at a time, replacing this with the resource iterator makes sense. With the changes in this pull request I am now able to use all commands on this website.

This pull request enhances the eav:config:restore-use-default-value command to also remove values from the database which match those set in etc/config.xml.

This fixes #7.

• Create a list of all product attributes from the database
• Search through the codebase to see whether they are mentioned in InstallData/UpdateData scripts - those are fine
• Search through phtml files to see whether they are used (also make sure to look for getAttributeName / setAttributeName instead of just attribute_name) - those are fine
• We should whitelist all core attributes since those have names that occur a lot ('name' / 'sku')
• The remaining product attributes might be removeable

This probably can't be done automatically since it'll most likely show too many false positives.

Maybe we should add a command that can identify which tables can be deleted from a Magento 2 install? I'm thinking it should do something like this;

• Whitelist all core Magento tables
• Run through the db_schema files and InstallSchema scripts of all extensions to identify table names
• Compare that list versus the tables actually in the database
• Interactively ask to drop that table (or generate queries to do it)