Channel which should be private is subscribed
Closed this issue · 13 comments
I have one channel called private, which can't be subscribed by any servergroup. But the query does. How can I fix this?
To hide a channel from TS-website viewer you can either:
- add channel ID to the config under
viewer_hidden_channel_ids
- set channel permission
i_channel_needed_subscribe_power
to75
or higher
I can't find viewer_hidden_channel_ids in the configtable of the mysqldb
My bad, the change in not in any release. I would need to publish a release, or you can update your viewer.php file to the one in the repo and then add a new config row to the config table:
INSERT INTO `tsw_config` (`identifier`, `type`, `value`, `user_editable`) VALUES ('viewer_hidden_channel_ids', 'JSON', '[]', 1);
Then you can set viewer_hidden_channel_ids
to the IDs you want.
I will try it this afternoon. Thank you for your fast reply
I have added the channelid to the db and it is still displaying the channel on the webpage with all the clients which are inside (After 15 Minutes)
Are you sure you have updated the viewer.php
file?
I think so. I will try it again
It was exact the same content as mentioned previously, so everything should be correct
I think I know what the problem is
This is the constructor of the ViewerRenderer:
`public function __construct($imgPath) {
$this->imgPath = $imgPath;
$cm = CacheManager::i();
$this->serverInfo = $cm->getServerInfo();
$this->channelList = $cm->getChannelList();
$this->clientList = $cm->getClientList();
$this->serverGroupList = $cm->getServerGroupList();
$this->channelGroupList = $cm->getChannelGroupList();
}
`
And this constructor is getting called
$viewerRenderer = new ViewerRenderer("img/ts-icons", Config::get("viewer_hidden_channel_ids"));
I believe, that I also need to update the constructor so there is support for both parameters.
Am I right?
I have fixed it, by copying the ViewerRenderer.php from your repo and replacing my old one.
You are right, more files need to bed edited. I really should publish a new release.
Maybe. But you have done a great job with this project. Keep it up.
We can keep this issue closed, publishing a new release should be a separate issue.