Simon

Hey @djbrunolima,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hey @zahost!

Thanks for getting back to us, that’s understandable! I’ve had a look over your description and it sounds as though there might be some front-end issues causing these errors, as it’s certainly not something we’re seeing widespread at the moment.

It would be great if you could confirm if with only WooCommerce and Facebook for WooCommerce active, do you see the same error? You mentioned that you attempted to deactivate other plugins and it disappeared when Facebook for WooCommerce was deactivated. I wonder there is a conflict between another plugin, and so if either of the plugins are deactivated, the problem would disappear. If this was the case, being able to narrow this down would let us offer some suggestions to get this working again!

Another option would be to check the browser console when you’re on the edit product page with the broken Screen Options. Here’s a list of common ways to access the console for different browsers: https://documentation.concrete5.org/tutorials/how-open-browser-console-view-errors

Would you be able to let me know if you see any errors logged after trying to access Screen Options?

Cheers!

Simon.

Hey @snehminz,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hey @sanitjain,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hey @mitchellk,

It has been a while since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Simon.

Hi @zarausto,

Thanks for the feedback! The New Relic image in your last reply seems to be regarding a different scheduled action, the wc_facebook_regenerate_feed rather than wc_facebook_background_product_sync_cron_interval, is that right?

In the previous versions of the plugin, we had to remove API access to sync products due to a security issue with token access. The only way that products were synced was to generate a feed file that Facebook would request from the site on a schedule, once per hour. In order to guarantee that the information synced was most up to date, we had to regenerate the feed file on a schedule too, every 15 minutes.

With the API access now restored in our latest versions, this has become less important though still useful for a few edge-cases. Ultimately I hope we can move away from this in the future though, and it’s something our product and development team are already looking into.

That said, if this is causing a significant impact on your customer’s sites, it is possible to adjust the interval that the feed file is regenerated.

/**
* Filters the frequency with which the product feed data is generated.
*
* @since 1.11.0
*
* @param int $interval the frequency with which the product feed data is generated, in seconds. Defaults to every 15 minutes.
*/
$interval = apply_filters( 'wc_facebook_feed_generation_interval', MINUTE_IN_SECONDS * 15 );

You would first need to disable product syncing to remove the existing schedule. Then insert the custom code adjusting the returned interval from above, then re-enable product syncing for the new interval to be used.

Thanks again for taking the time to leave ar review, and I hope we can look at this closer in the future! In the meantime, I hope this might prove useful for your customer’s sites.

Cheers,

Simon.

Hey @fcrowe,

As we’re waiting for the new release from Facebook to look at this further, let me close this topic for the time being.

If you’re still experiencing other issues please take a look at our documentation for more information and create a new thread for additional support.

Thanks,
Simon.

Hey @begumyildirim,

Sure thing! I’m sorry that the plugin didn’t meet your needs on this occasion. If you’d like to keep the plugin for the product syncing side of things, that should still be possible. You can then use a snippet to disable the pixel integration.

Of course, I completely understand if you’d like to use one plugin for both and can find a suitable alternative.

Can you please let me know if there is anything else I can help with?

Cheers,

Simon.

Hi @begumyildirim ,

The latest we’ve had from the Facebook team is that they’re looking into providing more information for this error in a future release, such as showing the affected URL and the parameter/what is wrong with it. Though they did also mention that even with some additional details, we would not be able to solve the problem, as it can be at the platform level. I hope the additional information would let us try and work around it though!

They weren’t able to pass along an expected date for release, though did mention that they usually see some features/improvements added after the holidays.

It seems that at this moment, we’ll need to wait for this release before looking at the Invalid Match Content parameter further as all logging and examples that we were able to find so far showed that we already include the required parameters.

Cheers,

Simon.

Hey @barouzj,

Awesome, thanks! I’ve just sent an email now. I hope that works out and we can get this moving for you! ??

Cheers,

Simon.

Hi @pandeskapl,

These sound like two different issues, so I’d like to make sure we focus on them separately. The previous issue related to ‘Invalid parameter’ which is typically shown when the connection is no longer valid. We suggested resetting the external id and reconnecting for that, yet you mentioned that hadn’t helped. Unfortunately, we couldn’t see the error we’d expect to see in the debug logs for this.

Now it sounds like you are seeing a different error which is typically shown when a product has been synced previously, and has been changed or deleted from the Facebook catalog since then. Facebook responds that it can’t find the ID that was saved from previously and so the product can’t be synced.

To workaround this second issue, you can use the “Reset Facebook metadata” link from the Facebook sidebar metabox: https://cloud.skyver.ge/2Nuj0ZD7 and then try to update the product again.

Could you let us know if the first issue still persists, or how you get on with the workaround for the second issue?

Cheers!

Simon.

Hi @barouzj,

When you submitted the form via our website, you should have received an auto-response back with a conversation ID number. Did you get one of these for any of your submissions so far?

If not, I can see that your Facebook page has an email address listed. Is it okay if I email you there so that we can get connected?

Cheers!

Simon.

Hey @cmgeoogz,

Thanks so much! I’ve got it! I replied just now and we can follow up via the email thread, so let me close this topic for now.

Thanks again for reaching out directly.

Cheers,

Simon.

Hi @davidfranom,

We’ve now heard back from the Facebook team regarding the Invalid Match Key error. They’ve said that they have seen this in their logs, though it should be a rare occurrence.

While they weren’t able to share any logs with me due to privacy concerns, they also mentioned that even with logs, the issue could be a platform issue. Something that we wouldn’t be able to resolve from within the plugin anyway.

They appreciate that it’s difficult to see what is causing the error, and so they’ve added an item to their backlog to improve the user notice, to help add additional information about why the error occurred and which validation failed. They weren’t able to say when this might be released though I’m afraid.

For now, it doesn’t sound like I’m able to do anything further for this issue. I would suggest clearing out the error notice, and if it does continue to crop up, reach out to Facebook directly to see if they have any further news on these improvements.

I’m sorry this isn’t the best of news this time around. I’m going to close this topic now then, but if you have any further questions or issues, please don’t hesitate to contact us again! We’re always happy to help ??

Cheers,

Simon.

Hey @davidbeger,

I’m glad we could run the manual sync again to try and remove the other products. I never heard back from you on the email thread after that, so I hope all is okay now.

I’m going to mark this topic as resolved though. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

You’re also more than welcome to reply back on our email if we need to take another look at the latest sync attempts too!

Thanks,
Simon.