This repository has been archived by the owner on Mar 22, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 50
Magento 2.1.7 not getting correct urls #17
Comments
I received this reply to my email, but can't find from here, so it was:
I used this command: php bin/magento iazel:regenurl -s1 and changed the end to -s2 etc. for different shops. Still one shop only has broken urls and it's super frustrating (althought this should be fixed by Magento, not @iazel of course. |
Yep i deleted the comment since i noticed this was probably a different issue. Since i upgraded to 2.1.7 i had the issue that the plugin sets the URLs for the wrong scopes. I also use a modified Version of lazels module. What Kind of broken URL´s are you talking about by the way? I wouldnt call myself a magento specialist but maybe i can help.
Regards
Gesendet von Mail<https://go.microsoft.com/fwlink/?LinkId=550986> für Windows 10
Von: hellekim<mailto:[email protected]>
Gesendet: Donnerstag, 29. Juni 2017 18:27
An: Iazel/magento2-regenurl<mailto:[email protected]>
Cc: Culth<mailto:[email protected]>; Comment<mailto:[email protected]>
Betreff: Re: [Iazel/magento2-regenurl] Magento 2.1.7 not getting correct urls (#17)
I received this reply to my email, but can't find from here, so it was:
I think you have to set the product store id in all cases. At least this fixed the issue for me.
I used this command: php bin/magento iazel:regenurl -s1 and changed the end to -s2 etc. for different shops. Still one shop only has broken urls and it's super frustrating (althought this should be fixed by Magento, not @iazel<https://github.com/iazel> of course.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#17 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AL0hJWDHOnmLRnqPgAEBXYOcHuZajpkhks5sI9B2gaJpZM4OJYZv>.
|
OK - Thanks! My issue was down to Mageworx SEO extension which was messing with the URLs. Disabled that, run this and all was ok again. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I used this succesfully with 2.1.5, but with 2.1.7 nothing is changing when I run this code.
Any thoughts?
The text was updated successfully, but these errors were encountered: