Basics

In the Hello World example you have seen, that it is very easy to create a kitCommand.

There are some basics, you should know if you are working with kitCommands.

If you are placing a kitCommand within a WYSIWYG section of your Content Management System:

~~ MyExtension ~~

You should know that a kitCommand is case insensitive. You can also write:

~~ mYeXTEnsIOn ~~

Before processing, the kitFramework will lowercase the kitCommand.

The route for the kitCommand must be always in lowercase:

$app->post('/command/myextension', function ()

If you try to execute a not existing kitCommand, for example:

~~ MyExtensions ~~

the kitFramework will return:

_~~ Error: Can't execute the kitCommand: myextensions ~~_

For the visitors of your website this is enough information. As a developer you want to get a more detailed response.

Add the parameter debug[] to the kitCommand:

~~ MyExtensions debug[] ~~

The kitFramework will now respond with:

If you are using the debug[] parameter, the kitFramework will always try to return a qualified error message.

Next step: Out of the Content Management System