mendrik

mendrik

I’m trying to implement multiple file upload buttons inside the same live_view. I have this kind of code:

defmodule AlbumWeb.AlbumLive do
  use AlbumWeb, :live_view
  alias Album.HashedIds
  alias Integer
  require Logger

  def mount(%{"id" => id}, _session, socket) do
    album_id = HashedIds.decode!(id)
    album = Album.get_album!(album_id)
    pages_per_album = Application.get_env(:album, :pages_per_album, 10)
    {:ok, assign(socket, album: album, pages_per_album: pages_per_album)}
  end

  def render(assigns) do
    ~H"""
    <div class="flex-1 book_holder">
      <div class="book" style="--c: 0;--translate: 0;">
        <%= for page <- 0..(@pages_per_album - 1) do %>
          <PageComponents.photo_page page={page}>
            <:front>
              <.live_component
                module={AlbumWeb.PhotosetLive}
                id={page * 2}
                page={page * 2}
                album={@album}
              />
            </:front>
            <:back>
              <.live_component
                module={AlbumWeb.PhotosetLive}
                id={page * 2 + 1}
                page={page * 2 + 1}
                album={@album}
              />
            </:back>
          </PageComponents.photo_page>
        <% end %>
      </div>
    </div>
    """
  end
end

which uses AlbumWeb.PhotosetLive a few times. PhotosetLive is defined like so

defmodule AlbumWeb.PhotosetLive do
  use AlbumWeb, :live_component

  # use def update_many(assigns_sockets) to load all photos in the albnum

  def mount(socket) do
    socket =
      socket
      |> assign(:uploaded_files, [])
      |> allow_upload(:photoset, accept: ~w(.jpg .jpeg .png .webp), max_entries: 7)

    {:ok, socket}
  end

  def handle_event("validate", _params, socket) do
    {:noreply, socket}
  end

  def handle_event("save", _params, socket) do
    uploaded_files =
      consume_uploaded_entries(socket, :photoset, fn %{path: path}, _entry ->
        dest = Path.join("priv/static/uploads", Path.basename(path))
        IO.puts(path <> " -> " <> dest)
      end)

    {:noreply, update(socket, :uploaded_files, &(&1 ++ uploaded_files))}
  end

  attr :page, :integer, required: true
  attr :album, Album.Album, required: true

  def render(assigns) do
    ~H"""
    <div>
      <div>photos</div>
      <div>
        <%= for entry <- @uploads.photoset.entries do %>
          <%= entry.client_name %> - <%= entry.progress %>%
        <% end %>
        <form phx-submit="save" phx-change="validate">
          <%= live_file_input(@uploads.photoset) %>
          <button type="submit">Upload</button>
        </form>
      </div>
    </div>
    """
  end
end

this crashes by page with

ArgumentError at GET /albums/1Ovxpva
assign/3 expects a socket from Phoenix.LiveView/Phoenix.LiveComponent  or an assigns map from Phoenix.Component as first argument, got: %{accept: ".jpg,.jpeg,.png,.webp", __given__: %{accept: ".jpg,.jpeg,.png,.webp"}}You passed an assigns map that does not have the relevant change tracking information. This typically means you are calling a function component by hand instead of using the HEEx template syntax. If you are using HEEx, make sure you are calling a component using:

    <.component attribute={value} />

If you are outside of HEEx and you want to test a component, use Phoenix.LiveViewTest.render_component/2:

    Phoenix.LiveViewTest.render_component(&component/1, attribute: "value")

Would anyone have a pointer what I am doing wrong? I also tried only one component but it gives the same error. It’s pretty text book implementation so far, and I’m very new to phoenix and elixir.

First 2 of 2 Posts Switch mode

mendrik

mendrik OP

Upon further debugging, it’s this line that causes the error:
<%= live_file_input(@uploads.photoset) %>

I have inspected the socket and @uploads.photoset is set, I have also tried <%= live_file_input(@uploads) %>, but it doesn’t work either :thinking:

mendrik

mendrik OP

problem was with using <%= live_file_input(@uploads.photoset) %> instead of <.live_file_input upload={@uploads.photoset}/>

— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New

We're in Beta

About us Mission Statement