# Get information back from end user?

**URL:** <https://forum.shopware.com/t/get-information-back-from-end-user/49479>\
**Category:** International (English Only)\
**Tags:** programming\
**Created:** [15. November 2017 um 13:43 UTC](https://forum.shopware.com/t/get-information-back-from-end-user/49479 "2017-11-15T13:43:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kegg](https://avatars.discourse-cdn.com/v4/letter/k/9e8a1a/32.png) [@Kegg](https://forum.shopware.com/u/Kegg)\
**Post date:** [15. November 2017 um 13:43 UTC](https://forum.shopware.com/t/get-information-back-from-end-user/49479/1 "2017-11-15T13:43:57Z")

</div>

Hi,

&nbsp;

How do I get information back from the user on button press when button is created using tpl, how do I add events to style tpl objects?

&nbsp;

I want to basically have a text box on a page, where when the user clicks the button, the text inside gets saved to the database in a custom attribute column.

&nbsp;

Any help is appreciated 🙂

&nbsp;

-Ian

---

<div class="post-metadata">

**Author:** ![PStadtfeld](https://avatars.discourse-cdn.com/v4/letter/p/3bc359/32.png) [@PStadtfeld](https://forum.shopware.com/u/PStadtfeld)\
**Post date:** [20. November 2017 um 14:17 UTC](https://forum.shopware.com/t/get-information-back-from-end-user/49479/2 "2017-11-20T14:17:05Z")

</div>

Well you’d probably want to make it a plugin that registers on certain events.

For one - the call of the page you wish to add the textfield to 'n then to the event responsible for saving/further processing the data after button click.

Maybe you find something on here, it’s the Shopware guide to writing your own plugings: [https://developers.shopware.com/developers-guide/example-plugin/](https://developers.shopware.com/developers-guide/example-plugin/)

&nbsp;

Not sure what sort of text you expect to get from them but maybe you’d want to consider extending the database by your own table “customernumber/id, text” or something like that. In this case your data would not have to depend on the shopware architecture itself too much 'n is also safe from updates, etc.