Apr 25, 20239:57 AM - bearbeitet Apr 25, 202310:00 AM
Teilnehmer/-in
'text' fields are not supported in theme fields.json
lösung
I was receiving the same error. When I fetched the module for the destination location I wrote the module folder name as "mycustommodule-module" instead of "mycustommodule.module"
My answer is not something new from the accepted answer, but rather written a bit differently.
'text' fields are not supported in theme fields.json
lösung
@andireuter Post an MVP / reproducable version. I.E. - a sample theme giving you this and commands + module directory. Your structure is wrong somehow somewhere.
'text' fields are not supported in theme fields.json
lösung
Maybe I didn't wrote that my sample above is from my module, not the theme fields.json. But the cli prints this weird error message. This confuses me. In modules the "text" type is a valid field. But the cli treats my module fields.json as the theme fields.json. Any idea?
'text' fields are not supported in theme fields.json
lösung
This should be a module not a theme setting....
And usages like this give good reason to the product team to not add text fields.
Which is understandable, when used wildly improperly this way, but it's a shame such proliferative misuse by novice methodologies causes significant detriment within themes as text fields do have valid use cases for advanced scenarios and settings that do in fact require text fields to properly manage.