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

TeamSpeak3_Viewer_Html: str_pad(): Padding string cannot be empty #136

Closed
Sebbo94BY opened this issue Jan 5, 2020 · 2 comments
Closed
Assignees
Labels
bug Confirmed as a valid bug and requires fix.

Comments

@Sebbo94BY
Copy link
Collaborator

I have the problem, that one of my TeamSpeak 3 servers can't be displayed using the standard TS3 Viewer feature of this library.

I've double-checked the used URI and it's correct. The virtualserver ID is correct, exists and matches the respective TS3 server.

When I change the virtualserver id statically to any other existing virtualserver, the TS3 viewer is working as expected.

This is the stacktrace:

image

I'm confused why the result of the factory is always empty, because TeamSpeak does not log any errors - only the information, that the query successfully connected to this specific virtualserver id.

This is the result of the factory URI "serverquery://serveradmin:<password>@<serverquery_ip>:10022/?ssh=1&use_offline_as_virtual&server_id=850#no_query_clients":

$uri = "serverquery://serveradmin:<password>@<serverquery_ip>:10022/?ssh=1&use_offline_as_virtual&server_id=850#no_query_clients";

$TS3PHPFramework = new TeamSpeak3();

try {
    $ts3virtualserver = $TS3PHPFramework ->factory("$uri");
} catch (TeamSpeak3_Exception $ex) {
    return false;
}

return $ts3virtualserver;

image

What's the issue here and how can I fix this?

@Sebbo94BY
Copy link
Collaborator Author

@ronindesign @svenpaulsen any idea? This issue causes, that the TS3 Viewer does not load and thus the entire page can not be displayed.

Is there any way to try-catch errors in order to show something like "could not render TS3 Viewer" in case of any issues?

svenpaulsen added a commit that referenced this issue Feb 15, 2020
@svenpaulsen
Copy link
Contributor

I guess this happens when people create repeating spacers without a display name to make use of the TS5 channel banners. Please re-test with the current master.

@svenpaulsen svenpaulsen self-assigned this Feb 15, 2020
@svenpaulsen svenpaulsen added the bug Confirmed as a valid bug and requires fix. label Feb 15, 2020
ronindesign pushed a commit that referenced this issue May 18, 2020
* Icon Download extended function (#131)

* Update Server.php

Option to Download an icon by name.
This has the benefit that you don't have to change the virtualserver_icon_id to download a specific icon.

* Update Server.php

fixed name was not set for download

* Fixing naming error (#135)

* try to fix issue #136

* add -banners option to channellist

* remove iconname argument

use transferInitDownload() instead

* add -keepfiles argument to snapshot deploy

* update changelog

* set release date for 1.1.34

* Fixing deprecated curly braces for PHP 7.4+ (#142)

* removed deprecated curly braces from string.php, host.php, crypt.php, char.php

* removed another deprecated curly braces from string.php (#144)

overlooked one more curly braces

* * Added Travis CI build status icon to README
* Travis CI tests now also PHP 7.3 and 7.4
* Improved composer.json
* Updated command to run all tests in README
* Added `docker-compose up` to README for existing docker container(s)
* Fixed PHPUnit config issues

* Exposed ServerQuery SSH port

* Switched from libssh to phpseclib

* Changed requirement from PHP extension SSH to phpseclib

* Fixed composer warning

* #148: Fixed deprecated curly braces in PHP 7.4

* Updated composer packages

Co-authored-by: Sensznet <ssensz@gmx.de>
Co-authored-by: Thomas Hanke <18329992+thhan@users.noreply.github.com>
Co-authored-by: Sven Paulsen <info@sven-paulsen.de>
Co-authored-by: Fjonan <fjonan@fjonan.com>
Co-authored-by: Sebastian Krätzig <sebastian.kraetzig@4g-server.eu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed as a valid bug and requires fix.
Projects
None yet
Development

No branches or pull requests

2 participants