# Using text\_input with textcat.manual

**URL:** <https://support.prodi.gy/t/using-text-input-with-textcat-manual/4704>\
**Category:** Uncategorized\
**Tags:** usage, textcat, custom, front-end, solved\
**Created:** [September 21, 2021, 1:09am UTC](https://support.prodi.gy/t/using-text-input-with-textcat-manual/4704 "2021-09-21T01:09:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [March 6, 2022, 2:42pm UTC](https://support.prodi.gy/t/using-text-input-with-textcat-manual/4704/4 "2022-03-06T14:42:50Z")

</div>

See my comment here 🙂

> [@Add user input field to spans.manual recipe](https://support.prodi.gy/t/add-user-input-field-to-spans-manual-recipe/5423/2):
>
> In theory, yes! The only thing you'd need to adjust here is the view\_id, which should be blocks instead of spans\_manual (or any other interface). This is something you'd have to adjust in the recipe code at the moment. The quick and dirty solution would be to find the location of your installation via prodigy stats and then edit the built-in recipe. I'll think about a good way to make this configurable from the outside, e.g. via an environment variable, similar to the PRODIGY\_CONFIG\_OVERRIDES. …

---

_[View the full topic](https://support.prodi.gy/t/using-text-input-with-textcat-manual/4704)._