Magento2: After import products categoty URL rewrites removes automatic

[adoardo]

1. I have Magento CE 2.1.
2. "Use Categories Path for Product URLs" is enabled.
3. "Create Permanent Redirect for URLs if URL Key Changed" is enabled.
4. If i save category from admin page manually, url rewrites works. But if i import products after this i still have this issue.
5. As i understood problem with "Magento\CatalogUrlRewrite\Observer\AfterImportDataObserver" observer because there is no basc functionality to add new category rewrites. But i dont understand why this observer removes exiting category rewrites.

[hostep]

Ah yes, I've seen this behavior as well in the past during category/product imports.
We work around it by re-inserting url rewrites after the import using some custom code, but during the import certain url rewrites are being removed, so people browsing the webshop during an import will see non-seo friendly url's popping up here and there.

If I remember correctly, this only seemed to happen when we do a product import where we only import stock qty and prices. We don't import a name or url_key, since it already exists in Magento. I think the lack of those attributes in the import data, might have something to do with this problem.

Would be great if Magento can look into this, because disappearing url rewrites aren't very fun to deal with.

[andidhouse]

@hostep not really shure what the logic is on handling bugs from magento side. If you browse GitHub or even google for the "Magento2 URL Rewrite bug" you find hundreds of posts and problems. Right now also this issue was posted far more then one year ago here - nothing happened from magento side. The bug is still present and there is no reaction from magento side but creating pull requests or creating internal tickets. Is this really how you handle bugs? wow...

[christian-forgacs]

PUSH!

[magento-engcom-team]

@adoardo , thank you for your report.
Please provide more detailed steps to reproduce or try to reproduce this issue on a clean installation or latest release.
Please, add the following information:

• [ ] Magento version
• [ ] Steps to reproduce
• [ ] Expected result
• [ ] Actual result

[magento-engcom-team]

@adoardo, we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.

[rigroweb]

This is definetely still an issue and can be easily reproduced. please reopen.

[hostep]

@rigroweb: it might be better to open a new issue detailing exact steps to reproduce, commenting on old already-closed issues usually has no effect (especially since most contributors - like myself - no longer have the rights to re-open issues for some reason)

[rigroweb]

Thank you. I will do exactly that.

On Thu, Jun 25, 2020 at 12:15 PM Pieter Hoste [e-mail]
wrote:

@rigroweb
https://mailtrack.io/trace/link/54a46c3a4569dc436c200dad255edf22da7f7df5?url=https%3A%2F%2Fgithub.com%2Frigroweb&userId=4761662&signature=ee6228a9dcb33962:
it might be better to open a new issue detailing exact steps to reproduce,
commenting on old already-closed issues usually has no effect (especially
since most contributors - like myself - no longer have the rights to
re-open issues for some reason)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://mailtrack.io/trace/link/a37bc2a34d14b0ec9b71d94076d9e572d9adde5f?url=https%3A%2F%2Fgithub.com%2Fmagento%2Fmagento2%2Fissues%2F8786%23issuecomment-649668177&userId=4761662&signature=360a1bfe82f8b20f,
or unsubscribe
https://mailtrack.io/trace/link/0c6c0b276ad62097084f3afb95a23c573cbb2e52?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOR23HHJ2HQQR3DISABZSYTRYNZ3HANCNFSM4DCKRYPA&userId=4761662&signature=1d2f96586cdf4c62
.