Jeremy Pry

@glashkoff

All old events have the status “Failed”. Their log shows that they run from 6 to 15 minutes.

Typically these log entries should also include an error message when a failure occurs. This will be in the far right column labeled “Log”. Could you copy the log data from that column here so we can see what is happening?

The second problem (it is impossible to open /wp-admin/edit.php?post_type=product) I managed to solve by forcibly deleting the “Facebook sync” column in the plugin code. Unfortunately, not all sites can turn off this column manually through the admin interface, because the list of products does not open due to the expiration of the PHP script timeout.

If you (or anyone else finding this later) needs a way to turn this off in the future, here is a link to a method for disabling these columns without being able to access the screen in question: https://gist.github.com/JPry/a701f30f3d99d5b5479801788bad415e.

Hi @eva73,

That message in your log is just a warning, not an error. Could you tell me where you are seeing it, meaning is this in a particular log file? Are there other messages as well related to the Facebook for WooCommerce extension?

That kind of error should only happen if there is an unusual response from the Facebook API. If it just happens a few times, then it shouldn’t be something to be concerned about. But if it is happening regularly, that’s something that we should investigate.

@bjorngus Please start your own thread instead of posting in this one.

@glashkoff

Just in case, I will clarify why I wrote that storing a job in wp_options is an undesirable solution.

Thank you for your explanation. We do understand why it is desirable to avoid using the wp_options table, for all of the reasons you specified. Unfortunately, reworking the database storage is not something we’re able to do in the near future. But since this plugin is open-source, you’re welcome to submit an issue and/or pull request on the public repository.

There are not so many of them with failed. Most tasks with the status “completed”.

It sounds like the action to clean up the old rows is either not running at all, or it is failing when it does run. If you go to the Admin Dashboard, then WooCommerce > Status > Scheduled Actions, you can use the search field to search for facebook_for_woocommerce_daily_heartbeat. Does it seem like many of these are either “Pending” or “Failed”?

@polsola

Sorry but it doesn’t seem to be any log from facebook_for_woocommerce there

That seems unusual. Could you check to see if there’s anything prefixed with fatal-errors?

Could you also paste your status report here?

As a result, after a while I got more than 75,000 entries of the form wc_facebook_background_product_sync_job_* in the wp_options table. It’s not normal, is it?

No, this is not normal. Background processes that have completed are cleaned up daily. For you to have this many left in your database means one of two things:

1. Your jobs aren’t being marked as completed, and therefore are not being cleaned up.
2. Your background process isn’t running daily as it should.

If you look in the database at the option_value column, you should see some JSON for the job. Would you be able to paste the JSON here from some of the oldest jobs?

Hi @polsola,

We’ll need to get more information to determine what needs to be done to resolve your issue. To get more information about the error, navigate to Dashboard > WooCommerce > Status > Logs. In the log name drop-down on the right side of the screen, look for one that begins with facebook_for_woocommerce, and select the one with the most recent date. Then click the “View” button that is to the right of that drop-down.

Once you’re viewing the log file, please copy and paste the contents here.

Hi @mate2193,

It shows a 503 Service Unavailable error.

That kind of an error means that there’s an issue with your server. That could be from the plugin conflict you mentioned previously, but it could also be a different issue entirely. Could you check your website logs to see whether there is a new error message or any additional information?

It might also be worth asking your website host to see if they can help you find more information about what that error means so that we can understand what the next step is to get it resolved.

Hi @mariosnft,

Looking at the source code for your site, I can see the following comment before the pixel code:

 <!-- Facebook Pixel Code -->

Our plugin only uses this exact comment for a <noscript> tag, but not for the mail pixel script.

Do any of your other plugins include Facebook functionality as a feature?

Hi @felipexa,

Thanks for flagging this. We are tracking this issue on GitHub already.

Hi @advansys,

It looks like the changelog is being pulled from WooCommerce, and it seems that it is pulling an older version. This is being tacked on GitHub.

You can view the up-to-date changelog directly on the plugin page here on www.ads-software.com: https://www.ads-software.com/plugins/woocommerce-payments/#developers.

Hi @virgiliosantos,

Are you talking about a callback script within JS, or within PHP? If you’re talking about JS, then you should be able to attach to the same event handler that the form itself uses:

$( 'body' ).on( 'submit', '.yikes-easy-mc-form', function() {
    // Do your stuff here.
} );

If you wanted something more specific within the Easy Forms, it could be a feature request to have an event trigger within our own code.

Hi Rainer,

Based on the error message you mentioned, I think there might be a problem with the merge variables that the API is receiving. Here are the different things I think might be wrong:

• The merge variable named XFNAME might be incorrect. Double-check that this is the correct variable name in MailChimp.
• The API could be giving an error because you’re sending an empty value for the merge variable in some cases. I would suggest modifying your code to send the data if it exists in your form, but don’t set the variable at all when that data is not present in the form.
• It’s possible that the data being added to the merge variable is posing a problem to the API. This could mean that the data needs to be cleaned or processed more before being sent to MailChimp’s API.

In your previous messages, you mentioned a few different filters, and you provided a few different code samples. Could you provide a full sample of the code you’re using, as well as the exact error response that you’re seeing? That would make it easier to help troubleshoot what’s going wrong.

Thanks,
Jeremy

• This reply was modified 7 years, 3 months ago by Jeremy Pry.

Hey @csigncsign,

I’m glad that we got that error resolved, and I’m also glad to hear that a re-import didn’t cause the problem again.

I’ve logged an issue on our GitHub tracker to fix this error permanently, regardless of any bad option value like your site had.

Hi @csigncsign,

Could you remove the contents of that field entirely, and then use the “Save Changes” button at the bottom of the screen? Make sure not to modify any other values there.

Once you have done this, can you tell me if you are still seeing an error?

Hi @csigncsign,

Could you visit wp-admin/options.php (not options-general.php) on your site? Once there, look for the optin-checkbox-init option. Is it a disabled field that says SERIALIZED DATA, or is it some other value?

Thanks,
Jeremy