EvdHeuvel

Hi Michiel,

I did some debugging and traced things down to the rest_authentication_errors_filter function. The problem in my setup is related to the fact that the host in $currentUrl differs from the $siteUrl. This is caused by the fact that I’m contacting the end points in WordPress from a separate container. This causes the preg_match to return an error resulting in an 401 error in the client in my other container.

Initally I thought that I could workaround this by setting the Access-Control-Allow-Origin header but I couldn’t get that to work.

Hope this is of some help.

Alright, let me work on that.

I’m running WordPress and an automation tool side by side (Node-RED or OL Connect Workflow). The automation tool fetches a bearer key in order to create and update (custom) posts via custom end points. This works like a charm when running everything on the same box. We use this setup in various on-premise solutions.

I’m currently moving this setup to run on containers to simplify deployment in the cloud. This is where I ran into the CORS challenge.

Encountered the same when setting WP_DEBUG to true.

Proposed fix solved it for me. Thanks!

Agree with @nilsnolde, having additional information in the payload would be great (e.g. use the same object for all routes). It would simplify the integration for my headless setup. +1

Solved the problem.

I forget to set the Action and the accompanying key in the Login section. After changing this to “Log in by WordPress Username” and respectively “username” things work correctly.

Hi Kento,

Believe this is related to PHP version 7.4. Nested ternary operators without explicit parentheses are deprecated. https://www.php.net/manual/en/migration74.deprecated.php

I fixed things by modifying the stated source files in the Groups plugin (obviously not my preference ;)). I’m currently running 2.10.0 of the Groups plugin.

Erik

Never mind, I implemented it such that the external system (OL Connect Workflow) is requesting a token for a specific user account with a specific role. The token is used in subsequent request. It was nice to find out that custom end points with nonce validation where still working properly so there was no need to whitelist these.

Hello Kento,

Just curious ?? Is there a roadmap for the Groups plugin?

Erik

Thanks for the headsup. Excellent news! For now we will work around it and wait for the update.

Erik

Neocreo, were you able to solve this?

Hi Diana,

I noticed that an extra CSS permalink option is now showning when editing standard pages and posts. Think this is not correct, could you verify that?

Erik

Works like a charm… many thanks!

Erik

That would be really great!

Erik

I got the same problem. Did you find a solution?