Error login through WP
-
I am having issues logging into the system through wordpress… it woks fine when going to the site directly and login, but it will not through wordpress plugin.
First i got the message saying “something went wrong” “forbidden”
Then after i got “something went wrong” “Failed logging in, please verify your credentials.”
-
It sounds like there’s an error occurring when you try to authenticate with SimplyBook via the WordPress plugin, and the generic “Something went wrong” message likely appears as a result of this.
Could you navigate to the SimplyBook plugin once more, then open the Developer Tools -> “Console” tab of your browser (the shortcut is Ctrl + Shift + J in Google Chrome on Windows) and try logging in once more, while you have the Console tab open?
If the login fails once more, you should see related error messages with more information about the issue being logged to the Console. Please attach those in your reply to this thread, and we’ll have a look at those.
Kind regards, Jarno
-
This reply was modified 11 months, 2 weeks ago by
Jarno Vos.
i am on a macbook air, using chrome… where do i find the developer tools option ?
You can press Command (⌘) + Option + J in Chrome on MacOS to open the Developer Tools -> Console tab directly.
Alternatively, you can click the three dots (⋮) in the top right corner of your browser, then select More Tools -> Developer Tools and select the Console tab in the new window that appeared.


still comes with this error
Yes, this approach will not fix the issue; but it should log more information about the underlying cause of the “Something went wrong” error to the Console tab in the Developer Tools window when the login fails.
As described in my initial post: if you share the errors as listed in the Console tab when the login fails, that would allow us to have a closer look at those and determine what’s going on here.
Kind regards, Jarno
okay, i am not a computer genius in this sense – so i need to know exactly what it is you want to see, should i copy paste the whole console tab content or what do you need from my side to check more into it ?
There should be error message(s) marked in red, but you could also copy everything that you see in the Console (after producing a failed login with the Console tab opened) and paste it here; and I’ll figure it out.
Kind regards, Jarno
this is what you are looking for ?
this
for some reason it will not add the screenshot of the console to the post so i copy pasted the text in the console :
JQMIGRATE: Migrate is installed, version 3.4.1
2index.js?ver=8e5255b941ea5095845b:1 The notFoundRoute API is deprecated and will be removed in the next major version. See https://tanstack.com/router/v1/docs/framework/react/guide/not-found-errors#migrating-from-notfoundroute for more info.
update @ index.js?ver=8e5255b941ea5095845b:1Understand this warning
api-fetch.min.js?ver=3623a576c78df404ff20:2POST https://www.intfanregister.site/tedgolf/wp-json/simplybook/v1/onboarding/auth?token=zndt9&_locale=user 500 (Internal Server Error)j @ api-fetch.min.js?ver=3623a576c78df404ff20:2
h @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
P @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
o @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
P.method.t @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
o @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
r @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
g @ api-fetch.min.js?ver=3623a576c78df404ff20:2
(anonymous) @ api-fetch.min.js?ver=3623a576c78df404ff20:2
A @ api-fetch.min.js?ver=3623a576c78df404ff20:2
R @ 843.js:1
(anonymous) @ 843.js:1
(anonymous) @ 201.js:1
await in (anonymous)
Xa @ react-dom.min.js?ver=18.3.1.1:10
B @ react-dom.min.js?ver=18.3.1.1:10
W @ react-dom.min.js?ver=18.3.1.1:10
qe @ react-dom.min.js?ver=18.3.1.1:10
Ke @ react-dom.min.js?ver=18.3.1.1:10
(anonymous) @ react-dom.min.js?ver=18.3.1.1:10
dl @ react-dom.min.js?ver=18.3.1.1:10
V @ react-dom.min.js?ver=18.3.1.1:10
Je @ react-dom.min.js?ver=18.3.1.1:10
pe @ react-dom.min.js?ver=18.3.1.1:10
fe @ react-dom.min.js?ver=18.3.1.1:10Understand this error
843.js:1 {message: ‘Failed logging in, please verify your credentials.’, status: ‘error’, data: {…}, request_success: true}Great, the text version would be sufficient as I don’t necessarily need a screenshot.
However, in your copied text the
data: {…}section isn’t visible entirely, this has to be ‘expanded’ first by clicking the arrow in front of it, which will reveal it’s contents.Could you expand the “data: {…}” section as well, and then copy and paste all of the console errors once more (just like you did previously) and attach them here again? I’ll attach a screenshot below to better clarify how to do that.

Kind regards, Jarno
this ?
{message: ‘Failed logging in, please verify your credentials.’, status: ‘error’, data: {…}, request_success: true}- data: {message: ‘Failed logging in, please verify your credentials.’, data: {…}}
- message: “Failed logging in, please verify your credentials.”
- request_success: true
- status: “error”
- Prototype: Object
Almost there; but I’d need the expanded
data: {...}part as well. In your copied text this was still “minimized”.Please see my instructions above on how to expand that section, after which you can copy the error message again and share it here. The data section should look like this once it has been expanded.

okay expanded them all so hope its all good now
- {message: ‘Failed logging in, please verify your credentials.’, status: ‘error’, data: {…}, request_success: true}
- data:
- data:
- response_code: 400
- response_message: “Invalid login or password”
- Prototype: Object
- constructor: ƒ Object()
- hasOwnProperty: ƒ hasOwnProperty()
- isPrototypeOf: ƒ isPrototypeOf()
- propertyIsEnumerable: ƒ propertyIsEnumerable()
- toLocaleString: ƒ toLocaleString()
- toString: ƒ toString()
- valueOf: ƒ valueOf()
- __defineGetter__: ƒ __defineGetter__()
- __defineSetter__: ƒ __defineSetter__()
- __lookupGetter__: ƒ __lookupGetter__()
- __lookupSetter__: ƒ __lookupSetter__()
- __proto__: (…)
- get __proto__: ƒ __proto__()
- set __proto__: ƒ __proto__()
- message: “Failed logging in, please verify your credentials.”
- Prototype: Object
- constructor: ƒ Object()
- hasOwnProperty: ƒ hasOwnProperty()
- isPrototypeOf: ƒ isPrototypeOf()
- propertyIsEnumerable: ƒ propertyIsEnumerable()
- toLocaleString: ƒ toLocaleString()
- toString: ƒ toString()
- valueOf: ƒ valueOf()
- __defineGetter__: ƒ __defineGetter__()
- __defineSetter__: ƒ __defineSetter__()
- __lookupGetter__: ƒ __lookupGetter__()
- __lookupSetter__: ƒ __lookupSetter__()
- __proto__: (…)
- get __proto__: ƒ __proto__()
- set __proto__: ƒ __proto__()
- data:
- message: “Failed logging in, please verify your credentials.”
- request_success: true
- status: “error”
- Prototype: Object
- constructor: ƒ Object()
- hasOwnProperty: ƒ hasOwnProperty()
- isPrototypeOf: ƒ isPrototypeOf()
- propertyIsEnumerable: ƒ propertyIsEnumerable()
- toLocaleString: ƒ toLocaleString()
- toString: ƒ toString()
- valueOf: ƒ valueOf()
- __defineGetter__: ƒ __defineGetter__()
- __defineSetter__: ƒ __defineSetter__()
- __lookupGetter__: ƒ __lookupGetter__()
- __lookupSetter__: ƒ __lookupSetter__()
- __proto__: (…)
- get __proto__: ƒ __proto__()
- set __proto__: ƒ __proto__()
- data:
Yes, perfect. This error message should really only appear if invalid login details have been entered during sign-on, so that certainly seems to be causing this issue.
You will find the your sign-on credentials in the initial Registration information mail that you received from SimplyBook. The screenshot below elaborates on where to find the information for each of these fields.

Kind regards, Jarno
-
This reply was modified 11 months, 2 weeks ago by
The topic ‘Error login through WP’ is closed to new replies.