Product CSV import error report file missing

[engcom-Charlie]

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Product CSV import error report file missing #28420

Manual testing scenarios (*)

See #28420

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Charlie. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

[engcom-Charlie]

@magento run all tests

[eduard13]

Thank you for the fix ✔️

[magento-engcom-team]

Hi @eduard13, thank you for the review.
ENGCOM-7616 has been created to process this Pull Request

[engcom-Alfa]

✔️ QA Passed

Manual testing scenario:

Import a product CSV which will generate errors like a not existing path to an image

Before: ✖️ file is generated, but will be removed after the application ends.

After: ✔️ An error_report.csv file with the errors generated in the import.

[m2-assistant]

Hi @engcom-Charlie, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

[theCapypara]

Hi, any chance you could also provide this for 2.3?

[RaphaelBronsveld]

diff --git a/Model/Export/Adapter/Csv.php b/Model/Export/Adapter/Csv.php
index 580695d0..085d24ca 100644
--- a/Model/Export/Adapter/Csv.php
+++ b/Model/Export/Adapter/Csv.php
@@ -55,6 +55,19 @@ class Csv extends AbstractAdapter
     {
         if (is_object($this->_fileHandler)) {
             $this->_fileHandler->close();
+            $this->resolveDestination();
+        }
+    }
+
+    /**
+     * Remove temporary destination
+     *
+     * @return void
+     */
+    private function resolveDestination(): void
+    {
+        // only temporary file located directly in var folder
+        if (strpos($this->_destination, '/') === false) {
             $this->_directoryHandle->delete($this->_destination);
         }
     }

Patch above works fine for us at version 2.3.5-p1.