General
Aysali Bot is built to stay lightweight: small widget assets, no heavy front-end framework, and modular PHP on the server. For high-traffic or large databases, you can trim unused features under Settings → General → Performance optimization.
Settings
| Setting | Effect |
|---|---|
| Disable reports | Hides the Reports admin area and stops writing to sb_reports (sb_reports_update returns immediately) |
| Disable articles | Hides the Articles admin area for admins/supervisors with article access |
| Archive old messages | Moves stale conversation messages to sb_archive on scheduled cleanup |
Configure each option only if you do not need that functionality — changes apply after save.
Disable reports
When Disable reports is enabled:
- The Reports navigation area is hidden for admins (
performance-reports). - The system no longer records report metrics (visitors, registrations, direct messages, article views, automations, and similar).
Use this if you do not use analytics inside Aysali Bot and want to avoid background inserts into sb_reports.
Disable articles
When Disable articles is enabled:
- The Articles area is removed from the admin navigation (
performance-articles).
To also hide the knowledge base in the chat widget, disable Settings → Articles → Active (articles-active). The performance toggle alone targets the admin Articles workspace; the widget articles panel follows the Articles Active setting.
Archive old messages
Archive old messages moves message rows from sb_messages to sb_archive when a conversation’s last message is older than the selected interval.
| Interval option | Age threshold |
|---|---|
| After 1 week | 7 days |
| After 2 weeks | 14 days |
| After 3 weeks | 21 days |
| After 1 month | 30 days |
| After 2 months | 60 days |
| After 3 months | 90 days |
| After 6 months | 180 days |
| After 1 year | 365 days |
Leave empty to disable automatic archival.
What happens when messages are archived
- Cron / cleanup —
sb_clean_data()(scheduled maintenance) finds conversations whose latest message exceeds the interval. - Move —
sb_messages_archiviation()copies messages tosb_archive, deletes them fromsb_messages, and sets conversation status code5(archived messages state). - Hidden from lists — archived threads no longer appear in normal admin or visitor conversation lists.
Automatic restore
When a user sends a new message in an archived conversation, the status changes from 5 and sb_messages_archiviation($id, true) restores message history from sb_archive back into sb_messages. The conversation becomes active again with full history.
Manual access
Open the user profile in Users, find the archived conversation, and open it to review or restore history as needed (same restore path when messaging resumes).
Cron requirement
Archival runs inside sb_clean_data(), which is triggered by your instance cron job (same job that purges old visitors and trash). Ensure bot cron is configured on your Aysali/hosting setup or intervals will not apply.
Other performance tips
| Area | Tip |
|---|---|
| Widget load | Embed only on pages that need chat; enable Pusher under Settings → General to reduce HTTP polling when WebSockets are available |
| Rich messages | Disable unused Articles shortcodes and custom HTML blocks |
| Attachments | Offload files to remote storage (Settings → General → File storage) on busy sites |