🇺🇸United States @EHLOVader

There was a comment once, but it was removed for some reason
It would be good to add that back I think

It is supposed to be in there
https://www.drupal.org/project/google_analytics/issues/3328262 →

This is by design. That developer ID is what google uses to identify usages from Drupal. You can see more here: https://developers.google.com/tag-platform/devguides/gtag-integration

Was there a resolution for Accept.js issue and have they actually completed the switch to the SSL certificates?

I was still seeing Entrust certs coming from apitest.authorize.net and api.authorize.net.
I also see that the maintenance on the status page for SSL was still "In Progress" and now all of the APIs are in maintenance but no new incidents appear for Accept.js

I've still been seeing issues from Accept.js and they don't seem to know what is causing it.
Were others having issues still?

Ah, I see that it was replaced in https://git.drupalcode.org/issue/drupal-3484147/-/commit/3d645c1b3cd6aae...

So I was on 10.3.2 which must have been before this.

I'll attach my patch in case others need it but upgrading should also resolve this.

ehlovader → changed the visibility of the branch 3484147-missing-formattablemarkup-in to hidden.

ehlovader → changed the visibility of the branch 3484147-missing-formattablemarkup-in to hidden.

ehlovader → created an issue.

ehlovader → made their first commit to this issue’s fork.

ehlovader → created an issue.

EHLOVader → created an issue.

EHLOVader → created an issue.

oh, thanks for sharing your work around on this @jcnventura

"drupal/ctools": "4.0.4 as 3.99",

I don't think I'd known this was possible. It will help add to my notes on using the fork to install from.

And thanks for helping explain the failing on CI @IT-Cru I wondered why it was failing if I can get it to work on my own.

Thanks @jcventura so, if it isn't using that cloudflarephpsdk, that cloudflarephpsdk doesn't have dependency conflicts with guzzle, Drupal 10.2 doesn't have guzzle conflicts, and ctools 4 doesn't have guzzle conflicts was there anything else preventing this from being merged?

What needs to be done to move this forward?

Ah, thank you @dmudie, I appreciate the follow up.

Sorry I missed that detail.

That module appears to also support ^7.0 but maybe something funny is happening with the dependencies since it can also use ^6.0
"guzzlehttp/guzzle": "~6.1|^7.0"

I did a quick test, but it appears to install fine with the drupal/cloudflare:dev-3293730-support-ctools-4-2.x issue fork that is part of the merge request.

These are the modules I have installed (of relation to this issue). So I think I must be missing something else if this can't be merged as is.

d8-contrib-modules/cloudflarephpsdk 1.0.0
drupal/cloudflare                   dev-3293730-support-ctools-4-2.x 45e99be
drupal/core-recommended             10.2.3
drupal/ctools                       4.0.4

@dmudie can you elaborate more?

including requiring cloudflare SDK which in turn requires guzzlehttp/guzzle ^6.2.2

When I check the latest release it is requiring v7
"guzzlehttp/guzzle": "^7.0.1",

When I install this cloudflare module with the issue fork it installs fine.

ctools guzzle requirements don't conflict with the cloudflare sdk requirements for me, this just needs the version of ctools bumped.