You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sharing a post to linkedin through an error
this due to post url special char has been decoded.
automatic generated from sharing button: https://www.linkedin.com/sharing/share-offsite/?url=soom3a.github.io%2FAboutMe%2FBlogs%2Fposts%2Fwindows_core_process
Correct sharing link should be : https://www.linkedin.com/sharing/share-offsite/?url=https://soom3a.github.io/Blogs/posts/windows_core_process
Steps To Reproduce
Activate linkedin sharing
Create a post
Try to share the post via linkedin button
Expected Behavior
Expected behavior should share via linkedin without manually update the url
This conversation has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
automatic generated from sharing button: https://www.linkedin.com/sharing/share-offsite/?url=soom3a.github.io%2FAboutMe%2FBlogs%2Fposts%2Fwindows_core_process
Your url is missing the protocol part, so I infer that your site.url is also missing the protocol. Please read the documentation on how to set the correct value for it.
Checklist
How did you create the site?
Generated from
chirpy-starter
Describe the bug
When sharing a post to linkedin through an error
this due to post url special char has been decoded.
automatic generated from sharing button:
https://www.linkedin.com/sharing/share-offsite/?url=soom3a.github.io%2FAboutMe%2FBlogs%2Fposts%2Fwindows_core_process
Correct sharing link should be :
https://www.linkedin.com/sharing/share-offsite/?url=https://soom3a.github.io/Blogs/posts/windows_core_process
Steps To Reproduce
Expected Behavior
Expected behavior should share via linkedin without manually update the url
Environment
ruby 3.2.3 (2024-01-18 revision 52bb2ac0a6) [x64-mingw-ucrt]
jekyll 4.3.3
Anything else?
No response
The text was updated successfully, but these errors were encountered: