Hi,
I’m trying to enter permalinks (which works fine) but bump into an issue when entering url’s with special characters.
For instance when entering the url
display/exacom/ADO+<>+Jira+Cloud%3A+Date+time+sync
it is converted to
display/exacom/ADO+%3C%3E+Jira+Cloud%253A+Date+time+sync
Because &25 is the html counterpart of %
But then when I try the link
https://community.exalate.com/display/exacom/ADO<>+Jira+Cloud%3A+Date+time+sync
The page is not found.
Trying to use the html entity counterpart in the url entry, is not working either, because the original url is then not found.
Question - what is the correct way to enter permalinks which contains this type of characters (and avoid double HTML encoding)
Jagster
(Jakke Lehtonen)
November 16, 2024, 9:52am
2
Just a wild guess: escaping, like \%3A
?
pfaffman
(Jay Pfaffman)
November 16, 2024, 12:44pm
4
You could try entering them in rails to have more control over the escaping, maybe. Don’t know if it’ll help, but that’s what I’d try next.
We are using the hosting option of discourse.org
I don’t think we can have that liberty.
1 Like
Lilly
November 16, 2024, 1:31pm
6
those display links don’t look right - they are missing the first part it looks like.
have you tried TinyURL link shortening?
Hi Lily,
Thanks
These are wiki pages which we published on our old community site
For instance
https://community.exalate.com/display/exacom/ADO<>+Jira+Cloud%3A+Date+time+sync
Is now accessible on
https://oldcommunity.exalate.com/display/exacom/ADO<>+Jira+Cloud%3A+Date+time+sync
Of course - people who try to access today the first version, will arrive at the discourse site, and get a 404. That’s why we want to use the permalinks feature
The problem is that it is not possible to enter the url in such a way that it is found and thus the redirect doesn’t kick in.
A tinyurl will not be possible because that is not what the users will be using.
2 Likes
pfaffman
(Jay Pfaffman)
November 16, 2024, 2:45pm
8
How many are there and do they all have the same nonsense at the head?
Do they all have xxx%3A+slug?
1 Like
Lilly
November 16, 2024, 2:59pm
9
I’m obviously not understanding what you are doing. I just successfully created a test permalink on my site to this page:
https://oldcommunity.exalate.com/display/exacom/ADO+<>+Jira+Cloud%3A+Date+time+sync
when I go to /test
on my site it takes me straight to that page.
edit: nevermind, I wasn’t comprehending your OP properly, I see what you are trying to do now. you are tying to use that weird complex link as the permalink. yikes. yea I don’t know if that is possible without some special escaping.
Exactly - thanks for taking the time.
1 Like
Do they all have xxx%3A+slug?
no
We created now a page with an overview of all the use cases
There you can see some of the links and how these are url encoded.
1 Like
pfaffman
(Jay Pfaffman)
November 16, 2024, 6:23pm
12
Hmm. It would have been easier to migrate those before you made your community live.
Most of those are fine,I think.
You might be able to make a permalink normalization that removed everything before the >
and then make the permalink for just the part after that.
1 Like
The source url is being used in multiple locations and not necessarily under our control.
Being able to enter the source url would resolve the issue.
Lily is currently looking for a solution…
Thanks
pfaffman
(Jay Pfaffman)
November 16, 2024, 7:26pm
14
Lily:
From a quick look most urls should work fine.
I think the rest have a greater than and everything after the greater than is plain characters. So you can make the permalink strip out the first part up to the greater than and it’ll Just Work.
1 Like
Hi Jay,
The urls on that page have all been url encoded before adding, because the composer is also encoding it - which is to be expected.
They are not the original URL’s.
Would it work if I provide a text file with the original ones?
Francis