New to the community? Start here

WooCommerce 3.5.0 & SmushPro Conflict

I use WooCommmerce on my site to sell products. WooCommerce was recently updated to version 3.5.0 which enabled on-the-fly image resizing for the products.

This is causing Smush to get worked up and get very resource intensive to an extent that it affects the browseability of the site.

I have escalated this with WooCommerce team and they have also reached out to their developers. I am reaching out to you guys also in order to bring your attention to this.

As of now, I have downgraded the WooCommerce plugin and everything is working fine, but I will not be able to maintain this for a long time.

Wed, 31 Oct 2018 5:22:44

Adam Czajczyk
- Support Gorilla
- 4,882 pts: Hero points 27,817 pts: Rep. points LEVEL 30
Hi Michael

I hope you’re well today and thank you for your question!

I must say that I also wasn’t able to replicate this on my test setups. With the newest WooCommerce and Smush Pro I didn’t notice any issues and the site wasn’t going down (and I’m testing this on quite a simple and cheapo shared host).

I’m not saying there’s no conflict but I think it’s more into it than solely these two plugins just being enabled. I assume that either it’s some additional plugin involved or it’s related to specifics of the store/smush configuration.

I understand that you didn’t have WP debugging enabled on site when this crash happened, right? It would be good to check it, though, as it could help us identify the cause or at least give additional clue on how to replicate this.

I realize that you might not want to risk that on your live site again so would it be possible that you setup a staging site? Such a site should be an exact copy of the live one, on the same server. Then, adding following lines to the “wp-config.php” file of it would enable WP debugging:
```
define( 'WP_DEBUG', true);

define( 'WP_DEBUG_LOG', true);

define( 'WP_DEBUG_DISPLAY', false);
```
After they are added, the WooCommerce would have to be updated there and once the site crashes, there should a “debug.log” file appear inside the /wp-content/ folder (of that staging site, of course).

Could you give it a go and then share that debug.log file with me here? You can upload it into some file storage of yours (e..g Google Drive or Dropbox or similar) and just post a download link to it here.

Hopefully, that would give us a clue (without affecting your live site!) on what might be happening there. Then we’d see what to do next to pinpoint the source of the issue and how to fix it.

Best regards,

Adam
Michael
- Flash Drive
- 69 pts: Hero points 47 pts: Rep. points LEVEL 2
Hi Adam,

Thank you for the clear guidance. As instructed I have set up a staging site and generated the debug.log file for your reference (see attached).

Although the Gateway Error did not appear when I tried opening a few product pages, I believe that was because the page load time did not exceed the 60 second limit imposed by my hosting provider. Page load times were very slow however, and I guess somewhere in the range of 30 seconds per page depending on how many images were in the product image gallery.

Please let me know if you need anything else.

Michael
Michael
- Flash Drive
- 69 pts: Hero points 47 pts: Rep. points LEVEL 2
It appears that I cannot attached the log file so you can access it via the following Dropbox link:

https://www.dropbox.com/s/j292ly7ok7zbemp/debug.log?dl=0
Adam Czajczyk
- Support Gorilla
- 4,882 pts: Hero points 27,817 pts: Rep. points LEVEL 30
Hi Michael

Thank you for your response and for sharing a debug.log. There is a notice in the log but it’s not related to Smush Pro and doesn’t seem to be a reason for such slowdown anyway. I have also checked our internal reporting system but didn’t find anything related to the case.

I’ll need to “dig deeper” then. Since you already setup a staging site, could you please enable support access to that staging site too? I would also like to be able to access its files and database so a cPanel access would be perfect (or FTP + phpMyAdmin access, but cPanel is preferred if available). After enabling support access to the staging site, you may put these credentials safely in a text box below “Access active for X days” message on “WPMU DEV -> Support” page. The message won’t be posted anywhere so just let me know here once you’re ready and I’ll try to find out what’s happening.

Best regards,

Adam
Michael
- Flash Drive
- 69 pts: Hero points 47 pts: Rep. points LEVEL 2
Hi Adam,

Thanks for the follow-up.

As requested, I have granted you support access to the staging site and input the ftp and MySQL database access credentials in the support page text box. Please note that I am using Kinsta for my hosting and they do not use cPanel so you have ftp access instead.

Please let me know if you need anything else.

Michael
Predrag Dubajic
- Support
- 3,881 pts: Hero points 29,855 pts: Rep. points LEVEL 30
Hi Michael,

I was doing some additional tests and I was able to replicate the issue when using PNG image with transparent background, I’m guessing these images are making the most impact.

I have created a report to our developers with all the info from my tests so they can investigate this further.

Best regards,

Predrag
Michael
- Flash Drive
- 69 pts: Hero points 47 pts: Rep. points LEVEL 2
Hi Predrag,

Happy to hear you were able to nail down what was going on! I don’t use PNG images much on my site but they will certainly be there so if you can identify a workable fix that would be fantastic.

Regards,

Michael
- Anton Vanyukov
  - Developer
  - 590 pts: Hero points 628 pts: Rep. points LEVEL 6
  Hi Michael ,
  
  I have tried to replicate on my test sites, but was unsuccessful. Also, I have looked at your staging website. It does load slowly, but not because of Smush, because Smush does not optimize images on the frontend. I would recommend you do a plugin conflict test and find the conflicting plugin. Plugin conflict test is disabling all the plugins, and enabling them one by one to find which one is causing the issue.
  
  Also please update Smush to the latest version, as it includes fixes for WPML compatibility.
  
  Best regards,
  
  Anton
Predrag Dubajic
- Support
- 3,881 pts: Hero points 29,855 pts: Rep. points LEVEL 30
Hi Michael,

Anton was working on a patch for this issue based on few reports we got since WooCommerce 3.5.0 update, could you try downloading the attached file, unzip it and place it inside wp-content/plugins/wp-smush-pro/lib/ folder and see if that fixes the issue for you?

Let us know how it goes.

Best regards,

Predrag
Michael
- Flash Drive
- 69 pts: Hero points 47 pts: Rep. points LEVEL 2
Thanks for the follow-up Predrag/Anton.

As instructed I have uploaded the php file to the specified folder and tried browsing a few product pages. All the pages appear to be loading normally again, so I can only assume that the issue has been resolved. Thanks very much!

I have a number of other sites using Smush as well, so if you could let me know when you plan to release this update it will help me decide when to re-activate the plugin on those sites.

Many thanks,

Michael
- Anton Vanyukov
  - Developer
  - 590 pts: Hero points 628 pts: Rep. points LEVEL 6
  Michael , we are already testing the new update. So shouldn’t be long now.
  
  Best regards,
  
  Anton
Michael
- Flash Drive
- 69 pts: Hero points 47 pts: Rep. points LEVEL 2
Sorry, forgot to mark as resolved…

WooCommerce 3.5.0 & SmushPro Conflict

Learn more

In The WordPress

Resources

Blog

Learn more

How do you rate me?

Thank you for rating your experience!