Skip to content
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

IO - Fix non-ASCII characters breaking channel switching #1326

Merged
merged 4 commits into from
May 29, 2024

Conversation

jokoho48
Copy link
Contributor

When merged this pull request will:

  • Add Sanitization of serverName in sqf to prevent ts3ChannelMove to fail

@jonpas jonpas added the bug fix label May 29, 2024
@jonpas jonpas added this to the 2.13.0 milestone May 29, 2024
@jonpas
Copy link
Member

jonpas commented May 29, 2024

Does this fix #579?

@jokoho48
Copy link
Contributor Author

jokoho48 commented May 29, 2024

Does this fix #579?

Yes, it should fix that issue.

private _ts3ChannelDetails = format ["%1,%2,%3", EGVAR(sys_core,ts3ChannelName), EGVAR(sys_core,ts3ChannelPassword), serverName];
private _serverName = toString ((toArray serverName) select {_x < 127});
if (_serverName == "") then {
_serverName = "ServerName Fully Sanitized away";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a warning for RPT for that as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@jonpas jonpas changed the title IO - Fix ts3ChannelMove not working due to not sanatised ServerName IO - Fix non-ASCII characters breaking channel switching May 29, 2024
@jonpas jonpas merged commit 7469eef into IDI-Systems:master May 29, 2024
3 checks passed
@jokoho48 jokoho48 deleted the sanitize-servername branch May 29, 2024 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants