-
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
M2.1: Not scrollable picture on mobile / product page #5302
Comments
I think this is really an important bug stopping users to shop mobile at all so it needs to be reviewed here pls. |
@ilol can you pls have a look on this. i think it is really important as it is a total conversion blocker for mobile users! thanks! |
Thank you @andidhouse , registered to fix MAGETWO-55608 |
Please fix this, its a major issue on our site as the image spans 100% width. |
+1 |
Here is a workaround for this bug which solves the problem.
|
Has this been fixed? This is a pretty big issue for mobile shoppers. The workaround does not seem to work on 2.1.1 rendering Magento pretty useless on a good number of mobile devices. |
If you take a look at the default luma and blank theme this bug doesn't seem to have an impact on them. It rears its head on custom themes and is very present on several live sites I have looked at running CE. |
3 month later without an official bugfix of a major bug... i really do not know what is going on on magento side... |
It's pretty obvious, CE is not in the future. |
Development completed. So we are merging this into mainline and older versions. |
Thanks for responding, if your able to provide a date, when will we be able to utilize this, and how? |
Bug MAGETWO-56699 [GITHUB] Paypal checkout not possible with products that have custom options #5938 - for mainline MAGETWO-58290 [Github]Empty product option is added on each PUT request #5963 MAGETWO-58136 [Github] Shipping and billing address are not set if order placed with payment action Sale #6438 MAGETWO-55608 [GITHUB] M2.1: Not scrollable picture on mobile / product page #5302 MAGETWO-58285 Ajax error message doesn't display in backend MAGETWO-58338 [Github]Problem adding attribute options that start with a number via REST Api #5715 MAGETWO-52575 Unable to apply free shipping to specified method when creating order in admin MAGETWO-57078 [GITHUB] Can't set customer group when creating a new order in the admin. #6162 MAGETWO-58039 Table rate shipping not applying correctly - for mainline
Fix of MAGETWO-55608 is delivered to develop branch. Closing the issue. |
I have test site with v2.1.1 and am having the same problem with Luma and sample data installed. |
@PaperDS the fix is available in the developer branch, you could grab it from there and add it to your current install. |
still seems to be an issue in the version released today, 2.1.2 |
Yes, I can confirm the fix isn't in 2.1.2. Not sure why.... |
So will this issue be reopened? |
@PaperDS Currently Magento 2.X.X has hundreds of issues. So far every release comes with fixes for 5-10 of those issues plus new ones of the specific release.
|
Are there as many issues with EE? |
@jupiter01 I don't know really (i'm not a Magento employee). My previous comment is based on my experience so far using Magento 2 CE and the number of issues reported already in github by the community. |
Suffering from the same issue. @piotrekkaminski @elenleonova @pboisvert |
Applying the 7597a52 commit as a patch (add .patch to the end of that url to get a patch file) to my environment fixed the issue for me. |
After updating the following files, the patch is still not working. |
Did anyone find a solution? |
Hi all, after some reviews, as I'm a very noobie to magento.
And this should work. At least it did for me! More info about M2 command line here: http://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands.html |
Sorry, I'm noobie (a lot) too, how to install the patch? @yofisim |
You will find the files to replace (and the exact lines that have been changed) here: Replace them, then go for the few commands I gave you. Good luck 💯 |
Unfortunately, I did everything exactly as you suggested me... But it still doesn't work :( @yofisim |
@giusecapo on your browser, when you're on the product page, check the fotorama.js file the browser process to see if you have inserted the correct files and did the right manipulation |
You're right, page is loading fotorama.js from pub/static/... Do you know why? Should I clear static files again? @yofisim |
Ok! It works! Thanks for your help, maybe I called deploy static content before ftp finished upload :) You made my day man @yofisim |
@giusecapo Report again to these files here: 7597a52 and check the changes @ |
Ow nice! thumb up! Have a nice dev day @giusecapo |
@jmtakahashi please provide more infos as I tried to reproduce your issue
and didn't succeed. Patch is working fine from my side.
…On Mon, 5 Dec 2016 at 7:39 jmtakahashi ***@***.***> wrote:
@ilol <https://github.com/ilol> @yofisim <https://github.com/yofisim>
note that this fix works on initial page load, but on reload (refresh) it
does not work. on reload, first image in the slider will react to up and
down scrolling, but on 2nd image or 3rd image (any image after first), the
scrolling issue persists.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5302 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE-POZXpSxYGfvdvJsLnRtLayWYyU643ks5rE6OPgaJpZM4I_zKV>
.
|
Device: Magento 2.1.2 (i'm including these because the JS merge, minify and bundle are problems in themselves when set to on) 1.) Click to an individual product page from any page. Hope this helps. I'm not sure whether the Private Browsing mode has anything to do with it, but reloading the page (today) once, and it still worked. Then the 2nd time reloading it stopped working again. |
@jmtakahashi dis you emulate on your browser in Desktop? Can you please
check the console to retrieve the error that is triggered when the
scrolling doesn't work.
It's a very weird issue and I believe it comes from elsewhere in the code.
Maybe you can provide URL?
…On Tue, 6 Dec 2016 at 8:10 jmtakahashi ***@***.***> wrote:
@yofisim <https://github.com/yofisim>
Device:
a.) iphone 6s
b.) private browsing mode
Magento 2.1.2 (i'm including these because the JS merge, minify and bundle
are problems in themselves when set to on)
a.) Minify, Bundle, Merge JS: ALL OFF
b.) Merge and Minify CSS: ON
c.) Minify Html: OFF
1.) Click to an individual product page from any page.
2.) Check slider (all images), and check scrolling. It will work.
3.) Reload the individual product page a few times.
4.) Check slider (default first image), scrolling will work with first
image.
5.) Slide to 2nd or 3rd image, scrolling up and down while finger is over
the image stops working.
Hope this helps. I'm not sure whether the Private Browsing mode has
anything to do with it, but reloading the page (today) once, and it still
worked. Then the 2nd time reloading it stopped working again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5302 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE-POSpA0eheNnrBd-ZKZKGirHoL-Lyrks5rFPw7gaJpZM4I_zKV>
.
|
@yofisim this was tested on an actual phone. https://vizume.com Any product image does the same thing. |
we give it up on the native photorama implementation due to:
Magic zoom works like a charm and has a great support fixing bugs in minute not years. |
The issue has been delivered to 2.1.3 |
i can confirm this is fixed n 2.1.3 |
Its not fixed on Chrome on ios iphone. Its fixed in Safari. |
@erik-augustin just rechecked. It's fixed on both for me. |
[TSG-CSL3] For 2.4 (pr3)
Steps to reproduce
Expected result
Actual result
This issue appeared on early magento2 versions and was fixed then. Now it is there again and it is important. I do not know if this issue just happens when no product picture is uploaded and placeholder is shown or if this happens also with a product picture uploaded.
Anyway - this needs to be fixes asap as this is a massiv blocker for users.
The text was updated successfully, but these errors were encountered: