DevTools New theme fails with no error

Support
1

Hi, I’m creating a new theme following the instructions at Theme Tutorial | Grav Documentation

The script takes me through the settings for theme name, description etc.

When it gets to where you choose which type of theme to create (pure-blank, tailwind etc), the script just stops and takes me back to the command prompt. I’m not even able to choose an option.

Anyone seen this before?

Thanks,
Mark

2

@berthelemy, I cannot reproduce the issue using the following script using Grav 1.7.49.5 and PHP 8.3.6:

$ bin/plugin devtools newtheme

 Enter Theme Name:
 > aa

 Enter Theme Description:
 > aa

 Enter Developer Name:
 > aa

 Enter GitHub ID (can be blank):
 >

 Enter Developer Email:
 > aa@aa.com

 Please choose an option:
  [pure-blank  ] Basic Theme using Pure.css
  [tailwind    ] Basic Theme using tailwind.css and including Alpine.js
  [tailwind-mix] Same as `tailwind` but more opinionated with Laravel Mix compiler
  [inheritance ] Inherit from another theme
  [copy        ] Copy another theme
 > pure-blank


SUCCESS theme aa -> Created Successfully

Path: /www/grav/site-dev/user/themes/aa

Newly create theme “aa” is also working fine.

Are you using the correct PHP version for Grav 1.7 or 1.8?

3

@pamtbaau - your reply contains stdout i’ve never seen before. upon review, i see it’s a snapshot of results from

bin/gpm install devtools

a feature i’ve discovered only presently. good to know!
:slight_smile:

users should explore the ./bin/gpm and ./bin/grav commands . have you a standard reference for what’s available? (EDIT: rather, have you a recommended “onboarding” type of plugin-toolchain, where a “new” user might best learn of things related to devtools for example?)

4

@ajaxstardust, Did you already discover the documentation on cli-console ? :wink:

Try for example:

$ bin/gpm list
$ bin/grav list
$ bin/plugin

And off course, to explore what plugins might provide as cli-commands, read the README on the repo of plugins listed by $ bin/plugin.

5

Thanks @pamtbaau , I think my problem was due to the browser based terminal provided by my hosting company. I’ll move over to SSH and hopefully that will resolve things.