Umbraco Forms Validation Error Showing Incorrect Validation - umbraco

Umbraco Forms Installed working as expected 90% of the time, validating correctly.
There is an intermittent issue where the validation is firing incorrectly and preventing the form from submitting.
We have a simple contact form.
Name (*required text)
Email (*required email)
Phone
Message (*required text)
Recaptcha (*required)
When working the above validation all fires as expected. However the intermittent issue is that even when all fields are populated with correct data the Name, Email and Message are returning a validation error saying 'Please enter valid email address'. Even though the email address is valid and the Name & Message field is not being validated as an email.
The site is hosting on an Azure App Service.
Restarting the App Service in Azure resolves the issue and the form works correctly for a period of time before this happens again.
This is setup as per my other Umbraco sites which use Umbraco Forms and I do not experience this issue.
Anyone got any pointers on where I could look to debug/resolve this.

I've upgraded UmbracoForms to the latest version and this seems to have resolved the issue.

Related

LinkedIn: bug reporting

Hi guys #LinkedIn!
I have struggled with a bug using your oauth2 authentication.
Every time I was trying to "login with LinkedIn" to my site, only via mobile, I would get the authorization server encountered an unexpected condition.
Bummer.
It took me quite a while to figure out the problem. Apparently my mobile keyboard adds an extra "space" character after my email address. email#email.com_.
It does not trim the email string, and it does not return an "email and password does not match" error, rather redirects to the callback address with the said error.
This is reproducible in mobile and desktop too.
Are you guys aware of that bug? I couldn't find a proper place to report bugs to you guys.
(if you got here by searching the error message, please upvote so the good ppl #linkedin will see it :D )
Thanks!

Mails not sent in production side rails 4

I have a rails app with one form. After saving that form all data will be send in an email id. Form is working great in development side. But after deploying the app it doesn't work. It's giving the following error in the browser.
We're sorry, but something went wrong.
If you are the application owner check the logs for more information.
In this application I have another contact us form. That form work fine after deployment in production side.

How do I get the server logs for a Rails 4 application in development?

I am using Devise and it sends out a confirmation email when a new user account is created. Since I am in development, in localhost, it doesn't really send out the email, so I just copy the confirmation link from the server info that appears on the console.
The thing is, as one particular page grew, the amount of information that the server processes after the email is sent became too large for the terminal, the backscroll ends before I reach the link. I checked /log/development.log but it logs other things. I studied the config and debug parts of the rails doc but I couldn't find anything about server logging.
So now I have no way of copying the confirmation link from the console, and no way of confirming new accounts, which I still need to do since it is part of the proposed flow.
How can I get the server logs?

Why emails are not sending on production server?

I'm using the grails plugin "mail=0.9". Emails are not sending on production server. It just works fine on development environment on localhost.
Error is given below;
Stacktrace follows:
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at org.grails.mail.MailService.sendMail(MailService.groovy:63)
at org.grails.mail.MailService.sendMail(MailService.groovy:46)
at org.grails.mail.MailService$sendMail.call(Unknown Source)
at MailGrailsPlugin$_configureSendMail_closure4.doCall(MailGrailsPlugin.groovy:86)
at com.tkxel.chefvivant.api.SommelierController$_closure4.doCall(SommelierController.groovy:107)
at com.tkxel.chefvivant.api.SommelierController$_closure4.doCall(SommelierController.groovy)
at java.lang.Thread.run(Thread.java:636)
Can anyone help me? Why emails are not sending?
Thanks
Finally, after being spending the much time on this issue. I have fixed this error.
Actually the problem was just about to set the Gmail account settings. Google was sending the hidden captcha and that's obvious machine cannot recognize it. So that's why I was getting authentication error.
Solution:
I just unlocked the Gmail captcha and now it works fine.
Steps to reproduce this
1. Logout your gmail account first.
2. Visit this url https://accounts.google.com/DisplayUnlockCaptcha and then put username and password to login
3. Press "Continue" button to unlock the captcha
4. It will automatically save the settings.
Now, Check your application to hit the url like "Forgot Password" request. You will must receive email. :)
You can also read this article.
http://productforums.google.com/forum/#!topic/gmail/uBdBQAuGeTw
Thanks
javax.mail.AuthenticationFailedException means that you are useing incorrect credentials to access to account you use to send emails.

Net::SMTPUnknownError (could not get 3xx (550)) error when sending email on my Rails app

I'm using google for sending emails on my Rails 3.2 app. Most emails functions were working perfectly. Then I did some testing because delayed_job is not working. I got a warning from google that I need to log into the account via the web to unlock it (I sent about 20 emails in a span of 1 hour). Things were back to normal. Now, I am unable to send any emails whatsoever. I have this error message in my server log:
Net::SMTPUnknownError (could not get 3xx (550))
Has Google blacklisted me for sending 50 emails? I changed the password on the account, logged in a few times via the web, restored the settings to exactly what they were when the emails were working.
I got email working again by creating a new email address. Had to create a new one without using an alias for the old one to get it to work. I also created an SPF record entry, which I did not have before.

Resources