october:util error

[ctf0]

Actual behavior

Utility command "" does not exist!

October build

i believe its v1.0.398

[LukeTowers]

What command were you trying to run? It looks like you were trying to run october:util by itself which doesn't exist. Read https://octobercms.com/docs/console/commands#utility-commands for more information on the october:util sub commands.

[ctf0]

okay got it, but maybe the console should give a diff/better error msg, maybe like when using october:util without any options it would run october:util -h internally ?

however the main reason i ran it was hopping to find a cmnd where i can list all the routes and its corresponding controllers.

also regarding

i believe its v1.0.398

i couldn't find any cmnd to display the version for october ex.php artisan will show laravel version at the top, maybe we can have a one like this for october ?

[LukeTowers]

Feel free to implement the defaulting to -h internally in a PR.

In regards to the routes and the corresponding controllers, I don't believe there is such a command (@daftspunk correct me if I'm wrong). If you've got a more specific question about that I can probably answer it though.

In regards to the build number, it's displayed in the backend updates section. Again, feel free to implement a command for it in a PR.

[ctf0]

awesome, many thanx for the quick help.

btw for the version, i cant find in the backend, i've also tried http://octobercms.com/plugin/indikator-backend which have a widget to show the cms version but again nothing, if u can point me to where the class responsible for displaying the info, i can add a pr with the new cmnd.

[LukeTowers]

That's a better question for @daftspunk, sorry. Could try to find it right now but it's late and I need to get some sleep

[ctf0]

okay sure, thanx again for ur help 👍

ref ideas

[daftspunk]

I don't believe such a command exists, routes are not defined in the back-end per say, the controller is discovered based on the URL pattern. I suppose you could create a command that lists all the controllers (in the /controllers directory of each plugin and module) and then derive the URL and actions from that.

[ctf0]

@daftspunk maybe you can add an event for when

the controller is discovered based on the URL pattern.

and we can listen to it from the console cmnd and list/parse all the fetched data routes in a table ?