DFX Feed for Telegram Channels mirrors messages from one or more Telegram channels onto your WordPress site. Messages are fetched via a Telegram bot you control, stored locally as a custom post type, and rendered through a shortcode, Gutenberg block, or Elementor widget. Both public and private channels are supported.<\/p>\n\n
dfxfftc\/feed.php<\/code> or dfxfftc\/browser.php<\/code> into your theme to fully customize the output.<\/li>\n- Works with private channels<\/strong> if your bot is admin in them.<\/li>\n<\/ul>\n\n
Usage<\/h3>\n\n\n- Use
[dfxfftc_channel_feed channel=\"yourchannel\" count=\"5\"]<\/code> to show the N latest messages.<\/li>\n- Use
[dfxfftc_channel_browser channel=\"yourchannel\"]<\/code> to show the full channel history.<\/li>\n<\/ul>\n\nBehaviour and known limitations<\/h3>\n\n\n- Bot-only access.<\/strong> Messages are fetched via the Telegram Bot API, which only sees posts that arrived in the channel after the bot was added. There is no access to historical messages from before that point.<\/li>\n
- Background refresh every 2 minutes.<\/strong> The plugin schedules a WP-cron task that pulls fresh updates from Telegram for every channel you have stored data for. This keeps the local feed within ~2 minutes of the live channel without any manual action. Note that WP-cron only fires when traffic hits your site \u2014 on low-traffic installations you may want to disable WP-cron and trigger
wp-cron.php<\/code> from a real system cron job for reliable execution. The on-demand refresh on frontend visits is also kept as a fallback.<\/li>\n- Edits sync automatically.<\/strong> When a message is edited in Telegram, the local copy is updated on the next refresh and a small \"(edited)\" marker is shown next to the date.<\/li>\n
- Deletions are not syncable automatically.<\/strong> The Telegram Bot API does not notify bots about channel message deletions \u2014 there is no
deleted_channel_post<\/code> update type. To remove a message that has been deleted in Telegram from the local feed, use the per-message \"Move to Trash\"<\/strong> admin row action. Trashed messages are sticky: refresh will not bring them back.<\/li>\n- Hide vs. Trash.<\/strong> Use Hide<\/strong> to keep a message in the database but suppress it on the frontend (reversible via \"Unhide\"). Use Move to Trash<\/strong> for a permanent local removal.<\/li>\n<\/ul>\n\n
External services<\/h3>\n\n
This plugin connects to the Telegram Bot API<\/strong> to fetch channel messages, resolve media file URLs, and verify bot credentials.<\/p>\n\nWhat data is sent<\/h4>\n\n\n- Bot token<\/strong> (configured in Settings) \u2014 sent with every API call to authenticate your bot.<\/li>\n
- Channel username or ID<\/strong> \u2014 sent when fetching messages via
getUpdates<\/code> and when testing the bot configuration via getChatMember<\/code>.<\/li>\n- File IDs<\/strong> \u2014 sent when resolving media URLs via
getFile<\/code> so the plugin can proxy photos, stickers, and video thumbnails to the frontend without exposing the bot token.<\/li>\n<\/ul>\n\nWhen data is sent<\/h4>\n\n\n- On every WP-cron background refresh cycle (every ~2 minutes when site traffic is present).<\/li>\n
- On frontend page loads when the on-demand refresh fallback fires (at most once per 10 minutes per channel).<\/li>\n
- When an admin clicks \"Refresh Messages\" in the admin list page.<\/li>\n
- When an admin clicks \"Test Connection\" on the Settings page.<\/li>\n
- When a visitor views a page containing a message with media (the media proxy fetches the file from Telegram on first access and caches it locally).<\/li>\n<\/ul>\n\n
Service provider<\/h4>\n\n
Telegram Bot API, provided by Telegram FZ-LLC.<\/p>\n\n
\n- Terms of Service: https:\/\/telegram.org\/tos<\/li>\n
- Privacy Policy: https:\/\/telegram.org\/privacy<\/li>\n
- Bot API documentation: https:\/\/core.telegram.org\/bots\/api<\/li>\n<\/ul>\n\n
License<\/h3>\n\n
GPL v3 or later<\/p>\n\n\n