Send Telegram chat files by URL - #76
Open
mysubcult wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
This keeps the Telegram chat file forwarding path aligned with the existing LiveHelperChat REST API file handling.\n\nCurrent code re-uploads the local storage file with Request::encodeFile(->file_path_server), so Telegram receives the internal stored filename instead of using the file download response.\n\nThis change:\n- reuses the existing uploaded $file object;\n- builds the same temporary ile/downloadfile URL pattern used by core REST API {{file_url}};\n- keeps the existing Telegram API method selection and caption handling;\n- avoids reading file contents, temp copies, hardlinks, custom Guzzle multipart, or filename sanitizing logic in the extension.\n\nThis should let Telegram fetch the file through LHC and use the existing download response headers/file metadata instead of the internal hashed storage path.