Hey @civilvicky
It is not possible to detect if a device is actually a tablet, laptop, smartphone, desktop, etc.
What the plugin can do, is detect the user’s screen size, and then decide if a block needs to be sticky or not. To do that, enter a value in the “Block should not be sticky if the screens smaller than” setting:
Image link: https://d.pr/i/usnsqg
If you enter 1024 there, it means that the block will be sticky on screens that are wider than 1024 (mostly laptops, and tablets), and if the screen is smaller than that (mostly smartphones), it will not be sticky.
There’s no “magic” number here to use. Some smartphones are quite big, and some tables are quite small, so if you would use a number like 800, it’s possible that large smartphones will show it as sticky, and small laptops won’t, but you’ll have to experiment a bit with that.
Looks great! Glad to see it worked out. 🙂
Hey @stefank1
Sorry for the (ridiculously long) delay! If I understand correctly, you want the image (on the left) to be sticky, until you scroll down to a certain point and then if you continue scrolling, it should go away.
If that’s what you mean, then you can accomplish that by selecting a pushup element in the settings. If that element scrolls into view, it will then push the sticky element up again. Please let me know if that’s what you meant!
Hey @wizardry
Thanks for your suggestion! Interesting request — I’ll see if I can include this in the next update.
Hey @hblecher
I would continue to use pixels, except this will have negative effects on mobile, so I’d like to use percentages — and vh and vw don’t seem to work consistency across platforms either. Is this to do with the fact that the sticky is using js instead of pure css to stay sticky?
I’m not entirely sure what you mean here, but if you’re referring to the “space between sticky block and top of screen”, that can indeed only use pixels. Or are you talking about something else?
If you can share the link to an example page where you have this set, that may help to clarify it a bit more as well. 🙂
Hey @wenmedics
Can you tell us a bit more about this error message? When/where do you see this exactly?
Also, please share a copy of your site’s System Status Report — you can find it by going to your admin Dashboard and select WooCommerce → Status.
From there, select “Get system report” and then “Copy for support”. Once you’ve done that, you can paste it here in your response.
Hey @soylaostia
If you can share a link to your site, we can take a look and see what might be wrong here.
Hey @hblecher
In the settings for the Sticky Block, try setting the Z-index value to 4 or higher.
Hi @joselbabq
To fix this, please try the following:
1. Go to Apple Pay management in Stripe dashboard.
2. Remove the existing Apple Pay domain
3. Add it again inside the dashboard
Hope this helps!
Hey @joannaritsoni
That should be , (a comma) indeed. 🙂
Hey @veneetsayyer11
It looks like this may be caused due to a theme conflict, or possibly a third-party plugin (I’m suspecting Payment Gateways per Products for WooCommerce might be related, but it could be any other one). I’d recommend the conflict-testing steps here to isolate the source of the issue:Â https://docs.woocommerce.com/document/how-to-test-for-conflicts/
The best way to determine if the issue is being caused by a theme and/or plugin is to do the following:
– Temporarily switch your theme back to a default theme, such as Storefront.
– Disable all plugins, except for WooCommerce and your payment gateway.
– Clear your browser cache, and the cache on your site if you have one there.
– Test to see if the issue has been resolved.
If that resolves the issue, then one-by-one you can switch back your theme and re-enable your plugins, testing in between, until the problem appears again. This will then give you an idea about which plugin is the one causing the conflict.
Since these tests will impact the look and functionality of the site, we strongly recommend using a staging site where you can do your testing.
If you don’t already have a staging site set up, check with your hosting company as many offer this as part of their packages. Otherwise, you can use a free plugin such as WP Staging to set one up.
Hey @warakaku
The red square indicates there is an issue that is preventing you from checking out to begin with. I would suggest to do a conflict test to see what might be the issue.
The best way to determine if the issue is being caused by a theme and/or plugin is to do the following:
– Temporarily switch your theme back to a default theme, such as Storefront.
– Disable *all* plugins, except for WooCommerce.
– Test to see if the issue has been resolved.
If that resolves the issue, then one-by-one you can switch back your theme and re-enable your plugins, testing in between, until the problem appears again. This will then give you an idea about which plugin is the one causing the conflict.
Since these tests will impact the look and functionality of the site, we strongly recommend using a staging site where you can do your testing.
If you don’t already have a staging site set up, check with your hosting company as many offer this as part of their packages. Otherwise, you can use a free plugin such as WP Staging to set one up.
Hi @warakaku
The reason why the page is not working, is likely because you do not have any endpoints set. This is how it looks on a default WooCommerce site:
Image link: https://d.pr/i/gNvIdf
Unless you have a good reason to remove those settings, it’s best to keep them they way they are.
Hi @iciaretxebarria
I’m not seeing the same issue, as you can see here:
Image link: https://d.pr/i/0T4n7C
Has this issue been resolved, or are you still seeing this on your end?
Hey @joaquin2019
Are you referring to this image?
Image link: https://d.pr/i/xBoaBp
If that’s the case, then it looks like this is your site’s logo image. Most themes have an option to change/remove that in their settings (under Appearance → Customize → Site Identity).
