Forum Plugins: Supported Platforms, Setup, and Reliability

If your goal is to let forum admins plug directly into ImgLink, the most reliable approach is API-first + official adapters.

Important Reality: “All Forums” Means Categories, Not Infinite One-Off Builds

There are thousands of forks and custom forum stacks. No vendor can realistically maintain unique first-party plugins for every single fork forever.

The reliable way to support "all forums" is:

1. Build and maintain official plugins for major engines
2. Provide one stable integration API that any custom forum can call
3. Provide reference adapters and SDKs so self-hosted/custom communities can integrate quickly

This gives near-universal compatibility without fragile one-off integrations.

Officially Supported (First-Party Targets)

These should be your first-class, officially maintained plugins:

Modern major platforms

- Discourse
- XenForo 1/2
- Invision Community (IPS)

Classic / legacy still widely used

- phpBB
- vBulletin (3/4/5 where plugin hooks allow)
- MyBB
- Simple Machines Forum (SMF)
- Flarum

Community-Supported / Adapter Model

For everything else, publish a compatibility layer and let maintainers ship adapters:

- Vanilla Forums / Higher Logic variants
- NodeBB
- WoltLab Suite / Burning Board
- PunBB / FluxBB derivatives
- bbPress (WordPress forums)
- BuddyPress group forum flows
- Custom in-house forum codebases

Universal Compatibility Through API

Any forum can be supported if it can make HTTPS requests.

Required integration capabilities

- Upload image binary or URL-to-import
- Receive direct URL, viewer URL, thumbnail URL, BBCode, Markdown, and HTML
- Delete media by remote ID
- Validate API key / token
- Return structured error codes

Reliability requirements

- Idempotency keys for upload retries
- Request signing and scoped keys per forum
- Queue + retry backoff for temporary failures
- Rate-limit headers and predictable 429 behavior
- Webhook/event log for observability

Support Matrix Strategy

Use these support levels publicly:

- Tier A (Official): fully maintained by ImgLink, SLA-backed bug fixes
- Tier B (Verified Community): reviewed adapter, tested against API contract
- Tier C (Custom API Integration): works via API, no first-party UI/plugin package

This lets you claim broad compatibility honestly while keeping admin trust high.

Admin Setup Checklist (Reliable by Default)

1. Generate a forum-scoped API key in ImgLink dashboard
2. Restrict key by scope (upload/delete/read) and optional IP allowlist
3. Install plugin/adapter package in forum admin panel
4. Run built-in diagnostics:
- Auth test
- Upload test
- Thumbnail test
- Delete test
5. Enable queue mode + retry for background media handling
6. Confirm logs are visible in both forum admin and ImgLink dashboard

Download and Installation Model

Use one central hub page with:

- Official plugins (signed release zips)
- Version compatibility table
- Changelog + breaking changes
- Migration guides
- Fallback “Generic API Adapter” package

Live plugin hub: https://imglink.cc/tools/forum-plugins

What to Tell Admins Clearly

Use this exact expectation setting:

"ImgLink supports all major forum engines natively and any custom forum through our API adapter contract. If your forum can make HTTPS requests, it can integrate."

That statement is true, scalable, and reliable.

Recommended Rollout Order

1. XenForo
2. Discourse
3. Invision
4. phpBB
5. Generic Adapter SDK (for all others)

Related

- API Docs
- Image Hosting for Forums
- Image Hosting for BBCode Forums