Answers.Body: <p>You can include a property to your form called <code>$templatePath</code> and users can insert whatever they want in this path with a default value to your own template. </p>
  
  <p>When someone executed your <code>render()</code> function you check if the template file exists in the public template path, if so render it, it not render one of your plugin templates.</p>
  
  <p>If the validation fails, you want to include the validated data with errors to the url manager, so you can access it later. During your <code>render()</code> function you can check if there is data and if it matches your current form element, if so render the data in your url manager instead of the element to display errors. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-26T11:47:56.003Z
Answers.Text: Thank you for your answer but I don't understand how this would work. What do you mean with "include a property to your form"?
Answers.UserDisplayName: dazz
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-26T11:49:30.550Z
Answers.Text: Just add an additional class property http://php.net/manual/en/language.oop5.properties.php to your `Form` model that clients may set/change
Answers.UserDisplayName: Robin Schambach
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-26T12:29:24.283Z
Answers.Text: Ok, and then, how would the 'user' use this in their twig template? The idea is to include the contact form template in their own template, how would the render() function be called from twig?
Answers.UserDisplayName: dazz
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-26T18:33:40.097Z
Answers.Text: You would do something like `{{ form.render() }}` the form can be fechted via `ElementQuery` or via `BaseRelationField` like every other relation in Craft. Most Form plugins handle it that way or something similar
Answers.UserDisplayName: Robin Schambach
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-07-25T16:36:07.127Z
Answers.LastActivityDate: 2018-07-25T16:36:07.127Z
Answers.UserDisplayName: Robin Schambach
Body: <p>I'm building a simple contact form plugin and I would like to be able to provide a default form that the developer can include in his own template.</p>
  
  <p>Most plugins I've seen provide the controller and all the code to process a submitted form but you still have to create your own form.</p>
  
  <p>At the moment I tried 2 methods, using a hook and a template variable.
  While both work I was wondering if there wasn't a better/cleaner method.</p>
  
  <p>The downside of using a hook is that you can't pass variables to the template (or am I wrong?) and the template variable feels like a misuse of the functionality.</p>
  
  <p>Isn't there a way to use the existing twig import function? Maybe by registering a namespace twig path in the plugin?(<a href="https://symfony.com/doc/current/templating/namespaced_paths.html" rel="nofollow noreferrer">https://symfony.com/doc/current/templating/namespaced_paths.html</a>)</p>
  
Tags: <plugin-development><templating><craft3>
Title: Using a template from a plugin
ThreadText: # Using a template from a plugin
  
  (Asked by: username_0 on 2018-07-25)
  
  I'm building a simple contact form plugin and I would like to be able to provide a default form that the developer can include in his own template.
  
  Most plugins I've seen provide the controller and all the code to process a submitted form but you still have to create your own form.
  
  At the moment I tried 2 methods, using a hook and a template variable.
  While both work I was wondering if there wasn't a better/cleaner method.
  
  The downside of using a hook is that you can't pass variables to the template (or am I wrong?) and the template variable feels like a misuse of the functionality.
  
  Isn't there a way to use the existing twig import function? Maybe by registering a namespace twig path in the plugin?(<https://symfony.com/doc/current/templating/namespaced_paths.html>)
  
  **Tags:** plugin-development, templating, craft3
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-07-25. Score: 1
  
  You can include a property to your form called `$templatePath` and users can insert whatever they want in this path with a default value to your own template.
  
  When someone executed your `render()` function you check if the template file exists in the public template path, if so render it, it not render one of your plugin templates.
  
  If the validation fails, you want to include the validated data with errors to the url manager, so you can access it later. During your `render()` function you can check if there is data and if it matches your current form element, if so render the data in your url manager instead of the element to display errors.
  
  > **Comments:**
  > **username_0**: Thank you for your answer but I don't understand how this would work. What do you mean with "include a property to your form"?  
  > **username_1**: Just add an additional class property http://php.net/manual/en/language.oop5.properties.php to your `Form` model that clients may set/change  
  > **username_0**: Ok, and then, how would the 'user' use this in their twig template? The idea is to include the contact form template in their own template, how would the render() function be called from twig?  
  > **username_1**: You would do something like `{{ form.render() }}` the form can be fechted via `ElementQuery` or via `BaseRelationField` like every other relation in Craft. Most Form plugins handle it that way or something similar  
  
  ---
  
  