|
ChiroEurope
|
January 23, 2024 at 12:27 pm
Hi, within the last week we now have an issue that (at least this example) the url generated by EE for the invoice is leading to a critical error on the website page. https://chiroeurope.com/?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=invoice&context=purchaser&token=1-8e811f41fd8e34f8ac74e98d707f556b&GRP_ID=14&id=862
|
|
Tony
|
January 23, 2024 at 1:19 pm
Hi there,
A critical error will save a ‘Fatal error’ within the server error logs, can you check those logs and post the error here, please?
|
|
ChiroEurope
|
January 25, 2024 at 2:49 am
Sorry for the delay, had to find out how to find that. And of course now I can’t reproduce the error. If it happens again, I know what you need to see.
|
|
Tony
|
January 25, 2024 at 6:31 am
Just to note, I’m still getting the critical error on the link provided so the error from that one should be logged on the server.
|
|
ChiroEurope
|
January 26, 2024 at 12:20 am
Yes you’re right. I found an error_log file in public_html/wp-admin but the last record there is for 2 May 2023.. Is this the wrong place to be looking?
|
|
Tony
|
January 26, 2024 at 2:40 am
It depends on your host and how the server is set up, but if the last record was 2 May 2023, that’s the wrong file.
WHat you can do is add this:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
To your wp-config.php file to enable error logging.
Then visit the above link to throw the error and look in /wp-content/debug.log for the error.
|
|
ChiroEurope
|
January 26, 2024 at 4:05 am
I can’t code. You still have admin access to the site. Is this somethign you can do ? Otheriwse I get my IT to set it up.
|
|
Tony
|
January 26, 2024 at 4:58 am
We don’t save credentials so if you’ve sent them in the past we no longer have them.
I can do the above if you can send over FTP credentials using this form:
https://eventespresso.com/send-login-details/
|
|
ChiroEurope
|
January 29, 2024 at 9:47 pm
Just checking. You should have received my details via link Sunday.
|
|
Tony
|
January 30, 2024 at 6:10 am
Hi there,
The error you are getting is:
PHP Fatal error: Uncaught TypeError: Return value of EE_Line_Item::desc() must be of the type string, null returned
We fixed that in version 5.0.13.p+, as your currently using 5.0.12.p you’ll need to update to the latest version (currently 5.0.16.p) to fix this.
|
|
ChiroEurope
|
January 30, 2024 at 6:37 am
OK. Done.
Can you provide a solution to the app login please?
|
|
Tony
|
January 30, 2024 at 6:48 am
OK. Done.
Great, the above link no longer throws an error.
Can you provide a solution to the app login please?
Which app login issue?
The one from here?
https://eventespresso.com/topic/unsupported-url-error-on-event-app/
|
|
ChiroEurope
|
January 30, 2024 at 11:55 am
Ahh. I wrote it all in the message block for the FTP credentials.
On the weekend I used 5 differnt logins to try and get the app to see my events so I could register attendees I included using the login I set up for you, and all of them threw the same error (I sent a screen shot). And yes it is the same error from early 2023 or late 2022, I forget when that was. No access to the app at all.
|
|
ChiroEurope
|
January 30, 2024 at 12:27 pm
I just read though the old thread – as far as I recall those issues were resolved, and the main thing I was focusing on was the capabilities. Since this time I couldn’t even log onto the app.
|
|
Tony
|
January 31, 2024 at 5:39 am
Ahh. I wrote it all in the message block for the FTP credentials.
Ah, ok. So there wasn’t any context with that message so thought it was related to the above error.
On the weekend I used 5 differnt logins to try and get the app to see my events so I could register attendees I included using the login I set up for you, and all of them threw the same error (I sent a screen shot).
Register attendees using the app?
The app allows for ticket scanning, you can’t register attendees onto event using the app. Unless you are using the term register for what we would class as check in?
And yes it is the same error from early 2023 or late 2022, I forget when that was. No access to the app at all.
Previously I could log in via the app so I couldn’t view this.
I’ll set up the proxy I use for this and check now.
|
|
ChiroEurope
|
January 31, 2024 at 6:45 am
Sorry, it was just easier to send you all the info in one message I thought.
I keep using the wrong terms, I meant I cannot logon to the app to check people into an event. Im not using it to register people, poor choice of words. As mentioned I attempted to login and view the events using 4 different emails, none of them worked – all gave the same error as per the screen shot sent.
|
|
ChiroEurope
|
January 31, 2024 at 6:49 am
3 missing permissions read _events, read_other_events & read_private_events.
|
|
ChiroEurope
|
February 2, 2024 at 4:32 am
Hiya, do you need more info from me ?
|
|
ChiroEurope
|
February 6, 2024 at 12:37 pm
Hello Tony, Im not getting any response from you on this. What happened when you set up the proxy?
|
|
Tony
|
February 6, 2024 at 5:16 pm
Hi there,
My apologies, I’ve been digging into this but didn’t want to reply with a “I don’t have any answers just yet” message, yet that is what I’m having to do currently.
Loading the connection through the proxie allows me to easily view what is happening on the requests… but… they appear normal.
I was waiting on some feedback on where to go from this point, which I’ve not tested and get the same results.
I’d like to add some debugging code to the site to view where exactly the request makes it too, right now it looks like the authorization headers isn’t being processed but I also noticed that users have multiple roles on your site which may also be affecting this.
So I’d like to work through the auth steps to confirm if it makes it through that. I’d need to enable WP_DEBUG_LOGGING on the site and then add some code to view the requests, as you’ve provided details to file manager I can do that on my end.
Is that ok?
|
|
ChiroEurope
|
February 7, 2024 at 12:52 am
All good – ‘I like the ‘Im still looking into it’ message !!
Yes by all means. Does it help to say that the error message also appears 3 times when I try to log in? But I suspect that is related to the 3 permissions that are missing.
|
|
Tony
|
February 7, 2024 at 2:18 am
To explain that one, the app sends multiple requests when you log in.
The 3 requests that require authentication are failing so they return missing permissions and you see that for each request on the app. I don’t think this is a permissions issue as such, I think either the request is unauthenticated OR the multiple roles are messing something up. Right now it looks like something is preventing the authorization headers on the request or hooking in before EE’s code runs and doing something weird, that’s why I want to add some additional code and see where it gets up to.
|
|
ChiroEurope
|
February 7, 2024 at 7:16 am
OK. The accounts I used are a variety of mostly test accounts, so all of them have subscriber, some are admin, some have added content access, and then I added the Event App capability to all of them. I also figured the variety of them might help make it work (at the time I was trying to log in)
|
|
Tony
|
February 7, 2024 at 9:00 am
So the issue is from the reCaptcha plugin enabled on the site.
The REST request authenticates with the details passed and it’s not expected to use reCaptcha for those logins, what’s happening is the details are being passed correctly but then the function used to submit the log details returns a reCaptcha error (because you can’t ‘complete’ a reCaptcha over REST) and no login is allow… no long means no user, no user means no capabilities.
You can test this by going to Dashboard -> reCaptcha.
Disable the reCaptcha on the login form:
https://monosnap.com/file/Pcev4TVYXlz0upY6PglonUYdcJxPKz
Save the settings there and then try logging in with the app. It works fine for me that way.
|
|
ChiroEurope
|
February 7, 2024 at 1:30 pm
OK wow, wouldnt have thought that might be an issue. However the whole reason we have reCaptcha is that we had months of card testing through our site. Hundreds of attempts every day for months, stripe gave us less than zero help to resolve it, in fact they were intentionally unhelpful, and part of the solution was to halve reCaptcha at login. if i disable it, we open ourselves back up to this problem .
|
|
ChiroEurope
|
February 8, 2024 at 11:28 am
Hiya, true to be said I didnt ask a question, but my concern is that disabling reCaptcha, which I have not done nor tested, was because of the massive number of fraud attempts made on site in part that were stopped through having reCaptcha at login. Could I disable it long enough to login, then reenable ?
|
|
Rio
|
February 8, 2024 at 8:00 pm
What security plugin/tools you’re using for your site? this might be your alternative for your concern.
thanks
|
|
ChiroEurope
|
February 9, 2024 at 2:44 am
we use sitelock from Buehost, and reCaptcha. No plug in security tools as they are not that secure.
|
|
Tony
|
February 9, 2024 at 8:01 am
For this to work, you’ll need to find a reCaptcha plugin that allows you to either disable it on REST API requests via setting or one that allows you to hook in and disable it via custom code with a hook.
The current reCaptcha plugin you are using doesn’t allow for this and I don’t currently know of one that does. You are right to want to keep reCaptcha enabled but REST request can not complete reCaptcha so it needs to be disabled for those.
|
|
ChiroEurope
|
February 9, 2024 at 11:42 pm
Ok , thanks Tony, good to know the problem finally, and potential solutions. Appreciate your help.
|
