And that makes sense, Andre.
Because: How would you want to chat without identifying yourself, first? :)
Thus to fix that,
move line #30 in the com file if(ossn_isLoggedin()) { above the two page registrations (line #27)

Hy first of all praise a great idea I think I have tried it now but when I log out and want to go there directly, the error comes on the picture

Thanks ~Z~Man. I've added array verification to prevent those errors now.

Currently it only updates their status when the contact list is updated on new notifications - so i'll add an explicit status check and update at some point.

Theres also now a home button to make it easier to return to the main site.

Fine, with 1.3.1 friends are selectable now ...

But Honey's still producing those 2 warnings
this time in line 113 and 191
and after Botox sent her first message to Honey I got

"Invalid argument supplied for foreach()" in file /var/www/html/components/WebChat/plugins/default/webchat/chat_api.php (line 88)

Well, it doesn't really harm here, but it's no bad idea in general to check returns for something meaningful BEFORE further processing. :)

And: the online state doesn't refresh: Botox logged off, but is still green in Honey's list.

As I said:
Honey and Botox are friends, but Honey never exchanged a message with anyone
Thus, when Honey opens the webchat

$recentMessages = CallAPI ($recentURL , $recentPARAM); is false

you're checking that correctly on #60
but not before the foreach loop
$listMessages is undefined because of the check in #60
so we're getting that second error

Cool thanks for doing that. I get an average of 1s for my chat_api queries on chrome and Edge (Win10). So such a difference is baffling? What hardware are you running on?

I have a Lenovo ThinkCentre Pentium G2030 3.00GHz with 8GB RAM, which is not a particularly fast PC?

Can you tell me how to reproduce the error you received? It sounds like its trying to display messages for a contact where there are none... but I don't know how you got it to attempt to load data for a user not in the contacts list?

I'm currently just populating the contacts using the "recent_messages" API call. So if there are no existing messages, they wont appear. I will grab the friend list and any that dont have a message thread - will appear in the list still... and you'll be able to message them - I'll do that once the basic function works well :)

So here are some results:

As you can see the avarage notif takes something between 6 and 7 secs
(the blue one is a send, sends seem to take a little longer.)
So in the bad case
1. a send has just been issued
2. the next notif will fetch nothing because the send's return is still pending
3. another notif is necessary to fetch the message
thus the 15 seconds I reported (= two notifs plus a little screenwork) make sense

There's another issue I found:
A member who never exchanged messages with a friend before is unable to use Webchat (both friends don't see each other) and my log gives

"Invalid argument supplied for foreach()" in file /var/www/html/components/WebChat/plugins/default/webchat/webchat_page.php (line 110)

"Invalid argument supplied for foreach()" in file /var/www/html/components/WebChat/plugins/default/webchat/webchat_page.php (line 171)

Wow?! I was seeing about 5 seconds and thought that was slow. I'll disable all logging and switch to input instead of post as they may both improve performance.

I'll also have a dive into the service worker component to see how it works and see if I can utilise it for notifications.

The data its pulling back is a tiny amount, and even refreshing the content is done in single divs. Surprised it's taking so long :(

May need to do some performance profiling to see where the delay is happening.

Running 1.3:
Webschat messages are updated now - but with a delay of ~ 15 seconds!
OssnMessages is updating almost immediately

Without an absolute path like /var/www/html/... whatever ... your logs are written into wild

Ok despite chat_api not outputting the correct data to the log file - it all seems to be working! I have incorporated the API extension so thats no longer required, and have changed the Site URL and API Key so they are not hard-coded.