Jonathan Miller
122c7b630a
- Telegram: updated default bot from @MokoWaaSBot to @mokosuite_bot - Telegram: embedded obfuscated bot token in plugin PHP (XOR + base64) - Telegram: added <config> section to plugin XML for parse_mode/preview - Telegram: removed bot token from admin-visible plugin params - Branding: replaced all MokoWaaS references with MokoSuite - Wiki: reorganized into getting-started/, user-guide/, services/, developer/ - README: updated with all 36 service plugins and current features - CHANGELOG: added entries for recent fixes and changes
1.5 KiB
1.5 KiB
Configuration
Navigate to Components → MokoSuiteCross to access the admin panel.
Global Settings
Go to Options (toolbar gear icon) to configure:
| Setting | Default | Description |
|---|---|---|
| Auto-post on Publish | Yes | Automatically cross-post when articles are published |
| Max Retries | 3 | How many times to retry a failed post |
| Retry Delay | 300s | Seconds between retry attempts |
| Log Retention | 90 days | How long to keep activity logs |
| Default Template | {title}\n\n{introtext}\n\n{url} |
Fallback message template |
Message Templates
Templates use placeholders that are replaced with article data:
| Placeholder | Description |
|---|---|
{title} |
Article title |
{url} |
Full article URL |
{introtext} |
Article intro text (stripped of HTML, max 280 chars) |
{image} |
Article intro image URL |
{category} |
Article category name |
{author} |
Article author name |
You can create per-platform templates. The system checks for a platform-specific template first, then falls back to the default.
Service Modes
Services that support universal bots offer two modes:
- Default Mode — Uses the pre-configured MokoSuite bot/app. API keys are stored in the component's encrypted global params and never exposed in the individual service record.
- Custom Mode — You provide your own API keys, tokens, and credentials.
Services supporting default mode: Telegram (@mokosuite_bot), Facebook, Discord, Slack