Support two-way message replies and quotes for Telegram forum topics and webhooks - #78
Open
mysubcult wants to merge 1 commit into
Open
Conversation
mysubcult
force-pushed
the
feature/telegram-topic-reply-sync
branch
from
August 21, 2026 12:46
2c08ba5 to
dd2f64e
Compare
Contributor
Author
|
Hi @remdex, Apologies for the previous branch state — some leftover static paths from an older dev commit accidentally slipped in earlier. I have completely cleaned up the branch and rebased it directly onto clean
Please take a look when you have a moment. Thanks! |
mysubcult
force-pushed
the
feature/telegram-topic-reply-sync
branch
9 times, most recently
from
August 22, 2026 10:09
0178ea3 to
eee54a8
Compare
mysubcult
force-pushed
the
feature/telegram-topic-reply-sync
branch
from
August 22, 2026 10:19
eee54a8 to
5ff450d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements native two-way message replies and quotes synchronization between Telegram forum topics (operator side) and visitor channels (Telegram visitor bot / Web widget / Incoming webhooks).
Clean changes included:
classes/Commands/GenericmessageCommand.php:$message->getReplyToMessage()).tg_topic_msg_idinmeta_msg.[quote=ID]BBCode to the message and populatesmeta_msg_array['content']['quote']andmeta_msg_array['content']['reply_to'].message_idintotg_topic_msg_id.bootstrap/bootstrap.php:saveTopicMsgId($msg, $topicMsgId)to record topicmessage_idon send.getTopicReplyId($msg, $chatId)to resolve target topic message IDs fromcontent.reply_to.db_msg_id,content.reply_to.iwh_msg_id,content.quote.id, or[quote=ID].reply_to_message_idto Telegram Bot API when sending text messages, media files, and bot messages into the topic.Default configuration templates updated (
doc/telegram/):doc/telegram/incoming-webhook.json: Added"message_id_reply": "message.reply_to_message.message_id"so incoming replies from visitors in Telegram are mapped automatically.doc/telegram/rest-api.json: Added{reply_to},"reply_parameters":{"message_id":raw_{{iwh_msg_id}}}{/reply_to}tobody_rawandbody_raw_fileso operator topic replies are sent to the visitor with native Telegramreply_parameters.