ryanzidago
I have the following form:
<%= form_for @conn, Routes.auth_path(@conn, :request, "passwordless"), [method: :get], fn f -> %>
<%= hidden_input f, :redirect_url, value: Routes.page_path(@conn, :login_mail_sent) %>
<%= email_input f, :email, placeholder: "Your email address", required: :true %>
<%= submit "Log in" %>
<% end %>
Now if I try to submit the form with the email field input empty, I’ll get a small error bubble from Phoenix with something saying: “Please, fill out this field.”
Could anyone please tell me how can I translate this error message?
I know I can use gettext but I do not understand where should I call the gettext function since the string “Please fill out this field” is not written anywhere in the code.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sfusato
That bubble message you get is not from Phoenix, but from your browser (if you remove
required: :true, you will get Phoenix’s message which iscan't be blank)For the Phoenix error messages, check
priv/gettext/errors.potryanzidago
@sfusato thanks for the info!
I decided to change the default browser message thanks to this stackoverflow post.
sfusato
oninvalidonly seems to have ~38% global coverage according to caniuse.comdimitarvp
You’re better off simply providing a translated
titleattribute for the element. Much simpler and works well.ryanzidago
What do you mean exactly?
If I write:
<%= email_input f, :email, placeholder: "Your email address", required: :true, title: "Veuillez fournir votre adresse Mail" %>It still displays the English warning “Please fill out this form”.
dimitarvp
It shouldn’t say that at all, I guess you have a validation form error raised earlier than before the browser can yell at you for an invalid email field.
ryanzidago
When I remove the
required: :trueoption, I don’t get thecan't be blankmessage that @sfusato mentionend; hence why I decided to write some small javascript.That might be the reason why also the title property does not work?
Also this form is not used to create a user, it is mostly for login so it has nothing to do with Ecto (who, as far as I know, usually displays those
error this field can't be blanktype of message).dimitarvp
Very likely. For
titleto work you need not to intercept and process JS events for the element in question.If that’s not okay then I am afraid you’ll have to go all the way with JS.
sfusato
Do you have
:emailin thevalidate_required([:email])changeset function?You can still use Changesets even without a schema: check Schemaless Changesets
ryanzidago
No actually I do not use a changeset at all, just the @conn.
I’ll look into how to implement a schema less changeset.
Thanks for the tip one again.