eimpacteric

This may help you:

https://support.cloudways.com/en/articles/5799334-how-to-use-and-serve-webp-images-in-wordpress

Step #2 — Enable WebP Redirection – might be what you need. We use Cloudways and this plugin and this step is what worked for us.

I’m not looking for info regarding REST API caching. What I want is for the actual product page cache to be invalidated after the price is updated via the REST API.

This didn’t answer my question but I’ll move to your support system. Thanks.

Roll back to version 1.1.11 of the Breeze plugin if you can…version 1.2.0 has broken functions on many websites.

Or make the changes shown in this thread: https://www.ads-software.com/support/topic/new-version-1-2-0-major-issues-with-other-plugins/#post-14459827

Roll back to version 1.1.11 of the Breeze plugin if you can…version 1.2.0 has broken functions on many websites.

Or make the changes shown in this thread: https://www.ads-software.com/support/topic/new-version-1-2-0-major-issues-with-other-plugins/#post-14459827

We’ve also rolled back to 1.1.11 on all our sites due to *serious* issues like WooCommerce checkout not working, form submissions not getting to our email marketing software, etc.

Nice to know its related to the “Delay JS inline scripts” feature…but I’m afraid I’ll skip this version. ??

Yes, it looks like the error is gone! Thanks!

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

https://www.dropbox.com/s/ht8er5dxtlesusz/Xnip2021-05-04_08-21-11.jpg?dl=0

In the back end: right under the admin bar (although the errors are the first thing to show on page load)

https://www.dropbox.com/s/azguqbm0dx4ennh/Xnip2021-05-04_08-21-52.jpg?dl=0

On the front end: right under the header

(I think the errors only show on pages where the 360 viewer is used)

Here’s a snippet from my emails with Maciej:

“My plugin stopped the canonical redirect, because of ?page=1 endpoint in URL. I excluded this particular endpoint and now ?page=1 endpoint will no longer stop the redirect”

“To fix the problem, please simply download the fresh copy of plugin (2.2.8.9 version).”

So even if you’re already on 2.2.8.9 (as I was), Maciej made changes to that version, so install a fresh copy of the plugin and that should take care of it.

The plugin that seems to cause (or help cause) the issue is Permalink Manager Pro. We’re not using that plugin to make any changes to the permalink structure on the page with the search form. I did find an option in the plugin for “Force 404 on non-existing pagination pages”, but I’ve tried that checked and unchecked with no success either way.

If I disable Permalink Manager Pro on WP 5.5, GEOmyWP searches work fine. (“&page=1” does not appear in the URL)

If I rollback to WP 5.4.2 and leave Permalink Manager Pro enabled, GEOmyWP searches work fine. (“&page=1” does not appear in the URL)

I have submitted a request to the Permalink Manager Pro dev also.

Thanks again for your help!

Ok, so I just disabled a bunch of plugins, and it seems to be working now, so I better do some research to see if or which one might be causing the conflict.

https://staging.northlandsheds.com/temp1/
(using the Twenty Twenty theme – for testing only)

For a sample search (with results), you can search for Fargo, ND, USA.

Thanks!

Sorry, I tried on the Twenty Twenty theme as well as our other theme, and this doesn’t fix it for either one.

Just confirming that I received the same 404 result when using the Twenty Twenty theme.

Thank You!

I was working on a staging site for testing alternative themes as well as rolling back to WP 5.4.2 as a temporary fix.