Just wondered if there's an issue with the current version of Safari and the sites? 

On my site, from time to time, on Safari on my Macbook the page locks up and then I get a message about the page taking too long to load and I have to reload the page. It happens mainly when I put up any pics. It's not a major issue, just a niggle. Wondered if it's just my end or it's something that has been happening to others?

There are no issues with safari that I am aware of, and I use safari quite a substantial amount of the time myself

No issues for me and I use Safari for both mobile and desktop almost exclusively. 

Edited August 10, 20231 yr by Randy Calvert

 

I use Safari for both mobile and desktop almost exclusively. 

I have great disdain for Safari. lol

We recently implemented some dynamic dropdowns which utilize jquery to populate the fields via ajax calls to a php script.  For whatever reason, they work perfectly on windows, linux, and android using a variety of browsers, and even with iPad and iPhone, but NOT with the latest version of Safari for iMac and Macbook.  I'm sure I'll figure it out, but it just goes to show Apple implements things quite differently from everyone else (even themselves! lol)

I've had a member report that he cannot login using his iPhone but can with his iPad.  This is a screenshot of what he gets and there is nothing in the logs.  What does the code on the bottom right mean?

2S119/1 means that they are banned. You will want to ensure that their IP address isn't in your ban settings in ACP -> Members -> Ban Settings.

I've checked and there are no ip bans, just one "Non-Registrable Name".

Ahh, the member has changed their password.  If they had tried and locked themselves out would they have got the same error code?

They shouldn't get this warning unless they try to access something and they don't have access. Locking themselves out would render a different error on the login form that states they're locked out.

Thanks for the info Jim. I am waiting for a further response from the member, having reset their password may have solved the issue.

How did you work out what the error code meant, is there a list of them somewhere?

 

How did you work out what the error code meant, is there a list of them somewhere?

I have our codebase open here and just searched it using an IDE 🙂 .

Ah, understood. They are like markers where the code stopped before outputting that error page.  Good the know thanks.