Diego

So far, I've seen it occurring on a development server and on localhost. On other sites, it doesn't happen. However, a safeguard should be easy to implement.

I don't have an update URL without a path. The URL and the path are always the same in all cases. Anyway, not a big deal, I will see what's...

Actually, the issue is simple to reproduce: ``` // Use a URL without a trailing slash. It's a valid URL, anyway, as the trailing slash is optional $url= 'https://example.org'; //...

That's precisely what I'm checking now. So far, the two sites where the issue occurs have the URL without the trailing slash. I'm checking the other ones, to see if,...

I worked on at least two projects where the call to the update endpoint returns a JSON without that information, because it's used for premium products. If a valid licence...

In this specific case, that might not be that easy. An "invalid licence" is returned with a response code of 200, because it's considered a successful request. It all works...

I sent an email to your support contact, with a link to download the latest Currency Switcher. That should allow you to reproduce the issue easily.

**Additional note** A client reported that the conflict apparently doesn't arise with PHP 8.0, whereas it occurs with PHP 7.4. However, we can't explain why. I wouldn't rely on this...

The client indicated that, on a staging site, the issue occurred with PHP 7.4. When they switched to PHP 8.x, it didn't occur. However, it also didn't occur anymore with...

If I may add a personal note, this issue is not particularly rare, nor necessarily difficult to address. It's a know fact that WordPress lacks any sort of dependency management,...