-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Responsive Design Issue on Mobile with Magento 2.1.9 #10941
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
Comments
@rishabhchd19, thank you for your report. |
I have this as well @magento-engcom-team. Did you test it on an Android Device like he specified? Version 2.1.5 |
You can please visit the website at catalogue.yogdiagnostics.com and can check yourself. I am getting the problem on each n every mobile device except iPad, iPhone(i didn't check), Laptop and Desktop. |
@rishabhchd19, thank you for your answer. |
@rishabhchd19, thank you for your response. |
Content>Widget
|
layout update xml.txt |
@rishabhchd19, thank you for your report. |
I'm working on it #SQUASHTOBERFEST |
@rishabhchd19 I'm trying to reproduce the issue on a clean installation with sample data.
The page layout is "2 Columns with left sidebar", is it right?
but the result is:
Are you sure that the layout update is the same you are using? |
I've removed this block
from the layout update and now i can render the page and the result is: This can be easily fixed |
@slackerzz Yes, it is 100% sure that I am using the same layout update reason being it is showing Navigation layer on adding that container. And removing that block is actually removing the Navigation layer. Also, you can notice that by removing the Navigation Layer as Shop By option not resolving the other issues. It would be good if users would able to use Navigation Layer by this block...Is it there any other Layout update that getting back the Navigation Layer properly? |
Also, it has started showing Show X per page at top and bottom of the main block...twice on the page after updating to 2.2.0 |
Internal ticket to track issue progress: MAGETWO-81986 |
Hi @rishabhchd19 the issue has been fixed and delivered to 2.2-develop branch and will be available with 2.2.2 release soon |
yaaaaaaay!!!! will be waiting for it to be released |
Hi @rishabhchd19. Thank you for your report.
The fix will be available with the upcoming patch release. |
Problem is still there.
…On Tue, Jan 30, 2018 at 5:35 AM, Magento Community Engineering < ***@***.***> wrote:
Hi @rishabhchd19 <https://github.com/rishabhchd19>. Thank you for your
report.
The issue has been fixed in magento-engcom/magento2ce#1283
<https://github.com/magento-engcom/magento2ce/pull/1283> by
@magento-engcom-team <https://github.com/magento-engcom-team> in
2.3-develop branch
Related commit(s):
- 0742857
- fde512e
- e7d90de
- 6d4f36d
- 2e83a36
- 23b4aa1
- b50bfa8
- 04cd60d
- 75d5a05
- 5e02b15
- aad5ba6
- 3e32140
- 7898946
- a173e1c
- 41d0075
- dda19b2
- cba48cd
- 0c62caa
- 736f783
- 7569b70
The fix will be available with the upcoming patch release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10941 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Adg8bZEAKSWXO6UTgM6BmMepXej9KsT0ks5tPlzggaJpZM4PaWf6>
.
|
Problem is still there as you can see in the attachment.
…On Tue, Jan 30, 2018 at 5:35 AM, Magento Community Engineering < ***@***.***> wrote:
Hi @rishabhchd19 <https://github.com/rishabhchd19>. Thank you for your
report.
The issue has been fixed in magento-engcom/magento2ce#1283
<https://github.com/magento-engcom/magento2ce/pull/1283> by
@magento-engcom-team <https://github.com/magento-engcom-team> in
2.3-develop branch
Related commit(s):
- 0742857
- fde512e
- e7d90de
- 6d4f36d
- 2e83a36
- 23b4aa1
- b50bfa8
- 04cd60d
- 75d5a05
- 5e02b15
- aad5ba6
- 3e32140
- 7898946
- a173e1c
- 41d0075
- dda19b2
- cba48cd
- 0c62caa
- 736f783
- 7569b70
The fix will be available with the upcoming patch release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10941 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Adg8bZEAKSWXO6UTgM6BmMepXej9KsT0ks5tPlzggaJpZM4PaWf6>
.
|
I have added below code on above "Bucket does not exist" condition. Because we are showing subcategories on main category pages. So we don't need filters.
|
hi @samanaveen .I have added above code \vendor\magento\module-catalog-search\Model\ResourceModel\Fulltext\Collection.php above below line
|
Preconditions
Magento 2.1.7, 2.1.8, 2.1.9, php 5.6
Steps to reproduce
Open frontend on mobile device (Android)
Expected result
Expected that the
Shop By
is positioned correctly and nothing positioned incorrectly as shown in the screenshots.Actual result
The
Shop By
and other contents positioned incorrectly and it happens only at the landing page i.e. the Main Page. It shows correctly andShop By
tab comes to correct position when any category or subcategory is selected as shown in the last image.Everything showing OK on iPad, Laptop and Desktop website...having an issue on mobile layout.
The text was updated successfully, but these errors were encountered: