https://ti.to/rails-world/rails-world-2025/with/enaplf3hgye

I mean, they might have added a wrong link on the rails world homepage 😂

it showed me for 3 seconds, I clicked on it, it showed that it's locked

should we pay the extra 400 euros and get the other tier ?

yeah ... already 500 is expensive for no reason

there seems to be an issue if you want to activate multiple (basic) filters -> they don't seem to be preserved:
https://cdn.discordapp.com/attachments/740892037640880180/1372165525144207380/CleanShot_2025-05-14_at_12.54.06.mp4?ex=6825c83a&is=682476ba&hm=918a1e89d876caf735224e71bc33bdb12dd9d2c5ece85269a42e81395efe7513&

maybe related to this? but I have no access
https://cdn.discordapp.com/attachments/1372165525429551194/1372166241279541348/image.png?ex=6825c8e5&is=68247765&hm=a12216ca5bc51a164f50bd486bd7868fa70175391a8ebf2e17ddc8b4bf98a574&

Ah, it seems to behave differently if rendered in the association turbo frame or not.

It seems to be a bug when filters are applied on a association field

I‘ll post them when I‘m back at my computer. But it’s just two simple Boolean filters

I think the queries they trigger shouldn’t matter? One is querying a timestamp (simple if/else) and the other a JSONB field

the frame url is not updated on filter apply

here are the filters, just for the record:

```rb
class Avo::Filters::EventRegistrations < Avo::Filters::BooleanFilter
  self.name = "Event Anmeldungen"
  # self.visible = -> do
  #   true
  # end

  def apply(request, query, values)
    return query if values["registered"] && values["unregistered"]

    if values["registered"]
      query = query.where.not(registered_at: nil)
    elsif values["unregistered"]
      query = query.where(registered_at: nil)
    end

    query
  end

  def options
    {
      registered: "Angemeldet",
      unregistered: "Nicht Angemeldet"
    }
  end
end

class Avo::Filters::EventRoles < Avo::Filters::BooleanFilter
  self.name = "Event Rollen"
  # self.visible = -> do
  #   true
  # end

  def apply(request, query, values)
    return query if values.values.all? { _1 }

    conditions = values
                   .select { |_, value| value == true }
                   .keys
                   .map { |role| "event_roles ->> '#{role}' = 'true'" }
                   .join(" OR ")

    query.where(conditions)
  end

  def options
    roles
  end

  def roles
    Event.find(params[:id])&.roles || {}
  end
end
```

the second is a bit more involved, but interestingly it does seem to work correctly if I take the Turbo Frame URL and paste it in a different browser tab

i.e. .../admin/resources/events/214/event_participations?view=show&turbo_frame=has_many_field_show_event_participations&page=1&encoded_filters=...

well, also not completely... also wrong, but different 😅

https://github.com/avo-hq/avo/issues/3849

can I help with this somehow? it's rather... pressing 🥴

the filters code is all on the `avo` community

let me know if you hit any obstacle with the setup / reproduction

we would merge a PR and cut a release with this fix

can't give you an ETA yet... other fires to put out 🧯  ... launch week y'know 😉

but I'll sure allocate some time monday at the latest

There is no pressure at all on community contributions. Take your time and make sure to ping me whenever you hit any blocker

found the issue it's in 

```js
  uriParams() {
    return URI(window.location.toString()).query(true);
  }
```

we need to check if we're in a Turbo Frame

then use its `src`, not the `window.location`

okay, this works:

```js
  uriParams() {
    const turboFrame = this.urlRedirectTarget.dataset.turboFrame;
    return URI(
      !turboFrame
        ? window.location.toString()
        : this.element.closest(`turbo-frame#${turboFrame}`).src,
    ).query(true);
  }
```

now I just need to find a way to use your prettier settings 😄

okay I think I've got it... PR incoming...

That makes sense. Thanks for looking into in!

filters not being preserved

Hey, everyone!

We are facing a weird issue related to the "succeed" toast when running an avo action. 

The problem is that some browsers run perfectly, and in others don't.

We recorded some loom videos to help to understand.

Error (nothing happens): https://www.loom.com/share/26bd724da03e4b52aab48faaadcfff63
Run perfectly: https://www.loom.com/share/d13c37c81bce4792b89b520aa9ff5d07?sid=3a7d5673-ef16-4ef8-b9c7-d72ab7500f1e

Can someone help me with this issue?

Hi <@418550241651064853> !

That's weird, I'll check it out tomorrow.

So, the same action, same output, but the alert only shows up in some browsers, right?  Which browsers work, which don't, and what Avo version are you using?

Exactly.
We are using...

- gem "avo", "3.19.2"
- gem "avo-advanced", "3.19.2", source: "https://packager.dev/avo-hq"

And we tested in...

- Arc 1.9.4 (worked) 
- Chrome 136.0.7103.114 -- last version (not worked)
- Firefox 138.0.3 (worked)

In other words, the problem seems to be with the Chrome.

Got it. I've been trying to reproduce the issue, but I haven't had any luck so far.

I did notice that you wrapped the `has_many` association field in a panel. That's actually redundant, since association fields already come with their own built-in panels. It also looks a bit odd visually. Wrapping it in a panel adds an extra white background that creates unnecessary visual noise.

I'm guessing your code looks something like this:

```ruby
tabs title: "Title", description: "Description", id: :second_tabs_group do
  # ...
  tab "Api tokens" do
    panel do
      field :api_tokens, as: :has_many
    end
  end
  # ...
end
```

You can simplify it to this:

```ruby
tabs title: "Title", description: "Description", id: :second_tabs_group do
  # ...
  field :api_tokens, as: :has_many
  # ...
end
```

Try this approach with the latest version of Avo. If the error persists, please double-check whether it's happening exclusively on your machine. Let's stay in touch and get to the bottom of it.

Hey, <@138354902966599681> !
I applied the changes you recommended, but the issue persists. 😦

Could you please confirm whether this issue is limited to your local environment, or if other developers on the project have also experienced it?

Also, is happening on development or other environments as well?

Im not able to reproduce it

My IT team is running some tests, but the errors are only occurring on the computers of certain users in the company.

I recorded a video instructing some users to clear their cache and session to help determine if that might be causing the issue.

As soon as I have all the results, I’ll get back to you.

Hi <@138354902966599681> !

I’m happy to share some good news... the issue has been resolved!

After investigating, we found that the problem was related to the browser cache. Once the cache was cleared, everything started working as expected again.

Thank you very much for trying to help.

Best regards!

Great news <@418550241651064853>!

Cache-related bugs can be tricky to identify, glad you guys figured it out!

Hey, everyone!

`Sidebar fields` - those don't show on index page - is this intentional?

Hi <@451078590507909120> yes it intentional

Sidebar only renders on show view, so the fields declared inside a sidebar ar not parsed on index

on the thread that you mentioned I posted a code snippet to mannually declare fields on both index / sidebar without duplication

```ruby
def fields_bag(**extra_args)
  field :name ..., **extra_args
  field :skill ..., **extra_args
end

def fields
  fields_bag(only_on: :index)

  sidebar do
    fields_bag
  end
end
```

Yes, I used that , and it worked, thank you!!

(the AI bot here helped to find it)

Awesome! we should have this as a guide and a link to it on the sidebar documentation

`Sidebar fields` - those don't show on

Found a previous thread on the topic - https://discord.com/channels/740892036978442260/1141725701549072486/1232246369285181481

What's the recommended way to flash error/success notices in an Avo::ToolsController method?

Hi <@266623597907279874> here is a snippet with all the possible flash types, this would make a cool quick guide, I'll add this to our guide ideas discussion

```ruby
class Avo::ToolsController < Avo::ApplicationController
  def custom_tool
    @page_title = "Custom tool"

    # Error
    flash[:error] = "This is an error"
    flash[:alert] = "This is an alert"

    # Success
    flash[:success] = "This is a success"

    # Info
    flash[:info] = "This is an info"
    flash[:notice] = "This is a notice"

    # Warning
    flash[:warning] = "This is a warning"

    # Something else
    flash[:something_else] = "This is a primary"
  end
end
```

Added it to the guides list 😉

https://github.com/avo-hq/docs.avohq.io/discussions/373

What's the recommended way to flash

The time has come to add an admin backend to https://github.com/yshmarov/moneygun. Any suggestions?

[This one](https://github.com/yshmarov/moneygun/pull/157) looks nice. Will go with it

The time has come to add an admin

Question about some of the stuff you're exploring for Avo 4:

1. Is the DB-backed config stuff going to be optional?
2. What does the workflow look like for taking DB-backed configuration and move it between environments / reconcile differences?
3. For all the in-UI development features, are those built on the DB-backed config, or is it creating/modifying Ruby code?

Great questions!

1. yes. completely optional. the code that back them up and migrations are opt-in
2. we asked ourselves that too. There are a few things we can do. One is to offer a system (through avohq.io or not) where you register your production and development (and other) evnironments and you can import/export them from one place to another
3. it depends which ones. if you're talking about the index view editing, those could be applied to any type of resource (db or file backed)

what were your first thoughts when you watched the video?

Haven't had a chance to watch it just yet.  Been hip-deep in a project that boils down to "incrementally migrate a full-page-app from AngularJS 1.6 to React 18 while adding new functionality as we go", and so today has been... involved.

Chapter stops on release videos would be helpful...

Inline action definitions look very handy and ergonomic.  

The let-power-users-do-light-dev-things is not a capability I'll be making use of (should I wind up in a position to use Avo again), though.  Maybe saving particular filter configurations as a scope, but beyond that... not so much.  Too much opportunity for an ill-performing query to hork system equilibrium.

I worry that you're headed down the path of recreating a crude MS Access-esque system.  A product like that might be a perfectly reasonable thing to build, but it seems to me to be a different product than what Avo has been attempting to be thus far.

You might consider making it a _separate product_ and just sharing code between the projects to get leverage...  I'd imagine that orgs that want that functionality might be willing to pay more for it -- and that could help ensure you have the resources necessary to keep it from becoming a drag on development of the core system.

> but it seems to me to be a different product than what Avo has been attempting to be thus far
I get that, but we did get some requests for those capabilities

and that's also being created for some specific use-cases. I don't expect everyone to build Avo apps like that from now on

Question about some of the stuff you're

Hi! I'm actually here because a client project I am working on has the license showing up as a Community license even though the client has paid for a Pro licence. `avo_private/status` shows the correct license key, but I see " Valid Community license"

That can be done by adding it to the gemfile and run bundle

https://docs.avohq.io/3.0/gem-server-authentication.html

```ruby
# Avo Pro
gem "avo", ">= 3.2.1"
gem "avo-pro", ">= 3.2.0", source: "https://packager.dev/avo-hq/"
```

ah, I didn't realize it was a separate pacakge

All right, its a package that is on our private packager

You need to configure the gem server token

yep I think I got it. I think it would be nice if you showed a warning if you detect a pro license key but the pro package is not installed, and added this to the "License troubleshooting" section of the docs (which is what I checked)

Actually that is a good idea, thanks for the suggestion