[Release] devMX TeamSpeak3 ChannelWatcher - Auto delete unvisited Channels

[drak3]

The devmx TeamSpeak3 ChannelWatcher is a tool that allows to monitor a TeamSpeak3-Server and automaticaly delete unused channels.


Development of this tool has been discontinued. There will be no support by the developers anymore.

Current Version:
1.0.1

Features:

• Automated deletion of unused channels
• Usable with nearly all SQL-Databases (Sqlite, MySQL, PostgreSQL, MSSql,...) (But independent from TeamSpeak3-Server DB)
• Fine grained configuration.
• Specify rules like "do not delete Spacers", or "do not delete channels with visited children"
• Detailed documentation

The documentation of the TeamSpeak3 ChannelWatcher can be found here: http://docs.devmx.de/teamspeak3-channel-watcher/
For a quick introduction read Getting started.
If you are encountering any errors visit Troubleshooting

Prerequisites:

• Php version >= 5.3.3
• Current TeamSpeak3-Server (Tested with 3.0.5, older should work too)

Latest Changelog:

! Major Change
+ Add
- Removal
~ Minor Change
* Fix

v1.0.0
* removed build script from build (thanks to Ar2rJke from forum.teamspeak.com for reporting)

v1.0.0-beta.2
* Issue #35: Missing comma in example.php
* db:migrate command was run twice when running the init command. This caused problems with SQLite databases

Full changelog is available here.


Download:
http://devmx.de/en/software/teamspeak3-channel-watcher
Download on Addons-Page is also available.

Planned features: Attention: Development discontinued

• Configure and watch multiple server at once
• Automated database cleanup (removing entries of deleted channels)
• Logging and reporting facilites:
• Regular report (email) about deleted channels
• "Undo" function in case of accidentaly deleted channels

Features we thought of but are currently not planned:

• Translation of the ChannelWatcher
• Support for more config-file formats (xml, json, yaml...)

Please give us feedback if you want to see one of these features implemented, or if you have a need for a new feature we didn't thought of yet.
We really appreciate any contribution: report bugs, fork us on github and help developing and documenting this tool!

[Ar2rJke]

nice nice nice nice!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! THANKS!!!!!!!!!!!!!

[Maxe___]

We just released Beta 2 of the ChannelWatcher. Those are the changes:

v1.0.0-beta.2
* Issue #35: Missing comma in example.php
* db:migrate command was run twice when running the init command. This caused problems with SQLite databases

For the download link see the first thread.
Please report any bugs.

[Ar2rJke]

until 2 questions:

1. the role played by a file called "make-package.sh" (beta2)
2. how the updated version? which files should be changed that would upgrade to the latest.

[drak3]

1. the role played by a file called "make-package.sh" (beta2)

This is a file we use internally for packaging and will be removed in the next beta

how the updated version? which files should be changed that would upgrade to the latest.

When updating you could simply make a copy of your config-files and then overwrite all the files with the new package.
When especially updating from beta.1 to beta.2 only the file src/devmx/ChannelWatcher/Command/InitCommand.php changed notably so replacing this would be enough.

[TeamSpeak3]

Very interesting!

Can I select some channels to not be monitored, not just spacers, to never delete.
Like a fixed channel, nobody enter there, is a info channel...

Congratulations on your iniciative.

[drak3]

Can I select some channels to not be monitored, not just spacers, to never delete.

Yes, this is possible, you have to enter its id in the $c['watcher']['rule.acl_filter.blacklist'] array (line 62 in the example.php)
So it looks like this:

$c['watcher']['rule.acl_filter.blacklist'] = array(<channel_id_1>, <channel_id_2>);

The easiest way to get the channel ids is with this plugin. (You will see the channelid in brackets when you select the channel).

You then have to enable the $c['watcher']['rule.acl_filter'], rule by simply uncommenting it (remove the // in line 73)

Hope that helps,

drak3

[drak3]

1.0.0 just got released

As there were no major bugs reported, we decided to skip the rc phase and released 1.0.0-beta.2 as final 1.0.0 version.
There are no real changes, so if you are using beta.2 already there is no need to upgrade.
Download link is in the first post.

We also started the developement version 1.1.0, which will improve overall usability and stability and will hopefully provide a stable base for the following releases, for which we planned interesting new features. See the roadmap for details.

As usual, we are open to suggestions, and please report all bugs you find

[Ar2rJke]

You hit me, his genius

[Ar2rJke]

<? PHP

    $c['db']['connection.params'] = array(
    'driver' => 'pdo_sqlite',
    'path' => $c['storagedir'].$c['profile'].'_db.sqlite',
    );

>

Bring a ready example of how to specify the path to the base?

[SilentStorm]

Without knowing anything about this Script (so I wouldn't know if you used valid Array Indexes, or if the values you specified are valid options) your Snippet got a few Syntax Errors which I fixed below

<?php
    $c['db']['connection.params'] = array(
        'driver' => 'pdo_sqlite',
        'path' => $c['storagedir'].$c['profile'].'_db.sqlite'
    );
?>

[Ar2rJke]

is not the case, I copied a piece from the config, and I need an example of how to specify the path to the base sqlite

[Ar2rJke]

how to fix the problem?

[SilentStorm]

Configure your PHP Installation properly?

Alternatively you might be able to fix the Problem by modifying your above Configuration File to look like this:

<?php
    date_default_timezone_set("Europe/Moscow");
    $c['db']['connection.params'] = array(
        'driver' => 'pdo_sqlite',
        'path' => $c['storagedir'].$c['profile'].'_db.sqlite'
    );
?>

(ie. just add the first line right below the opening Tag.)
This **might** work or not, depending on when the original Author includes the configuration File and whether he uses Date Functions before that or not.

[Ar2rJke]

thank you) Now another error