Plugin Support
Laszlo
(@laszloszalvak)
Hi @eric410637340
Have you managed to fix the problem?
Since I tried to login with the Google button on the linked page, and the login worked fine for me.
No, I have currently disabled the JetEngine plugin, do I need to enable it?
Plugin Support
Laszlo
(@laszloszalvak)
Hi @eric410637340
Yes, please enable it and then I will check what is happening exactly.
Plugin Support
Laszlo
(@laszloszalvak)
Hi @eric410637340
I checked the login with Google again and the problem seems to be connected to the “prompt” GET parameter. When Google redirects the user back to your site (after a successful authentication and authorization), Google automatically adds the “prompt” query string to the URL, and probably JetEngine has a problem with that parameter name.
Actually if you inspect any other of your pages on the linked site, with the the prompt GET parameter added, e.g.:
(replace example.com with your own domain name) then the same 404 error will occur.
So this problem can only be fixed on the end of JetEngine, they could probably tell you why they throw a 404 error in these cases.
If they have an option to prevent their codes from running in certain requests, then doing so:
- in case of the requests with the “loginSocial” GET parameter
- or for the URLs of the pages that you selected for our “OAuth redirect uri proxy page” and “Page for register flow” settings
should fix the problem.
According to your description, I went to the previously added custom post type “Prompt”, which is the “Edit Post Type” page, and changed the “Prompt” in the “Post Type Name” option field to “Prompt post”.
And change the “prompt” in the Post Type Slug option field to “prompt-post”.
Now it has returned to normal, and visitors can log in to the website with their Google accounts normally, thank you for your help.
Picture: https://tinypic.host/i/ocHK7Q
Plugin Support
Laszlo
(@laszloszalvak)
Thank you for your feedback @eric410637340 !
So the query string conflicted with the custom post type created by JetEngine. I am glad you were able to fix that.
In this case I mark this topic as resolved.
Best regards,
Laszlo.