# 'text' fields are not supported in theme fields.json

**URL:** <https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217>\
**Category:** CMS Development\
**Created:** [October 12, 2021, 2:37pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217 "2021-10-12T14:37:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![andireuter](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/andireuter/32/53869_2.png) [@andireuter](https://community.hubspot.com/u/andireuter)\
**Post date:** [October 12, 2021, 2:37pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/1 "2021-10-12T14:37:19Z")

</div>

I get this weird issue in only 1 module of multiple modules I build. I just added the fields.json and the “hs watch” starts complaining about

`'text' fields are not supported in theme fields.json`

If I remove the “image\_box\_heading” and “image\_box\_text” everything works fine again. I use the same “text” fields in my other modules.

My module fields.json:

```lia-code-sample
[
 {
 "name": "image_box_heading",
 "label": "Image box heading",
 "locked": false,
 "type": "text",
 "required": true,
 "default": "Your Hero"
 },
 {
 "name": "image_box_text",
 "label": "Image box text",
 "locked": false,
 "type": "text",
 "required": true,
 "default": "Nam porttitor blandit accumsan. Ut vel dictum sem, a pretium dui. In malesuada enim in dolor euismod, id commodo mi consectetur. Curabitur at vestibulum nisi..."
 },
 {
 "name": "image_box_image",
 "label": "Image box image",
 "locked": false,
 "type": "image",
 "required": true,
 "responsive": true,
 "resizable": false,
 "show_loading": false,
 "default": {
 "size_type": "auto",
 "src": "{{ get_asset_url('/nuaware/website/img/spacer-img.jpg') }}",
 "alt": null,
 "loading": "disabled"
 }
 },
 {
 "name": "toggle_box",
 "label": "Show image on the left",
 "locked": false,
 "type": "boolean",
 "display": "toggle",
 "required": true,
 "default": false
 }
]

```

Who knows about this issue?

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 12, 2021, 6:55pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/2 "2021-10-12T18:55:01Z")

</div>

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.

This is not one of those cases.

---

<div class="post-metadata">

**Author:** ![andireuter](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/andireuter/32/53869_2.png) [@andireuter](https://community.hubspot.com/u/andireuter)\
**Post date:** [October 12, 2021, 7:19pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/3 "2021-10-12T19:19:36Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 12, 2021, 7:39pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/4 "2021-10-12T19:39:20Z")

</div>

@andireuter Post an MVP / reproducable version. I.E. - a sample theme giving you this and commands + module directory. Your structure is wrong somehow somewhere.

---

<div class="post-metadata">

**Author:** ![andireuter](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/andireuter/32/53869_2.png) [@andireuter](https://community.hubspot.com/u/andireuter)\
**Post date:** [October 12, 2021, 7:52pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/5 "2021-10-12T19:52:19Z")

</div>

Yes, I forgot to add suffix “.module” at the name of the module folder. 🙄

Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 12, 2021, 8:06pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/6 "2021-10-12T20:06:30Z")

</div>

You’re aware there’s a create module command right…? It does the folder etc for you.

If you’re using watch and trying to create it manually due to this… Just use two terminals lol

One for subprocesses the other for one offs per all development workflows ever.

---

<div class="post-metadata">

**Author:** ![LFilip](https://avatars.discourse-cdn.com/v4/letter/l/c89c15/32.png) [@LFilip](https://community.hubspot.com/u/LFilip)\
**Post date:** [April 25, 2023, 1:57pm UTC](https://community.hubspot.com/t/text-fields-are-not-supported-in-theme-fields-json/45217/7 "2023-04-25T13:57:34Z")

</div>

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.