Moodle plugins directory: Contact Form | Moodle.org
Contact Form
Michael MiletteThe Contact Form plugin for Moodle processes information submitted through a custom web form, sending it by email to the site's support email address, if defined, or to the primary system administrator.
Examples uses for this plugin include:
- Contact us form.
- Support request form.
- Request a course form.
- Information request form.
- Lead generation form.
- Membership application form.
Share with us how you use this plugin on your site.
Note: This is not a web form builder but a form processor. You must have some knowledge of how to create HTML forms or at the very least be able to cut and paste the example included in the README file.
Contact Form templates
If you are not familiar with HTML, consider using the following easy to use plain text {form...} tags included with the FilterCodes plugin. These will generate a Contact Form templates and therefore require that you have the FilterCodes plugin installed and activated.
- {formquickquestion} : Adds a "quick question" form to your course. Form includes Subject and Message fields. Note: User must be logged in or the form will not be displayed.
- {formcontactus} : Adds a "Contact Us" form to your site (example: in a page). Form includes Name, Email address, Subject and Message fields.
- {formcourserequest} : Adds a "Course Request" form to your site (example: in a page). Unlike Moodle's request-a-course feature where you can request to create your own course, this tag allows users to request that a course they are interested in be created. Could also be used to request to take a course. Form includes Name, Email address, Course name, Course Description.
- {formsupport} : Adds a "Support Request" form to your site (example: in a page). Form includes Name, Email address, pre-determined Subject, specific Subject, URL and Message fields.
- {formcheckin} : Adds a "I'm here!" button to your to your course. Form does not include any other fields. Note: User must be logged in or the button will not be displayed.
The initial work for this project was sponsored by the kind folk at l'Action ontarienne contre la violence aux femmes. Contact Form benefits from ongoing development by TNG Consulting Inc..
Useful links
Screenshots
Contributors
Sorry if I posted in the wrong place, I just thought that since other questions had been asked here and it was directly related to this pluging that this was the best place to post any problems, again sorry for that.
I understand that the html code defacto is in the yyyy-mm-dd format but as in the link you posted the output is in uk format as 22/07/2018. On our website on the form it shows dd/mm/yyyy and thought it is something that might have been able to change within the plugin for the displayed output but if that is not the case I understand and will have to live with that.
On the message, I did have a look at the customisation prior to posting but didn't come across it so must have been using the wrong search strings or in the wrong place I guess and will have another look into that one.
Having said all that I appreciate the help you have given, many thanks for that.
Regards
Steve
Yes found the info most useful and helpful, after revisiting the language customisation again managed to find the string and changed the wording as required.
We will have to live with the yyyy/mm/dd date format as the form works very well for our needs and hope the users remember to book the dates correctly when the email comes through the system.
Again Many Thanks for the help.
Regards
Steve
If you or anyone else would like to be notified about updates on this issue, please leave a comment on the following ticket:
https://github.com/michael-milette/moodle-local_contact/issues/62
Best regards,
Michael
Is there any way to make the CONTINUE button redirect back to the course page instead of going to the front page? Thanks!
Thanks for letting me know about the discussion forum. I will look into that.
The {formcheckin} tag is a pre-configured form provided for ease of use. You can definitely create your own and have a few options:
1) You can just add the HTML for the form to any page, label, block and other places. Examples are available in the Wiki:
https://github.com/michael-milette/moodle-local_contact/wiki/HTML-Form-Templates
2) If you plan on reusing the form, you can edit one of the existing pre-configured tags. More information on that is available at:
https://github.com/michael-milette/moodle-filter_filtercodes/blob/master/README.md#customizing-or-translating-the-forms-generated-by-the-form-tags
3) You can create your own tag, in FilterCodes settings, containing the form. More information on that can be found at https://github.com/michael-milette/moodle-filter_filtercodes/blob/master/README.md#define-your-own-custom-global-tags
Hope you find this helpful!
Best regards,
Michael
We want however this functionnality to be reserved to Moodle admin. Is it possible ? I do not see any permission associated to form creation. This could be an interresting evolution that would make the plugin more configurable.
Kisses
Zabelle
Here's a simplification of what I'm trying to accomplish, which is obviously not proper syntax because that gets stripped form this post:
FORM 1
form id="Form1" action="{wwwroot}/local/contact/index.php" method="post"
fieldset
input
input
formsesskey
/fieldset
div
input type="submit" value="SUBMIT FORM 1"
/div
/form
END FORM 1
FORM 2
form id="Form1" action="{wwwroot}/local/contact/index.php" method="post"
fieldset
input
input
formsesskey
/fieldset
div
input type="submit" value="SUBMIT FORM 2"
/div
/form
END FORM 2
Thank you for your question. Contact Form is a webform form processor, not a form creator or editor. It has nothing to do with the creation of a form. It is not because of this plugin that you can create forms on your Moodle site. It just gives you the ability to process the content and send it as an email.
Creating a form is something you do in the HTML view of the Atto or TinyMCE editors.
You might be able to limit a person's ability to create forms if you remove the editor's icon to switch to HTML view.