I have 2 different problems but probably with the same cause:

• When a user wants to enroll to a course A, the enroll button does not seem to work as it brings back the user to the list of available courses. ==> I see an API Call “/wp-json/lp/v1/courses/enroll-course?_locale=user” by POST method that gets an HTTP 302 code
• When the same user wants to enroll to a course B, the button to start does not even appear as if it was not possible to check the status of the user for this course (can enroll, already enrolled, etc.) => API CALL in POST method “/wp-json/lp/v1/lazy-load/course-progress?_locale=user” gets an HTTP 302 code

In both cases the API does not seem to provide the expected answer but I can’t figure out the problem. I sometimes get an error message telling the JSON Response is not valid.

Any help would be appreciated.

s

Here’s a detailed breakdown of the steps we’ve taken so far:

1. Plugin Installation and Setup:?We installed and set up the official Facebook for WooCommerce plugin. All settings were configured correctly according to Facebook’s guidelines.
2. Pixel Verification:?We verified that the Facebook Pixel was installed correctly on the website. Other events, such as Page View and Add to Cart, are being tracked properly.
3. Testing Events:?We have used the Facebook Pixel Helper and Meta’s Event Testing tool to confirm the tracking. These tools show that the Purchase event is not being triggered, while other events are working without issues.
4. Debugging Attempts:?We have checked WooCommerce settings, confirmed plugin configurations, and even deactivated/reactivated the plugin. None of these steps resolved the issue.
5. Final Observations:?The plugin does not seem to be sending the Purchase event at all. It’s missing entirely from the events tracked on Facebook.

Would anyone have any insights into why the Purchase event might not be triggering? Are there any additional steps we can take to ensure this event is being sent from WooCommerce to Facebook?

Thank you for your help!

It seems I’m having problems with the solution you gave in https://www.ads-software.com/support/topic/api-get_entries-limit-number-of-entries-returned/

The API Forminator_Form_Entry_Model::list_entries() function was working great for about a year, now it’s not working. I needed it to only get results for a particular entry, unlink the get_entries() which shows all entries. Is API Forminator_Form_Entry_Model::list_entries() function still part of the API or has it been removed/changed?

Here’s a detailed breakdown of the steps we’ve taken so far:

1. Plugin Installation and Setup: We installed and set up the official Facebook for WooCommerce plugin. All settings were configured correctly according to Facebook’s guidelines.
2. Pixel Verification: We verified that the Facebook Pixel was installed correctly on the website. Other events, such as Page View and Add to Cart, are being tracked properly.
3. Testing Events: We have used the Facebook Pixel Helper and Meta’s Event Testing tool to confirm the tracking. These tools show that the Purchase event is not being triggered, while other events are working without issues.
4. Debugging Attempts: We have checked WooCommerce settings, confirmed plugin configurations, and even deactivated/reactivated the plugin. None of these steps resolved the issue.
5. Final Observations: The plugin does not seem to be sending the Purchase event at all. It’s missing entirely from the events tracked on Facebook.

Would anyone have any insights into why the Purchase event might not be triggering? Are there any additional steps we can take to ensure this event is being sent from WooCommerce to Facebook?

Thank you for your help!

The Woo Rest API endpoint for a single product broke and started returning the HTML of the shop page a few days/a week back.. (Still a 200 response) So every time I hit the wp-json/wc/v3/products/XXXX endpoint I just get the HTML of the shop page as response.

Is there any known changes/issues with the Rest API? I’m not able to find any.

This is not true for all endpoints. The wc/v3/products endpoint is still working as expected.

What I’ve tried:
– Updating all plugins and themes.
– Disabling plugins.
– Switching to default WP theme.
– Regenerated API keys.
– All tests done on both prod and staging environments.

Not sure where to go from here.

we are using germanized, if that helps (since i don’t know if this is a core-problem or maybe a plugin-problem)

does anybody know what this could be?

This is my configuration:

• Url: https://mysite.com/wp-json/pmpro/v1/has_membership_access
  • Params:
    • post_id (found it in the url of the login page on WordPress)
    • email: email of the registered account
  • Authorization
    • Username: email of the registered account
    • Password: password of the registered account

With this configuration, I have 403 error. What I’m doing wrong?
Other question: where can I find post_id and email? Is my process right?

Thank you!

Here are the specific details of the issue:

1. Request URL:bashCopiar códigohttps://londonwine.com/wp-json/wc/v3/products/9057
2. HTTP Method:
   • PUT
3. Authentication: I’m using basic authentication with the correct consumer_key and consumer_secret.
4. Error Received: The server returns a 405 - Method Not Allowed error, which suggests that the PUT method might be blocked for this endpoint. I am uncertain if this is due to API configuration, server settings, or another restriction.
5. Troubleshooting Steps Taken:
   • I reviewed the WooCommerce API documentation and confirmed that the PUT method should be available for this type of request.
   • I tested the request using tools like Postman and cURL to ensure there was no issue with the request configuration.
   • I checked with my hosting provider to rule out any firewall or server security settings that might block the PUT method.

Could you help me identify why the PUT method is not allowed for this endpoint? Is there any specific adjustment or configuration within WooCommerce or the API that I should verify to ensure that product update requests are accepted?

Any additional guidance would be greatly appreciated, as I am struggling to resolve this issue. Thank you very much for your attention and assistance.

A google search showed me tons of other shelter websites with the same error; I’ve tried replacing the API key + secret to no avail. Anyone have any ideas?

Your recent plugin update,?Analytify Dashboard Widget V5.5.0, breaks the WP Mail SMTP widget. That is, API data is being blocked. Double-checked.?Details: https://prnt.sc/0aoP20KudPQy

Fix needed ASAP.

Thank you!