Sébastien Dumont

I don’t know how you have it returning like it does. I have created a variable product with the same attributes and mine return sanitized and match for both endpoints.

Maybe there is something that you have done differently in the backend that I missed or you have another plugin that filters the attributes but the data fetched is the same.

I have compared the data returning on the products page vs the REST API and they match.

Any other information you can share that might help would investigate further.

This is where you would need to contact your web host for support if the alternative method I linked did not help you.

@pujithamutyala After reviewing the issue, I find it is related to how WordPress sanitize the slugs. The character e and is replaced with a d

I don’t see a way to prevent this.

Hey @guntherf

Seems odd that you would get a CORS issue after coming back. Do you have the CORS add-on installed? This solves most CORS issues.

You can filter the cookie expiration. Have you tried that?

Ah OK so it’s not that the REST API is giving you an error but the server is.

Ideally, your server should be configured to accept these types of API request, but if not you can use the?_method?property.

Yes of course.

@pujithamutyala Thank you for reporting this mismatch. Will review what needs adjusting to fix this and have a patch out asap.

I’m sorry this post is a little vague. You haven’t exactly explained what is not working.

First I see that the item key is provided incorrectly. Why is there “&#8217” at the end of it?
Second you shouldn’t be posting any authentication details in the forum.
Third, not sure I understand why you added [NSFW] after posting. Your store has food products.

Can you share what the response you get from attempting to remove the product?

Hi @kit21

I have had a look at the code for WooCommerce Social Login and I don’t see where there maybe an issue with the session handler triggered wrongly.

Perhaps you can share the steps you took with and without CoCart so I can do the same. Also what configurations you have for the social plugin.

Thank you.

You may want to look at using the Postman interceptor.

Please know that CoCart v4 once released will not be using Cookies via the REST API.

Currently can be beta tested @chrisames See the beta releases for more.

I have added a filter for the authentication header and will be supported in the upcoming v4 of CoCart.

With CoCart we only support standard Authentication header. A filter can be added to change this if you like?

The JWT for CoCart is unique for customer identification. It’s not a standard JWT for back-end purposes that the other JWT plugins do.

If it works in Insomnai then check the headers are getting passed correctly in your code. I find not doing the headers correctly causes the most simple issues that should not be a problem to begin with.

The plugin does work as it should.

I’m curious as to what custom header your referring too?

It’s developed for just CoCart.