macgeekgab

I’ve been having the guzzle errors for months, but this being unable to even select an endpoint is new with this new version, yes.

Really, it’s happening when I try to add ANY S3 endpoint, and is not specific to my Minio issues I was previously having.

I have four different sites, all on the same server, and with the latest version the other three work great with MInio again (yay!). But for some reason this one site does not.

Thanks for that. I tried the workaround from the other thread, and now I get a different error:

[09-Oct-2024 09:26:34]?1. Trying to send backup file to S3 Service?…
[09-Oct-2024 09:26:34]?ERROR: Exception caught in Error: Call to undefined function GuzzleHttp\default_user_agent()

I’ll continue to try messing with it, of course… perhaps there’s a path just past my fingertips… but figured I’d report here, too.

Thanks for the proposed workaround @sflwa! Unfortunately, I’m still getting these errors:

[09-Oct-2024 09:26:34]?1. Trying to send backup file to S3 Service?…
[09-Oct-2024 09:26:34]?ERROR: Exception caught in Error: Call to undefined function GuzzleHttp\default_user_agent()

I’ll continue to try messing with it, of course… perhaps there’s a path just past my fingertips… but figured I’d report here, too.

I’m still seeing this with the latest versions of BackWPUp and WordPress. Any progress on the Error: Call to undefined function GuzzleHttp\choose_handler() errors?

I looked, and PowerPress is not adding these fields to wp_postmeta anymore. Looks like it started with Powerpress 11.9 (and persists in 11.9.1).

Confirmed “fixed” by rolling back to 11.8.3.

Hopefully this is enough to get a quick fix in place, because this is breaking a few things we rely upon.

Thanks!

• This reply was modified 9 months, 1 week ago by macgeekgab.
• This reply was modified 9 months, 1 week ago by macgeekgab.

I’m seeing the same thing. It’s properly detecting it, but not adding it to the feed for episodes published in the past two weeks.

Is there an answer here for getting the same error with a MinIO server? I’ve manually set the region on both the server and in BackWPUp to be exactly the same, but I still get this error. Thanks for any help you can provide!

We, too, were seeing this and by looking at the JavaScript console it was obvious that some non-existent functions were being called. I also noticed that it was loading all JavaScript from my browser’s cache/memory, and not from the site.

To fix it, we forced our browser(s) to reload everything from the site.

In Safari, hold down Option key while going to View > Reload Page from Origin.

In Chrome, holding the Shift Key down and choosing View > Force Reload This Page did it.

Thanks, and good luck!

Yeah, that’s the whole problem. With this enabled, neither Facebook nor Twitter will parse far enough to see the meta tags for images, article title, anything. It’s just a shell with no identifying characteristics.

If I disable Eliminate render-blocking CSS by moving it to the HTTP body I am not getting that issue.

The issue appears only if that feature is enabled.

Thanks @3sonsdevelopment — I don’t think this is a Subscriptions issue. It’s just that Subscriptions throws a critical error when the woocommerce_db_version field is missing from the wp_options table.

That problem is triggered by a WooCommerce update, not a Subscriptions update.

• This reply was modified 4 years, 9 months ago by macgeekgab.

AHh, rats. That’ll teach me to believe what I intuit when reading the AMP developers talking on their threads. ??

Thanks @westonruter.

I think this behavior is intentional to AMP (at least from my research this morning).

If you specify a type then it presumes you’re using a vendor definition and, when you’re using a vendor definition, the transport should be defined by the analytics vendor and not overridden by the publisher.

It would be possible, for example, for a vendor to only support GET requests, and then a publisher attempts to override that with a transport method that uses POST request and now thing are broken, hence the error. (Honestly I think it should be a warning and not an error, but, hey, the internet exists for opinions, right? ??

With type absent, it knows you’re not using a vendor definition and transport is an acceptable thing to define.

For example, this code works 100% fine, and tracks 100% fine, except the plugin is adding that type field (as above) which throws the error.

{
    "triggers": {
        "trackPageview": {
            "on": "visible",
            "request": "pageview"
        }
    },
    "transport": {
    	"beacon": false,
    	"xhrpost": false,
    	"image": true
    },
    "requests": {
        "base": "https://site.com/path/to/analytics/pixel.gif&rnd=${random}",
        "pageview": "${base}"
    }
}