How do I fix borked Sharepoint links?
How Do I?
I’m running EE 5.1.3. My site users are saving big long links to Sharepoint files, and the links look like this:
“https://livepascok12fl.sharepoint.com/ : b : /r/sites/etc” and so on.
I added spaces in the above link, because removing the spaces causes the link to not be displayed properly in this post!
In MySQL, the link looks fine. While editing an entry in EE, the link looks fine. But what ends up getting published on the site is that the string containing : b : gets replaced with garbage and the link is broken. And apparently the same thing is happening in this field right here, in the forum.
Why? Any and all help greatly appreciated. It’s the only problem we’re having right now.
Richard MacLemale, District Website Coordinator, Pasco County Schools
Have you tried swapping the colon for %3A which is the URL encoded version?
Just tried it now, and replacing : with %3A does work to fix the issue manually. Thanks! The problem, of course, is that I can’t ask all 70 of our district level office secretaries to go into a huge, huge long Sharepoint link and edit the HTML. And they shouldn’t have to. EE5 is essentially breaking these links. Here’s another fun fact: the links get broken in entries. They don’t get broken if hard coded into a template. Which does me no real good, but it’s more info. I’m going to submit it as a bug. In the meantime, I can cron a mysql script to run a update/replace command on the appropriate fields every 10 minutes, which will “auto-heal” the links by using the %3A trick, so thanks again for that. It’s not a great solution, but it’s better than not having a workaround.
Richard MacLemale, District Website Coordinator, Pasco County Schools
Indeed, :b: to the Typography parser looks like an emoji short code, like :email: (✉️), so it gets output as 🅱️. Didn’t anticipate that text pattern in a link I suppose. GitHub Issues would be the best spot to post your findings so it’s properly tracked. Thanks Richard!
Thanks for the explanation! Bug submitted via GitHub. Would love to see this one patched soon, because we’re heavy Sharepoint users and my workarounds aren’t too appealing. Fingers crossed!
Just pushed a fix. 😉
AWESOME!!!!!