Contact Form

Hi Sue,
Thank you for reporting this issue. I believe I might know the reason and have just published a new version of Contact Form for Moodle which should address your problem. However, you will need to make a few changes. The Name field must be called "name", Email field must be called "email". For consistency, the Subject field should be called "subject" and Message field called "message". The labels displayed in the email will still be taken from the language pack so these should display correct in German.
What I suspect might have been happening is that someone updated the German translation in AMOS for the email fields. This affects anyone who was using the German language pack. Anyway, stick with the English names for these 4 fields and it should work again. By field name, I am referring to the input name="email" part of your form.
Let me know if this resolves your problem. If it doesn't, please open an issue in the Bug Tracker (see link on the Contact Form plugin page) and I will be happy to work with you to resolve the issue.
Best regards,
Michael

Dear Michael Milette,
thank you for this plugin, it is very useful. We are kindly asking for your support/help with a recent error, though.
We have been using the local contact form plugin without any trouble for a while on our German client's moodle site.
Strangely, somewhere after the latest two moodle updates, the contact form stopped working.
The error message says: Forbidden. Unknown sender - invalid email address or the form field name is incorrect
We read your troubleshooting page on git hub. But sadly, the description of this error is not very helpful to us.
The e-mail is valid and we did not change the form field names. We double checked all plugin files comparing them to backups to see if anything changed- nothing.
Everything else on the moodle site concerning e-mails works fine, still, it is just local contact form which seems to have a problem. We installed email test and it records no errors. We tried Debugging, but could not locate the issue.
We use the standard php method in email settings of moodle. We briefly changed that on the moodle site to using smtp server settings to see if that helps and the email tests still work fine...but the contact form still produces the same error message Forbidden. Unknown sender - invalid email address or the form field name is incorrect
What changed or what are we doing wrong? If you or anybody else on here has any ideas what we could try or tips for us, we'd greatly appreciate it.
Thank you for your time.
Best regards,
Sue

Hi Georg, I am hoping to get the global autoresponder implemented in time for the upcoming release of Contact Form for Moodle in November/December 2017 however I am not sure that the "form specific" autoresponder will make it in on time. Keep an eye out on the the project's "dev" branch on GitHub to see the latest changes. If you want make sure you are personally notified when that feature does come out, add a "Feature Request" in the bug tracker. I will be sure to let you know when it becomes available. As always, if you want it sooner, I am available for hire
Best regards,
Michael

Hi Michael,
I would like to ask if there is any update on the road with support for form-specific custom autoresponders and the like? This would be really terrific!
Kind regrads,
George

Hi LeeJH,
I was not aware that it wasn't supporting UTF-8. I would like to work with you to better understand the issue to see if this can be resolved. For example, are you having trouble using Moodle string translation tool or that Contact Form can't send the email messages containing UTF8 text?
Could you please use the Bug Tracker link on the Contact Form plugin page to open a new issue?
Best regards,
Michael

Hello. I like this. But can't use in Korean language. (Local tranlate not possible)
Do you have a plan support UTF-8 type. (Korean language)
Sorry about my English

Hi Georg,
Thanks for the feedback. I understand your concern. I have some ideas on how to address this and will try to implement a solution in the next release. In the meantime, instead of editing the language file locally, consider editing the language strings using Moodle's language tool. This approach will ensure that future updates of the plugin and the language packs don't override your string customisations. The tool actually looks and works in a very similar way to AMOS. You'll find it in your Moodle site by going to Site administration > Language> Language customization.
Thanks again for the feedback. Hope this helps.

Hi Michael,
everything is fine with the subject field! The German translation in AMOS for the required and optional fields (name, email, subject, message) has been changed, so after submitting the form the respective parameters are missing! Hence a multilingual usage of this plugin is not possible, the AMOS translations should be unified for the form fields concerned or maybe there is another approach to provide individual label translations...
I edited the language file locally, no issues while using different languages anymore!
Anyway, this plugin rocks!

Hi Michael, thank you very much for this great plugin! I love it and it works like a charm!
There is only one thing not working at least for me: the subject field. If I include an input field with name "subject" the subject of the received email still remains the default one from the language file (New message)! Is there anything I am doing wrong?
Moodle 3.3.1, PHP 7.1
Kind regards,
George

Hi again Zoran, you may need to modify the URL in the ACTION parameter of the FORM tag so that it reflects the location of local/contact/index.php plugin. In the future, we will be able to work around this through the use of a new upcoming filter_filtercodes plugin.

Hi Zoran, thank you very much for your question. Normally if there is anything wrong with your webform, you should see a message that says "Forbidden", not get a blank screen. What to do in the case of a "Forbidden" message is covered in the documentation for the plugin. Basically, set Moodle into Developer Debug mode and then try your form again. You should then see one or more messages appear that will tell you what's wrong with your webform.
To turn on Developer Debug mode, login to your Moodle site as an Administrator and click Home > Site Administration > Development > Debugging -- be sure to check the box next to "Display debug messages" if you want to see the errors on your screen. Otherwise they just end up in your log file.
IMPORTANT : Don't forget to turn debug off after you are done.
Hope this helps. If not, post a follow-up message in the Bug Tracker or Discussion forum (links on the plugin's page) and I will see what can be done to help you out.
Best regards,
Michael

Hi Michael,
I have problem with this plugin. Installation and setup is OK, but when I click on Send button, my browser open blank white page without any content?
Thank you

Hi Juliane, thank you for your question.
Take a look at the sample HTML source code of a form included with the documentation or on the plugin's wiki. You'll notice that there is a hidden field for the sesskey and some JavaScript. Both of these must be included in your form in order for it to work.
Hope this helps. If not, post a follow-up message in the Bug Tracker or Discussion forum (links on the plugin page) and I will see what can be done to help you out.

Hi Michael,
I installed your plugin. Now I am trying to insert a form into a block. When I insert the sample code and try to safe I get an error message. It says something like: "Wrongs sesskey, form not accepted." What am i doing worng? Do I have to insert a sesskey?

Hi Gloria, thank you for your question. I am glad you asked. It's no bother at all. Unfortunately recaptcha is not yet fully implemented. Half of the solution involves using a new plugin I recently created called FilterCodes. It is currently only available on GitHub at https://github.com/michael-milette/moodle-filter_filtercodes however, after a little more testing, I am hoping to have it published on Moodle.org in the near future. Amongst the many things it can do, it will insert the necessary recaptcha HTML code into your form. The other half involves making the Contact Form plugin handle the submitted recaptcha to ensure it is processed correctly. I am not sure when I will have the second part done but I will try to remember to let you know. If you want to ensure that I notify you, open an issue on the Source Code URL site and add a suggestion in the Issues suggesting that Contact Form include support for recaptcha.