Channel description url decode

[barricas]

So I have added automatically to new channels description a link that has a bookmark creation with the respective channels. The problem is when these channels (and parents) contain spaces.

Example:
Pathway "[cspacer0C]space test/test"

Encoded (so it doesn't break BB markup) becomes: %5Bcspacer0C%5Dspace+test%2Ftest

The encoded link by the ts3 client: ts3server://<-server address->?port=9987&channel=%5Bcspacer0C%5Dspace+test%2Fte st&addbookmark=Test

Decoded becomes: ts3server://<-server address->?port=9987&channel=[cspacer0C]space+test/test&addbookmark=Test

As you can see, the client is not converting the '+' back to space which causes the added bookmark to not work (enter in channel automatically).

It is not top priority but it is kinda annoying I had to replace the + with space with preg_replace.

[PotaBlava]

So I have added automatically to new channels description a link that has a bookmark creation with the respective channels. The problem is when these channels (and parents) contain spaces.

Example:
Pathway "[cspacer0C]space test/test"

Encoded (so it doesn't break BB markup) becomes: %5Bcspacer0C%5Dspace+test%2Ftest

Decoded becomes: ts3server://<-server address->?port=9987&channel=[cspacer0C]space+test/test&addbookmark=Test

As you can see, the client is not converting the '+' back to space which causes the added bookmark to not work (enter in channel automatically).

Have you try with %20 instead of + ?
Something like
%5Bcspacer0C%5Dspace%20test%2Ftest
?

[barricas]

No, I haven't tried because php's url_encode converts to +
But yes, it actually made more sense if it converted to %20

[dante696]

Where ist that + comming from? I can not reproduce this in our software.

I don't see a problem with the client, because "%20" for a space is used in our invite urls and the client alos expects "%20" for a space on connect.

[barricas]

Where ist that + comming from? I can not reproduce this in our software.

I don't see a problem with the client, because "%20" for a space is used in our invite urls and the client alos expects "%20" for a space on connect.

From php's urlencode. (which I then place in channel description with ts3 php framework).

BTW I think you can close this thread, %20 is a better way to encode spaces.

[barricas]

I would like to update that, due to the amazing php's logic they have a similar function that follows the RFC rules.

And.... it is rawurlencode(). Yeah that's it. This one encodes correctly.

So if anyone would also want to do this. use rawurlencode().