Plugin POST route 404...But logic is executed...HUH?

[sunnyson]

@bvgsoftware

Right now if the token is missing or not valid, I am outputting a url to the terminal. I then click that url, go through the google oauth, and get redirected back to the admin homepage. I then copy and paste the code url param from the browser back into the terminal - this triggers the token to be saved to a json file.

You can use puppetry to automate that process.

@bvgsoftware

Flattening out callbackville worked somewhat. As long as the token is valid it returns 200. My only issue is the authorization.

That means some of your functions return something that causes 404. I would write all that custom login into a custom service with try-catch instead of writing all the logic in the controller.