Without more specific info, you should simply delete the tasks from the application developer center. This will delete from your database and update the tasks.json file, which will be reimported when someone upgrades your application.
The external dispatcher sets up a few things under the premise that you're executing code but not within the Suite itself (using the framework, but in a standalone script). This is safer than simply loading the session handler, which may rely on other classes).
Consider it a best practice tip.
Yes. If you include the init.php from the forum after that like this.
/* Require the init.php file from the Community Suite root directory */
/* Initiate the session to verify who this user is */
After you include the init.php you can use most of the forum function 😄
1. Pay attention on
$form->add(new \IPS\Helpers\Form\Text('ebacore_steamid', $admininfo["steamid"], FALSE, , NULL, NULL, NULL, 'ebacore_steamid'));
$form->add(new \IPS\Helpers\Form\Text('ebacore_jelszo', $admininfo["steamid"], FALSE, , NULL, NULL, NULL, 'ebacore_jelszo'));
The $values is array with keys ebacore_steamid and ebacore_jelszo
\IPS\Db::i()->update( 'ebacore_adminok_awp', array( 'steamid' => $values['steamid'] ), array( 'felhid=?', $member ) );
\IPS\Db::i()->update( 'ebacore_adminok_awp', array( 'jelszo' => $values['steamid'] ), array( 'felhid=?', $member ) );
You use $values['steamid'] but you don't have it. In this case you get an Undefined index: steamid.
BTW why do you use ['steamid'] for both inputs (ebacore_steamid and ebacore_jelszo)?
I'm afraid there's no way to just add a new option, however a custom plugin could do so. The brand would need to be supported by Fontawesome 4 (we do not use version 5 yet), but I confirmed that Steam is indeed supported in Fontawesome 4.7.0.