-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LinkedIn Posts—Text Cut Off (#273 Bug Persists) #395
Comments
From what I have read, the limit of the API is 1300 chars. |
Yes, however Postiz is cutting it off way before that. Here is an example. Here is what I schedule in Postiz: (1,207 characters)
Here is what was actually posted (350 characters)
|
@nevo-david in investigating more, I think the problem, 'actually' lies in the characters in the post not being properly handled/escaped. For example in this reference post, it gets cut of at the first ')', and going back to issue #273 it got cut off on the same character. |
@nevo-david any luck figuring this out? |
📜 Description
This is a follow-up to Issue #273, which was marked as closed. The issue of LinkedIn posts being cut off around 715 characters still persists, specifically when using the Docker Compose version of the app. Despite the initial resolution, users continue to encounter this problem, indicating that the underlying bug might not have been fully addressed.
👟 Reproduction steps
👍 Expected behavior
The complete post should be visible on LinkedIn, matching the content entered in the Postiz app (up to LinkedIn’s character limit of 3,000).
👎 Actual Behavior with Screenshots
When posting via the Docker Compose version, LinkedIn posts longer than 715 characters are truncated. The same behavior noted in the original issue (#273) is still occurring.
💻 Operating system
Linux
🤖 Node Version
Docker version
📃 Provide any additional context for the Bug.
The issue is observed in the Docker Compose deployment, as shorter posts are unaffected and publish correctly. The same truncation behavior is consistently observed with longer posts, suggesting that the original bug fix may not have fully resolved the issue or is not compatible with the Docker Compose setup. Unsure if the bug exists in other deployment methods.
👀 Have you spent some time to check if this bug has been raised before?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: