simonbbs

Good Morning @nathvi

I have some more information for you after putting that exclusion in place and running some tests.

After ignoring the error yesterday we are still seeing the following error in our diagnostics tab related to the “View Content” event: https://www.dropbox.com/s/61uaez7ps91a37m/ViewContent%20Still%20Has%20Issue.png?dl=0

I ran tests of both the browser View Content and the server View Content event using FB’s test tool, and investigated the site using the Chrome “FB Pixel Helper Extension” and everything looked good, except for these errors that came via the browser event: https://www.dropbox.com/s/mbjydvu5hia13az/ViewContent%20Parameters.png?dl=0

I don’t believe those parameter errors have anything to do with this, but I wanted to send over all the information just in case.

My first question here: The initial error we were given was:

`Some of your Purchase events don’t have a deduplication key, so we’re unable to cross-check whether they’re duplicate events. This means they’re potentially being incorrectly counted twice and leading to inaccurate ad attribution.

You’ll need to use the solution below to fix the issue.

Once you’ve fixed the issue in your website code you can mark it as resolved. This will move it to the Previously Detected section. If the issue is found again after 3 days it will move back to the Active section.

To prevent this, add deduplication keys to Purchase events received by both your pixel and the Conversions API.`

It doesn’t seem to me like the “View Content” event is a purchase event, so I’m not sure if we’re barking up the right tree here.

Does the plugin track that “View Content” event / could the issue with the “View Content” event be the same issue as other users are experiencing with “Purchase events” ?

If so, we’ll likely run the test you highlighted with the code snippet, however, I wanted to confirm that the “View Content” event is tracked by this plugin.

Thanks so much!

-Simon

Hey @robert681

Update on this for you.

We were able to test things on the default twenty twenty one theme and we discovered this was a conflict between version 4.2.0.1 and WooCommerce version 4.8.0

If we update WooCommerce to version 5.0 it works as expected with the latest version of the Activity Log.

Thanks!

Hey @mikes41720

Currently the staging site we’re working on has 586 posts.

One of our authors does have 388 posts, another has 63, then 42. But those are the largest author collections.

We’ve tested a fresh installation of Yoast with the SEO data Optimization, and have tested trimmed the site down to ONLY Yoast SEO and the default twenty seventeen theme, and that issue still exists. Even if we’re running the twenty seventeen theme with the function in place to trim it down to 50 entries per sitemap.

I’m going to log a report on Github, but if you have any other thoughts that may help here please let me know.

Thanks so much!

Hey @suascat_wp,

Thanks for the information!

By the time I was able to get to it our server team had run the following tests, including that SEO data optimization, and is still not able to access the sitemap:

I’ve created a clone of the “Outdoor Command” staging site to run some further tests, but haven’t had any luck getting the post-sitemap.xml page to load. Here is a summary of the tests, while attempting to load the page after each step:

Deactivated all plugins except for wordpress-seo and switched the theme to a default WordPress theme (twentytwentyone).

Tried installing an older version of wordpress-seo (v14.8).

Completely deleted and manually installed a fresh copy of wordpress-seo 15.8.

Optimised the database via WP-CLI – as the database used InnoDB tables, it runs a “recreate and analyze” instead.

Ran Yoast’s SEO optimization.

Optimised the database using the wp-optimize plugin.

Bumped up the server memory to the maximum we can take it to (1024M).

This ultimately looks to be an issue with Yoast’s wordpress-seo plugin creating a memory leak of sorts on that page. We recommend reaching out to their support team from here! Do let us know if there’s anything else they’d like for us to try server-side to assist further 🙂

Given the above, are you aware of a way we can restore those sitemaps?

Thanks so much!

Good Morning!

I’m following up on this issue as we’re seeing this error returned on the site we initially had this issue with, as well as with a new site.

Here is the specific error we’re seeing: Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 1560576 bytes) in /wordpress/wp-includes/wp-db.php on line 2033
There has been a critical error on your website.

Learn more about debugging in WordPress.

WordPress database error: [Commands out of sync; you can’t run this command now]
SELECT umeta_id FROM wp_hhl8nefx92_usermeta WHERE meta_key = ‘wp_hhl8nefx92_yoast_notifications’ AND user_id = 32

WordPress database error: [Commands out of sync; you can’t run this command now]
SHOW FULL COLUMNS FROM wp_hhl8nefx92_usermeta

We’re seeing this both on one site with a lot of pages page sitemap, and another site with a lot of posts post sitemap.

Both sites have ~500 pages / posts respectively. And all other sitemaps on the sites work as expected. It is only the maps with a lot of data that don’t load properly.

I tested rolling things back to 15.4, the version here that initially fixed things, and even with the plugin rolled back that error persists.

I also ran the test earlier in this thread to install the Yoast test Helper plugin, and that did not help mitigate that error either.

Thanks so much!

-Simon

Hey Guys,

Just following up on this.

We’ve had the plugin disabled since my initial thread here, but as of today the server team is still seeing that action called in fresh tests.

Per the team this was what they saw in a 10 minutes span:

20306 [action] => jquery-migrate-downgrade-version

Is this expected activity after the plugin is disabled?

How can we halt those calls from the plugin?

Thanks!

Hey @mazedulislamkhan

The site in question has 0 posts and 428 pages.

Thanks!

-Simon

Hey @priscillamc

Thanks for reaching out!

1) Yes, everything is completely updated

Wordpress: 5.5.3, Yoast: 15.3, Twenty Nineteen Theme 1.7

I’ve also tested rolling back the Yoast plugin to several different recent versions and nothing removes that error except for deactivating Yoast entirely.

2) Yes, we meet all the server requirements and run Yoast successfully on probably 50-60 other sites using the same type of server.

3) Yes, I currently have things parred down so it’s ONLY Yoast and the Twenty Nineteen theme active, and we’re still seeing the following errors:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 212992 bytes) in /wordpress/wp-includes/wp-db.php on line 2033
There has been a critical error on your website. Please check your site admin email inbox for instructions.

Learn more about debugging in WordPress.

WordPress database error: [Commands out of sync; you can’t run this command now]
SELECT umeta_id FROM wp_hhl8nefx92_usermeta WHERE meta_key = ‘wp_hhl8nefx92_yoast_notifications’ AND user_id = 1

WordPress database error: [Commands out of sync; you can’t run this command now]
SHOW FULL COLUMNS FROM wp_hhl8nefx92_usermeta

Thanks!

-Simon