Hi Siropu,
I’ve gone through the resource description, update history, and support discussion. I’m evaluating Chat 2 version 2.5.9 as the dedicated live-chat layer for a large XenForo 2.3 community. Our normal forums and threads will remain the permanent discussion system; Chat 2 would be used only when members specifically want a live conversation.
I found answers to most of my questions, but I would appreciate current clarification on the following:
AJAX polling and capacity
Does every browser that currently has Chat loaded still make its own independent AJAX polling request at the configured interval?
When the chat is hidden, the browser tab is unfocused, or the member becomes inactive, does polling stop completely or only change to the applicable hidden or inactive interval?
Do you have any recent benchmarks, production experience, or recommended upper range for simultaneous connected clients using version 2.5.9 at the default five-second interval?
Opening or embedding one specific room
We may want to place a Live Chat button on selected pages that opens one corresponding Chat 2 room without loading Chat across the rest of the website.
Is there now a supported method for loading or opening one specific room without using an iframe? For example, is there a supported route, widget parameter, template hook, PHP service, class extension, or JavaScript API that another add-on can use without modifying Chat 2 files?
If an iframe is still the only supported method, can the embedded view show only the intended room without exposing the complete list of other available rooms?
Permission changes and immediate access removal
Can a Chat 2 room inherit or check access against a particular XenForo node’s permissions?
If not, when a member loses an allowed user group or is removed from a room’s permitted users, are they immediately removed and prevented from continuing to read or post, including through a direct room URL, or can they remain until they leave, refresh, or are manually kicked?
Member-facing terminology
Can all member-facing terminology used by Chat 2 be changed through XenForo phrases or the add-on’s normal options, including navigation labels, tabs, notices, alerts, widgets, archive pages, empty states, private-chat wording, and error messages, without modifying the add-on’s files?
Are any member-facing terms hard-coded or otherwise not phrase-controlled?
Development, beta, and production licensing
The current resource page says each installation requires a separate license. I also found your older answer stating that a development installation could use the production domain on the license.
What is the current licensing requirement for one private development or staging installation, one invite-only beta installation, and one eventual public production installation?
Data export, pruning, reports, and uninstalling
Is there a supported full export for Chat 2 data beyond exporting room messages into a XenForo thread? In particular, can room messages, room configuration, memberships, reports, sanctions, reactions, private-chat data, and attachments be exported in a structured form?
When a reported message is automatically pruned or deleted, is the reported content preserved anywhere for staff review?
Does uninstalling the current version cleanly remove all Chat-owned database tables, files, jobs, permissions, navigation entries, and other add-on data, or are there manual cleanup steps?
Accessibility
Has version 2.5.9 been tested for keyboard-only operation, visible focus, screen-reader use, announcements of newly arriving messages, focus retention while messages refresh, 200% zoom, and reduced-motion preferences?
Are there any known accessibility limitations that we should account for during our own testing?
Thank you. I realize this is a detailed list, but I reviewed the existing material first and tried to limit it to questions that I could not find a current answer for.
I’ve gone through the resource description, update history, and support discussion. I’m evaluating Chat 2 version 2.5.9 as the dedicated live-chat layer for a large XenForo 2.3 community. Our normal forums and threads will remain the permanent discussion system; Chat 2 would be used only when members specifically want a live conversation.
I found answers to most of my questions, but I would appreciate current clarification on the following:
AJAX polling and capacity
Does every browser that currently has Chat loaded still make its own independent AJAX polling request at the configured interval?
When the chat is hidden, the browser tab is unfocused, or the member becomes inactive, does polling stop completely or only change to the applicable hidden or inactive interval?
Do you have any recent benchmarks, production experience, or recommended upper range for simultaneous connected clients using version 2.5.9 at the default five-second interval?
Opening or embedding one specific room
We may want to place a Live Chat button on selected pages that opens one corresponding Chat 2 room without loading Chat across the rest of the website.
Is there now a supported method for loading or opening one specific room without using an iframe? For example, is there a supported route, widget parameter, template hook, PHP service, class extension, or JavaScript API that another add-on can use without modifying Chat 2 files?
If an iframe is still the only supported method, can the embedded view show only the intended room without exposing the complete list of other available rooms?
Permission changes and immediate access removal
Can a Chat 2 room inherit or check access against a particular XenForo node’s permissions?
If not, when a member loses an allowed user group or is removed from a room’s permitted users, are they immediately removed and prevented from continuing to read or post, including through a direct room URL, or can they remain until they leave, refresh, or are manually kicked?
Member-facing terminology
Can all member-facing terminology used by Chat 2 be changed through XenForo phrases or the add-on’s normal options, including navigation labels, tabs, notices, alerts, widgets, archive pages, empty states, private-chat wording, and error messages, without modifying the add-on’s files?
Are any member-facing terms hard-coded or otherwise not phrase-controlled?
Development, beta, and production licensing
The current resource page says each installation requires a separate license. I also found your older answer stating that a development installation could use the production domain on the license.
What is the current licensing requirement for one private development or staging installation, one invite-only beta installation, and one eventual public production installation?
Data export, pruning, reports, and uninstalling
Is there a supported full export for Chat 2 data beyond exporting room messages into a XenForo thread? In particular, can room messages, room configuration, memberships, reports, sanctions, reactions, private-chat data, and attachments be exported in a structured form?
When a reported message is automatically pruned or deleted, is the reported content preserved anywhere for staff review?
Does uninstalling the current version cleanly remove all Chat-owned database tables, files, jobs, permissions, navigation entries, and other add-on data, or are there manual cleanup steps?
Accessibility
Has version 2.5.9 been tested for keyboard-only operation, visible focus, screen-reader use, announcements of newly arriving messages, focus retention while messages refresh, 200% zoom, and reduced-motion preferences?
Are there any known accessibility limitations that we should account for during our own testing?
Thank you. I realize this is a detailed list, but I reviewed the existing material first and tried to limit it to questions that I could not find a current answer for.
