-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can it generate URI by url_key during importing? #43
Comments
Here is my workaround (import is done with an external script):
It's a little dirty because it reindex the URL for all categories, but you could select only the imported categories. |
Hello VincentMarmiesse, I recently added this feature to the master branch. Its in the commit e14bfdc Feel free to try it out. Greetings |
Hello @EliasKotlyar, Can I get this update via Composer? It tells me there is no update. Thanks! |
@EliasKotlyar: just curious: did you test it out with categories having different url_key's in different storeviews? Because we ran into a bunch of core Magento2 bugs a couple of months ago, when we were trying to do something similar. For example: we sometimes got the error 'URL key for specified store already exists', or we ran into this: magento/magento2#8396 (I just see a couple of very recent commits referenced at the bottom which should fix it, but not tested yet) |
Hello everyone, @VincentMarmiesse : Please have a look at this Page : You will find some instructions how to install the development Version @hostep : I personally havent tried it, because i didnt had such requirements yet. But i heard of some problems with the urls which can be actually solved using following "Core-Hack"(you can actually turn it into a Plugin): vendor/magento/module-catalog-url-rewrite/Model/CategoryUrlPathGenerator.php Insert "$category->setStoreId($storeId);" into the method: ` ` |
I have been able to get the latest version by using |
It looks like it saves url_key during the import but it cannot generate an URI properly.
It was found for categories.
The text was updated successfully, but these errors were encountered: