Wudman

Michael,
Thanks for the response. I have already done the SOP for checking plugin conflicts several times, deactivating every thing but DIVI and WooCommerce at which time I started activating plugins until the issue manifested itself.

When I reactivated Yoast SEO this morning, the issues appeared to go away. Since there had been no update in the last 24 hours, I looked at Yoast SEO changelogs. Yoast SEO’s last update (17.7) was 12/2/2021 yet I had the issue yesterday (12/8/2021).

Then I noticed I was working in Brave which is not the browser I usually use due to installed dev extensions and addons. So I opened the site in Firefox and the issue was present.

As this is a working eCommerce site, I am not inclined to change the theme, especially when deactivating Yoast SEO eliminates the problem in Firefox.

Per my original post, I went through several tests using my iMac and Windows browsers. Only time the annoying behavior happens is with Firefox.

So here is the side story, my client finally authorized re-subscribing to the Yoast WooCommerce Premium Bundle. That bundle improves my workflow and saves my client money. I’d rather have that installed than “un-Yoast” the website.

On the other hand, I have payed a lot of attention to Yoast SEO resources including the YAcademy, to go without the plugins.

Also, if you haven’t already, wander over to the other DIVI/Yoast issue post and there is another mention of a user pulling Yoast under the same circumstances.

As I am not a hobbyist, I try to keep my diligence extreme AND I like Yoast’s time saving capabilities. I venture others just deactivate, delete, and install a lesser SEO plugins.

@mollyann1,
I am starting a new thread with some additional information related to WordPress and DIVI.

Versions: Yoast 17.7, WordPress 5.8.2, DIVI 4.14.2 & WooCommerce 5.9.0. My additional information may be specific to your issue and meet WP posting rules (therefore get a response.)

• This reply was modified 3 years, 3 months ago by Wudman.
• This reply was modified 3 years, 3 months ago by Wudman.

I can confirm two issues generated by the basic Yoast SEO plugin and DIVI.
1. Editing a Product Post (WooCommerce), causes DIVI to spawn a blank preview page.
2. Exiting any Editing Mode spawns a “Your changes will not be saved…” warning.

All plugins on this site reflect the latest versions. The issue was tested by unplugging almost all plugins other than WooCommerce and WordFence after checking the operation of the website in “Safe Mode”.

Disabling Yoast solved the issues.

Hi,
Thanks for the response. Due to a WooCommerce issue, Automattic has an ongoing investigation on what appeared to be an unrelated exploit of the core WooCommerce plugin.
As part of the investigation, Automattic just sent me a discovery that 5700 attempts to validate a transaction. This times with our Braintree failure. So we are closing this because the issue appears to be internal to our Braintree account, not the plugin.
Thank you

How I solved this…
While on the phone with my host to verify proper SSL and no other restrictions, I took the following actions with the results listed.

Action:
Deactivated the Plugin WITHOUT disconnecting it from SQUARE
Flushed the website cache (WPEngine)
Result:
NO CHANGE

Action:
Disabled WordFence Security (Premium) Left Plugin ACTIVE
Result:
NO CHANGE

Action:
Disconnect Plugin From Square, Flushed Cache
Result:
Location Populated and was able to use a credit card to make a transaction!

The last action was taken while I was on the phone with WPEngine to make sure their hosting or SSL configuration was not the likely issue. While their CSR was consulting their Senior tech support, I disconnected SQUARE from the plug, reconnected and magically the Location showed up. I ran a transaction and that was successful as well.

I have no idea of flushing the cache did anything to help, but that is part of my process when I make any major changes to plugins.

Hope this helps!

Mirko,
This is a client site and I am pretty demanding about where my client’s should host websites and what basic infrastructure has to be in play if they want my best rates. This website is hosted on a host that has 24/7 support, a separate User Control panel where I can manage the CDN and Backup/Restoration, among other services off site. It took 15 minutes to restore the website and another 15 minutes to revert the website back. Plus the access of backups goes back two weeks.
Hosting matters on so many levels.

Thanks for the reply. So the rest of the story…

First I recognize the need to back up more often. Daily backups are mandatory, but in cases where a website is “highly active”, for example, an eCommerce website, whenever making any update or change, set a restore point and back up first. That is my take away.

What I left out of the original post is that the “broken” image issue materialized as soon as I saved the changes input via Customizer> WooCommerce>Images. Immediately after using the Customizer, the odd product image sizes materialized. The regeneration wasn’t close to being done. In fact I stopped the regeneration within a minute or so the first time because once I refreshed the site on a different computer, the image issue showed up.

(Checking the site on a different browser and computer verified it wasn’t a local browser cache issue. Purging all caches with the host made no difference either.)

Again, it all looked good up until the moment I used the Customizer and the thumbnail regeneration is just a part of that process. (Sorry WooCommerce, you may be either part of or a victim of other issues.)

For the heck of it, I took a different angle. I copied all my added CSS and pasted it into Notepad for safekeeping. After pulling out all the previously working, error-free CSS, the product and catalogue images returned to a uniform size. Note that the broken images showed up in both the product posts and catalogs.

Taking a deeper look at the CSS there were a few adjustments that overrode the theme’s settings. I pulled that CSS out, restored the rest of the CSS and darn if that didn’t fix the issue. Even resetting Customizer>WooCommerce>Images back to the original settings and letting the thumbnails regenerate did not restore the website with my original functional.

Also the only constant I could identify is that the image size fail seemed to affect products in groups added at certain times. It appears that over the six years of this site’s existence, some combination of WordPress, WooCommerce, and theme (DIVI) updates, have conspired to invalidate some added CSS. Once the Customizer action was initiated, changes were made that invalidated previously working CSS and there was no going back in time.

I still have to figure out why the Customizer isn’t working for resizing the Product images or come up with some new CSS to manage the size and thumbnail. They are currently resolving physically bigger than before, which is also bigger than the uploaded images. Therefore are blurry.

(Since I comment out my CSS and include a date code, I was able to pin down the added CSS to July 2020.)

Delete and then re-upload.
If you haven’t deleted it yet, check to see if you still have an item link under the “Settings” for WPS LOGIN (SETTINGS > WPS HIDE LOGIN >)

That was my first clue something broke in a recent update.

Awesome, uploaded the update this morning and my tables are back to “functional”. Thank you for the quick response.

Came to see if there was a solution to this column issue. I just noticed my columns are also all the same size despite resolving in the “View” mode as designed. Where I had a narrow SKU column, followed by a wider Description and then another narrow Price column, I have three equal columns that basically trashes the layout since the Description Column now wants to be up to four lines tall.

• This reply was modified 4 years ago by Wudman.

Thanks for the reply. I will take your advice and see how my site is detecting IPs. Clearly the one that is whitelisted isn’t being treated as so on this site.

Louis,
The easy and fast way to get around this is to use SFTP and manage the folder with a name change. You can rename the Wordfence folder by putting an underscore (_) in front of it. Login, then return to your STFP folder view and restore the WordFence folder name. Then you can manage 2FA yourself. Either disable or generate new codes. (and of course store them somewhere you will remember.)

Noting the new block page says, “Manual Block By Administrator”. Marked this as resolved, though I don’t understand how I get locked out while doing Admin stuff…

• This reply was modified 4 years, 10 months ago by Wudman.

Thanks, resolved it for me as well.

Following this topic as well since exact same issue…again.