-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Issue with multi website URL #7815
Comments
i have same problem , i got 2 domains that ref to deterrent store views be .htaccess i also try to follow the guide : http://devdocs.magento.com/guides/v2.0/config-guide/multi-site/ms_over.html |
We are using Apache server. This issue occurs after upgrade from 2.1.2=>2.1.3 |
I have same problem. After upgrade to 2.1.3, I can't use multiple domain name for store view scope. |
Hello, It looks like magento does not note at my /etc/httpd/....../.conf file the following lines: Maybe the variables changed? Also everybody please note that the update overrides the .htaccess. My mod deflate options were lost and I had to insert them again. |
My guess, here is a related issue #7840 |
Same issue any news about ? |
Need to confirm if this is really a Magento 2.1.3 bug because two sumdomains are down afther upgrading from from 2.1.2 to 2.1.3 just works fine in main domain. |
Do you think best solution is revert to Magento 2.1.2 ? or maybe this bug will be fixed early in future 2.1.4 release. |
I reverted to 2.1.2 |
So did I. I'm trying to dig around and see where the breaking code is. I'll keep you posted. |
I'd rather wait because I just made some changes to some extensions installed to be compatible with magento 2.1.3 and if I revert then will be lost. |
Guys, please check workaround here #7840 and tell if it works for you. This fixed the configuration retrieving from the website scope for me. |
Fixed with @alexpoletaev help. |
Thanks to @alexpoletaev @salelsol |
@Yunus260 You must modify .htaccess when you install magento 2.1.3 afther run: php bin/magento setup:upgrade |
I experienced this issue after upgrading a multi-website install from 2.1.2 to 2.1.3. I had my "Base Url" and "Secure Base Url" values configured at the Website scope. I switched the values to be stored at the Store View scope, and that fixed my problem. |
@salelsol I still do not understand what you mean with "You must modify .htaccess.." |
@Yunus260 Your .htaccess start with this line ? All explanations you could find in .htaccess.sample fileIf Yes you are Magento 2.1.3 .htaccess file right |
Yunus260 Magento 2.1.3 .htaccess started : All explanations you could find in .htaccess.sample fileDirectoryIndex index.php |
@salelsol I used the Admin-Backend to upgrade from 2.1.2 to 2.1.3 and that upgrade has updated my .htaccess, like mentioned above. Thats why I wrote " I haven't modified anything and it worked." |
@Yunus260 I use ssh command line to upgrading all new Magento versions and then I must manually add properly line to redirect to subdomains. I this version .htaccess is quite different from previous version so I have referred to that .htaccess file. |
Hi @netzweltvimal, this issue was fixed under MAGETWO-62648 in 2.1.4, that's why I closed it. If you have additional questions or info please feel free to reopen this one or create a new one. |
I know I have an old version but I have the same issue in version 2.1.18. |
Preconditions
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: