Cyrem

Eh it roughly works on 4.2 B4...

Other than the ACP page layouts being a little bit broken, using the bulk advanced tool left me with some glorious work to do:

It started off okay on the first cycle, then for each cycle after than the tag got longer and longer.

18 minutes ago, TAMAN said:

You're right,

good idea  

Sorry, I re-read your reply earlier and just wanted to clarify so that we're on the same page, do you mean adding an option to keep it permanently open unless closed? While that is a useful option, not entirely what I meant.

What I meant was, through use of a cookie, to save the open/close state of a widget. So when a page loads, if the last saved state was open it'll automatically re-open, if it was closed, it will stay closed.

Basically, I would like my site chat widget to be closed on first visit, but if members open it, I would like to to remain open as they browse the forums unless they explicitly close it again.

Hope I made sense

23 hours ago, TAMAN said:

the widget is simply opens and closses on click or refreshing the psge, however, i can add an option to optionally keep it open unless user wants to close it  maybe in next update 

That would be great, I think it would be annoying if you had to open every time in certain use cases, such as mine.

Considering the use case of a embedding a chat widget, will the floating widgets remain open if I change pages (through use of a cookie)? or will I need to re-open the widget?

Firstly, great tutorial!

Unfortunately I've hit a bump, I can't do the ACL setup (VPS), so I've skipped that part and went on to the PHP-FPM section, however after completing everything I get a 502 Bad Gateway error.

What may the cause of this? I assume it might be the fact that the webapp config isn't right without the ACL setup?

EDIT: (Actually it occurs without PHP-FPM running at all)

Maybe I'm being completely blind, I can't find the setting in the group settings?

​Ah yes, good point. Probably a good idea for an article as no doubt this question will come up several times.

​Yes that should be safe, it doesn't modify the database if thats what you mean.

Regarding group visibility, at the end of that file you'll see /* Display */ Return, replace that with:

/* Display */
$visibleToGroups = array(2,4); // 2 = Guest, 4 = Default Admin group
return (in_array(\IPS\Member::loggedIn()->member_group_id,$visibleToGroups) ? $this->output( $members, $memberCount, $guests, $anonymous ) : '');

Add more group id's to that $visibleToGroups array.

EDIT:

You could do the opposite way if it's more suitable so you don't have to edit for new groups.

/* Display */
$hideForGroups = array(2); // 2 = Guest
return (in_array(\IPS\Member::loggedIn()->member_group_id,$hideForGroups) ? '' : $this->output( $members, $memberCount, $guests, $anonymous ));

​Um no thats the SQL result limit and you're actually cutting the amount of results in the query. You probably shouldn't touch that.

Pretty sure you should be modifying the widget not the online module. File: core\widget\whosOnline.php

Make sure you edit times for both member and guest. Hopefully IPS will give this widget an option panel for this, probably just an oversight.