The next step would be to reset the external_business_id to force a full refresh of the connection. This can be done by adjusting the value in the database. I’d be happy to do this for you, or if you have access to PHPMyAdmin with your host, I’d be happy to offer some steps to do this instead.
If you would like me to take a closer look and adjust this value, please could you raise a support request via our support form?
Or would you like me to list the data that needs to be changed?
I’d prefer to do it myself 🙂
Please tell me what to do step by step.
Sure. The easiest method would be to try:
– Navigate to your options.php page (https://<site_url>/wp-admin/options.php) and search for wc_facebook_external_business_id
– Adjust the value to a new unique setting. For example, if it’s currently listed as skyverge-5f5646a59343a you could use skyverge-new-5f5646a59343a by adding the -new- keyword. This can be anything so long as it’s different from the current setting and uses plain characters!
– Click Save button at the bottom of the page
– Double-check the option saved correctly.
Sometimes, if there are many options in the database, this page will not save correctly. So it’s always a good idea to check it again once it refreshes after saving. The new value should appear. If it doesn’t, you will need to use your database tools such as PHPMyAdmin to adjust the option value in the database instead.
Finally, once the change has been made, try to run through the connection process again.
Could you let me know how you get on?
First method does not work. How to do that directly in PHPMyAdmin ??
You will need to search within the wp_options table for the option_name “wc_facebook_external_business_id“, and adjust the value accordingly. I would recommend searching online for a guide to follow if you would like to do this yourself. For example, this guide explains how to change the “site_url” option: https://www.hostdime.com/kb/hd/wordpress/change-wordpress-site-url-via-phpmyadmin
Instead, you would need to change wc_facebook_external_business_id, not the site_url. I’d also recommend taking a database backup beforehand too.
Could you let me know when you’ve had a moment to change the option and reconnect?
Done… database modified. Reconnected and still same error “invalid parameter”.
Thanks for giving that a go. To confirm that the new external_business_id has been put to use, we’ll want to enable debug logging in the plugin settings, and then try to reconnect. To confirm, you are still seeing the Invalid Parameter error as a red error notice on the plugin settings screen, is that right? Is this immediately after reconnecting or only when navigating to the messenger tab?
To enable debug logging, please navigate to WooCommerce > Facebook and enable “Log plugin events for debugging“. Then please try to reconnect to generate the error, or navigate to the messenger tab if this also shows the error too.
We’d then need to take a look at the debug logs themselves. These can be found at WooCommerce > Status > Logs and looking for the facebook_for_woocommerce log with today’s date. There may be private information included in these logs, and so if you’d prefer, you can email us the log file by first raising a support request at via our support form. Please be sure to mention my name, your handle, or the topic URL so that I can keep an eye out!
Could you let me know when you have a moment to run through that test?
After update to 2.04 error is more specific:
Facebook for WooCommerce error:
Unsupported post request. Object with ID ‘3137911689585885’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api
Above error occured when I was updating https://www.pan-deska.pl/produkt/kronopol-listwa-przypodlogowa-p85-d2583-dab-masala/
- This reply was modified 1 year, 11 months ago by pandeskapl.
Current logs: http://server006671.nazwa.pl/log_20201011.txt
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?
Thanks for your topic, actually i am facing also the same issue.
I have in my product list 9 items, only 2 are synced.
Thanks for your help
Thanks for reaching out about the plugin. I’m sorry to hear that you are experiencing an issue as well. Since you’re not the person who originally started this topic then, per the forum guidelines, would you please start your own topic? We’ll be more than happy to help there 🙂
I’m so confused… I think I’ll just give up.
Or maybe there is a possibility to you to just go in my shop and check everything?
But how to do it safely for me? (I mean how I can be sure that noone else will have acces to my wordpress).
Thank you for your patience here. I understand how it can be frustrating when a plugin doesn’t work as expected.
If you’d like us to take a closer look at your site specifically, we’d be happy to do that. Could I get you to please fill out our contact form so that we can securely gather more sensitive data, like your Business Manager ID, if we need to loop in the Facebook team?
- The topic ‘“Invalid parameter”… and that’s it. Item not on FB.’ is closed to new replies.