themightyant

Thank you.

I see that GitHub bug report was from April 2021. I realise this may be low priority – although it affects visuals on basically every stock WC install – is there anything that can be done to elevate this, anything I can do or supply to help, or do you think it will never be addressed?

I realise you may not know, but just trying to get answers for clients who were the ones that initially flagged it.

Regardless at least i’m not going mad! ??

• This reply was modified 2 years ago by themightyant.

Hello,
Again thanks for looking into this further. However in your example 2 things are different which is likely why you can’t see it.

1. The images have a white border on a white background so you wouldn’t be able to see the 1px of the other image even if it was visible.
2. Remember this only happens at some screen sizes (38.5% above 767px), as such you may have to resize your browser window to see it.

Regardless I have created a second brand new WordPress install locally with WAMP and tested it with no other plugins or themes but WooCommerce and Twenty Twenty-Three, I used brand new images all JPG, all the same size, and still this persists.

Conclusion: It isn’t a problem with the theme, other plugins, images or anything else. It is a problem within WooCommerce. As I said almost certainly a rounding error on the JavaScript that is handing the slider’s size dynamically.

I’ve made all images 1000×1000 pixels and the issues remains.

Question
Are you not seeing this on any of your own WooCommerce installs?

I’ve now tested this on several Woocommerce Sites i’ve built (see here and here) and am seeing exactly the same thing on every WooCommerce store I tested.

I’ve tested this on a blank WordPress install with just WooCommerce as the only plugin and it happens with the stock Twenty Twenty-Two, Twenty Twenty-Three or Storefront themes.

I’m seeing it in every browser I have tested, Chrome, Firefox, Edge etc.

It seems clear this isn’t a problem with the theme or images but WooCommerce itself, more specifically their custom version of the Flexslider plugin they are using which rounds all the image widths to a thousandth of a pixel. The stock FlexSlider doesn’t have the same issue but only rounds the images to the nearest WHOLE pixel.

• This reply was modified 2 years ago by themightyant.

Hello Igor,
thanks for the reply. I’ve updated the image and made it a JPG with a white background but it doesn’t fix it, the same problem is happening.

I’ve done some further testing and am 90% certain it is related to the JavaScript carousel library included in WooCommerce and a rounding error from that. The Width of each slide is updated in realtime as you resize the window via JavaScript to 3 decimal places.

Above 767px it seems to be happening for 5 of every 13 pixels, or 38.5%, of the viewport sizes, meaning it isn’t a negligible amount. I tested this in detail and it seems to repeat in a pattern every 13 pixels.

e.g.
Screen size in PX and if issue is happening Y/N
768 N
769 N
770 Y
771 Y
772 N
773 N
774 Y
775 N
776 N
777 Y
778 N
779 N
780 Y

This exact same pattern (NNYYNNYNNYNNY) repeats 781-793 and again for other sections I have tested.

Hi Igor,
thanks for looking into it and getting back to me. The issue isn’t happening in the lightbox version of the carousel you are looking at (with the black background) only in the standard one when the page is first displayed (with the white background).

https://www.dropbox.com/s/l18dhqop2j9sur3/woocommerceissue-1-22-1440.mp4?dl=0

I have attached a video above which should make it clearer. You will see when on the second image some of the previous image to the left is showing. Note this only happens at some screen sizes but not at others. When the screen width is changed you will see it flickering.

From further testing this happens at 5/13 or 38.46% of screen sizes above 767px and appears to be due to a rounding error, it repeats in the same pattern every 13px having the issue at 5 of those pixel steps and not at the other 8.

Regardless I have cleared both the browser and site cache as instructed but this is still happening in all browsers I have tested Chrome, Edge, Firefox etc.

• This reply was modified 2 years ago by themightyant.

Sorry was having a complete brain fart. Was looking for an ID (number) not post type (name) of course ‘page’ works fine.

@pumpaxxl I understand that sentiment but with that attitude the plug-in will never grow. There’s also mitigating circumstances here.

I believe the Analytics Insights plugin is developed by Alin Marcu who was the original developer of this plugin when it was still called “Google Analytics Dashboard”. He built that up to be millions of installs before he sold it to Monster Insights… who promptly ruined it with paywalls.

This plugin GAinWP was a fork of the original but seems to be dead in the water now. It hasn’t been updated for PHP8 and developer won’t respond.

Thanks Donna, I do. I didn’t realise that the plugin was split this way since the change to a free plugin + extensions. I will contact them there.
Many thanks

Understood. Though for the record I was just trying to be helpful to everyone else who stated they were looking to replace this once great plugin.

Does your site have a caching plugin enabled or your server have caching enabled? This is the most likely cause. Alternatively has the theme been amended to hard code this into the theme files?

If the plugin is disabled this will not appear in normal circumstances.

Thank you @nimonogi that solves it and @stevember for the extra info.
Thanks for the great plugin also.
Case closed

Hi Thanks for the prompt response.
I’m running 7.3 but have tested in 7.1 with the same problem. Below is a link to an image with all other plugins disabled, default theme and the problem still appearing (it is a dev site so errors are on).
Yes, the notice goes away when Cookie Bar plugin is deactivated.

https://www.dropbox.com/s/x4eacn57bpwv789/alp-error-cookie-bar.png

• This reply was modified 5 years ago by themightyant.

Thanks, I will look into these options.

Thanks for the reply and interesting to hear the plugin is extendable to other doc types. Is there any documentation for this feature?

Hi Yorman, thanks for the follow up. My apologies about the delay getting back to you, I wasn’t notified of your follow up via email despite ticking the box, I’ll check spam.

Re: purelatitude.com you said it “…was successfully scanned and HTTPS is okay” Yet this is also getting the same error “SUCURI: SiteCheck error: Unable to properly scan your site. 404 Not Found”. Any idea why.

Re: your other investigations are you saying that sitecheck only works over SSL? 4 of the 5 sites I sent do not yet run on HTTPS though we are looking to update these in due course.

As I said previously this was only a sample of sites, I have dozens that use this plugin and many have the same error.