It's definitely using an HTTP GET. I just confirmed that by looking at a sample in my nginx log:
40.77.190.63 - - [03/Jun/2024:08:14:10 -0400] "GET /visitors/_track?action_name=...
I guess this means that there's no visitors error here. No, I don't see it being logged by the module. Thanks for the help, @bluegeek9.
I've noticed that the errors are all associated with Microsoft Bing bot IP addresses. Could a crawler be doing something unexpected?
Thanks for such a quick reply!
What was the previous version installed?
8.x-2.16 was previously installed. I had uninstalled that version (using "drush pmu") while waiting for this new release, so this was basically a fresh installation.
Have you cleared the cache? The error is, No route found. It is referring to the path/route Visitors logs the visit. The data is sent as a POST
Yes, after using composer to install the update I ran both "drush updb" and "drush cr". I've since flushed all caches again, and the errors still appear.
Does the site have a path prefix? https://www.mysite.com/test
No, there's no path prefix like that. If it helps, here's the complete location given for one of the logged errors (with minor edits to redact the actual site name):
https://www.mysite.com/visitors/_track?_cvar=%7B%227%22%3A%5B%22route%22...
Looks good to me.
sah62 → created an issue.
Thanks for the reply! Yes, sorry, I believe this is an issue, or also an issue, for the XML Sitemap module. Please move it as appropriate.
1. The type is "xmlsitemap".
2. The URL I see on my site to enable or disable submission to Google is this one:
https://www.mysite.com/admin/config/search/xmlsitemap/engines
3. Yes, I'm using the XML Sitemap module. It's checked on the /admin/modules page.
4. My preference would be for sitemap submission to work without error. Given what I read in the Google blog, I believe this means "stop pinging Google AND modify robots.txt to include a Sitemap line" as you described.
In the meantime I can disable sitemap submission by uninstalling the XML Sitemap Engines module.
Fix confirmed. I haven't seen any errors since deploying the patch.
sah62 → created an issue.
I've been using the patch since I posted it. It's been working fine for me.
I've seen it in 9.3.2, too.
Patch attached.
The patch in #13 works for me.
Here's a patch.
Moving this to Commerce PayPal.
I posted this same question on StackExchange after not getting any feedback here:
https://drupal.stackexchange.com/questions/317446/user-error-funding-sou...
A response received there may contain the needed fix. This appears to be a Commerce PayPal issue. Here's the suggestion:
To create a valid render array, put the string the function returns in a markup render element:
$variables['order']['funding_source'] = ['#markup' => commerce_paypal_funding_source_label($data['funding_source'])];
That's in file commerce_paypal/commerce_paypal.module. I've made the change and am still testing to see if it solves the problem. If it does, this issue should be move to the Commerce PayPal issue queue with the fix included as a patch.
I tried re-installing a second time, but this time I made sure to completely uninstall first. As noted by @Janner, this seems to have solved the problem. I'm not seeing any more errors or warnings. I did have to go back and re-adjust my site settings, though.
I tried reinstalling. It didn't help. Ticket opened.
I'm using nginx/1.18.0. I have client_max_body_size set to 500M in nginx.conf.
I found a small typo in the patch: there's an extra "&" in the description of "USPS Ground Advantage& Parcel Locker". Here's a new patch with that extra character removed.
I've attached a patch that replaces the old service descriptions with the new service descriptions returned from the USPS web service. It works for my store; please review the changes and let me know if I missed anything.
The patches are working for me. Let's get this reviewed.
Would something like this work to mark an order item each time is payment is processed?
foreach ($payment->getOrder()->getItems() as $item) {
$square_item_processed = $item->getData('square_item_processed', FALSE);
if ($square_item_processed) continue;
// Process the order item.
...
$item->setData('square_item_processed', TRUE);
}
I've tried to test this idea. Nothing "bad" seems to happen when I process a first payment for a single item. If I edit the order and add an item, though, when I try to process the second payment the value of $square_item_processed is FALSE for both items in the order and the payment process fails because the amount of the order (2 items, plus tax, plus shipping) doesn't match the payment (1 new item plus tax). I'm clearly still missing something.
Am I correct in assuming that some of these instructions are intended for module developers, and some are intended for site administrators? For example, "migrate to the new template" appears to be a developer instruction. There's no GUI for it that I can find so there's nothing I can do as a site administrator, but I understand how a module developer would need to switch if their module is sending email.
I just did some testing with my existing webform configuration in which email with attachments is sent. It still works just fine, without changing anything, after configuring Symfony Mailer (with import of my Swift Mailer settings) and removing the legacy applications.
One last question: at what point can I (or should I?) disable the "Emulate swiftmailer" option as a site administrator?
Thanks again!