ostap
Hi. I ran this command:
mix phx.gen.live Forms Form forms domain:string bg_color:string primary_color:string title:string description:text
Then ran the migrations and added routes to the web scope.
However, when I try to visit the /forms/new route, I’m getting this error:
protocol Phoenix.HTML.FormData not implemented for %MyProject.Forms.Form{__meta__: #Ecto.Schema.Metadata<:built, "forms">, id: nil, domain: nil, description: nil, title: nil, bg_color: nil, primary_color: nil, inserted_at: nil, updated_at: nil} of type SuperSubstack.Forms.Form (a struct). This protocol is implemented for the following type(s): Ecto.Changeset, Map
I haven’t made any changes besides the generated code, so surprised to see this error. Any idea why it’s there and the ways to fix it? Maybe there is a name collision of some sort? (“form”)
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
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.
**Building the future of software with AI, trust, and human connection.**
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 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ostap
It indeed was a name collision. Using a different name for that schema solves the issue.
i.e.
SubscriptionForminstead ofForm.Reported at Using "Form" as a schema name in `phx.gen.live` causes components to misbehave · Issue #5871 · phoenixframework/phoenix · GitHub