Hi, we just bought a pro license and trying out Avo on a new project in our company. We like the product so far. However when we pushed the app up to heroku it behaves differently on our development machine. Specifically about the main menu. We tested it by setting like this on the config.

config.main_menu = -> {
    section 'Settings', icon: 'tools' do
      group 'Pricing' do
        resources :shop
      end
    end
  }

and it works as intended on our dev machine. However when we pushed to heroku this menu is not to be seen and we only see the default one. The image is attached. Is this a known issue? https://cdn.discordapp.com/attachments/1039573545828753438/1242417548390043668/Screenshot_2567-05-21_at_16.58.08.png?ex=664dc302&is=664c7182&hm=31c01b566450453ec5ae275a8d49ec276c1981855f769b15828d45d03a12e610&

There is a small typo "hwo", "how" in the first paragraph on https://docs.avohq.io/3.0/internals.html

Hi, think I've found a bug, the link to our dashboards from the sidebar does not include the /avo part, giving us a "The page you requested does not exist" error, until we manually change the url to include it

Hi, we have noticed a bug which occurs with the pagy gem. We already had it installed, so it is using our latest version instead of the version listed in the Avo dependencies of our gemfile. The problem is that Pagy recently had an update that changed the name of the "items" variable to "limit", as per link below. When Avo uses the later version of pagy in our app, this gives an undefined method error in app/components/avo/paginator_component.rb:31:in `render?' Are there plans to upgrade pagy on Avo soon? We have had to downgrade to keep things working in the meantime https://ddnexus.github.io/pagy/changelog/

Just a small one, for associated/related records tables where there are no records found, I find the default "No related record found" image unnecessarily large. I would prefer for it to take up much less space on the page eg see attached images https://cdn.discordapp.com/attachments/1039573545828753438/1272872944154181682/image.png?ex=66bc8ece&is=66bb3d4e&hm=66d31f1d40e02629c2c9be08b226391b9e0771eca8befecc49525827bebb2950& https://cdn.discordapp.com/attachments/1039573545828753438/1272872944632074291/image.png?ex=66bc8ece&is=66bb3d4e&hm=d6d4e5038a3a839ddb5706776171f9fe19d985d019a791a314ef5aaa727edd28&

> click_row_to_view_record This feature is exactly what I truly wanted. Thank you for developing it. I will try it right away. https://docs.avohq.io/3.0/customization.html#click_row_to_view_record

click_row_to_view_record is very convenient, but it seems we need to be a bit cautious due to the following issue: There are cases where it becomes unresponsive when using the browser's back button. https://github.com/avo-hq/avo/issues/2607

Thank you so much for creating Avo v3.11.8 and v3.11.9! I have already applied it to my production environment. With this version, paging has become much smoother and more comfortable. Thank you for your prompt response❤️😍

Just saw the date time basic filters, and I'm loving it! Thank's a whole lot @loud-jewelry-99127 for working on that ❤️

I investigated an increase in errors related to click_row_to_view_record. I found that when using click_row_to_view_record, the links to the Show page remain active even when access to the Show page is restricted by Pundit, leading to errors each time the link is clicked. Created feedback issue for click_row_to_view_record https://github.com/avo-hq/avo/issues/3200

While using the Avo demo, I noticed that Global Search results couldn't be opened in a new tab, so I created a feature request issue. It would be even more convenient if Global Search results could be opened in a new tab❤️ https://github.com/avo-hq/avo/issues/3203

For whoever is reading this, I personally love Avo and would recommended in a glance. I'm a freelance software engineer, and I've been using Avo as admin panel with a couple of clients ( 3 of them have the Advanced license ). I recently signed a new project that wasn't "admin panel oriented" and wanted to give Avo a try to see if it works. I was able to finish the project in less than 5 days, and all that for a license worth 1,000$. In other words, the time that I would have spent to build everything from scratch would have cost me more than the license's price.

It's a very minor issue, but clearly displaying the Rails version can be a security risk, so I would appreciate it if it could be shown in a more obscure format❤️ > view-source:https://avodemo.com/avo/dashboards/dashy

Curious question: Is anyone using ChartKick integration with Avo? We have been trying to debug this for days; it's funny: I added the color configuration for Avo and Chartkick using the configuration in avo.rb. In development, the chart uses the colors to identify certain statuses; in another production environment, other colors; and in production, another set of colors. They are the same colors I setu up, but for some reason, depending on the environment, the total of records, whichshould be green (done), is blue (in progress). I did the setup using avo.rb, and customized chart_kick_options inside an Avo Card, but both have the same behavior.

Quick request/feedback. It would be great if everything in the Documentation menu is alphabetically ordered (as the field-types section). 😅 https://cdn.discordapp.com/attachments/1039573545828753438/1288130514552623104/image.png?ex=66f41086&is=66f2bf06&hm=cd5d65b69ec1127e1e6ea8118b054c572d7100fcd827888635e979b609167552&

I have created an issue as there may be a problem when using tabs with the browser back button. I would appreciate it if you could check it when you have some time. https://github.com/avo-hq/avo/issues/3262

@loud-jewelry-99127 Sorry to bother you while you're busy. The Dynamic Filter is very useful!❤️ I was considering implementing it right away, but I encountered an issue where the Dynamic Filter can't be closed. I would appreciate it if you could take a look when you have time. https://github.com/avo-hq/avo/issues/3282

I immediately applied Avo v3.14.1 to the production environment. It seems to be working fine. Thank you for always improving Avo❤️

I quickly deployed Avo v3.15.1 to the production environment. I always look forward to the monthly Avo updates!

Hello! Just flagging a little bug on a feature I love. The 'disabling actions when no records selected' behavior doesn't work properly. It enables the actions even when the selected records belongs to a different resource: (3 sec video below) The same happens with the actions stored in dropdowns. https://cdn.discordapp.com/attachments/1039573545828753438/1342237925009788978/Screen_Recording_2025-02-20_at_17.53.19.mov?ex=67b8e7fa&is=67b7967a&hm=68f8ff52e56fcd0fa06fb6875e4536758cb7c6277e5b9506a3dd8498b33df2d4&

Hi Again! This is Jeremias from TwentyeightHealth. I'm passing a message from Henrique, who can't access Discord right now: > We turned the Avo Audit Logging fully ON in the production env but apparently some tasks like rails asset:precompile fail because Avo is now checking database connections before they are loaded > We worked on a fix, but we thought it was good to let you know. Also when you do config.enabled = false the resources that have Audit Logging raises the error undefined method avo_activities' for an instance of User

I had some discreet information configured in my app here: self.discreet_information = [ { tooltip: -> { sanitize("View #{record.full_name} on site", tags: %w[strong]) }, icon: -> { "heroicons/outline/arrow-top-right-on-square" }, url: -> { main_app.venue_attraction_path(record.venue, record) }, url_target: :_blank } ] But it errors on the New view. is there anything built in to configure when each item type should be allowed to show to avoid this?

ActionController::UrlGenerationError in Avo::Attractions#new
Showing /home/vscode/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/avo-3.18.1/app/views/avo/base/_new_via_belongs_to.html.erb where line #4 raised:

Hey all, Just a future feature suggestion for Avo: Warnings. A warnings feature made up of a Warnings page where records could be subjected to specific conditions. Eg, Company records that have not been assigned a Main Photograph. Project records that have not got a specific field filled out. These would be highlighted on the Warnings page. Maybe the record itself when visible in Avo in List or Grid view could have a form of badge to indicate that it has a warning against it. This feature would be fantastic to easily highlight to the user where your app has missing information etc.

Hey everyone, I need some help with an issue on my Rails app deployed on Render. Whenever I try to access the Avo dashboard, I get the following error in the Render logs: [Avo->] Failed to clear Avo HQ response: PG::UndefinedTable: ERROR: relation "solid_cache_entries" does not exist LINE 10: WHERE a.attrelid = '"solid_cache_entries"'::regclass. It seems like the table is missing, but I'm not sure how to resolve this. Has anyone encountered this before or has any insights on how to fix it? Any help would be greatly appreciated. Thanks in advance!

@loud-jewelry-99127 Hey Paul. Amazing work with the nested records feature! Really liking it. Going to compile some comments about it into a small thread. First off, i'm noticing that my custom stimulus controller is not activating on the nested resources. Is this a known issue?

The tags dynamic filter is very convenient. I can separate words using a comma, but I would like it to work the same way when words are separated by spaces. Even in Google search, when searching for multiple words, everyone types the words separated by spaces rather than commas. https://docs.avohq.io/3.0/dynamic-filters.html#Tags

Thread automatically created by yuki in #1039573545828753438

Since the dynamic filter is very convenient and is often used, it would be nice if there was a function to save the search conditions and their combinations as favorite filter conditions.

When there is a large amount of data, it would be greatly appreciated if the table headers remained visible even when scrolling vertically. Currently, it can sometimes be difficult to remember which column represents which data field. For instance, in the attached gif example, it would be extremely helpful if the following headers – id, avatar, first name, last name, user email, is active, cv, is admin, roles, birthday, is writer – remained visible at all times rather than being hidden when scrolling. https://cdn.discordapp.com/attachments/1039573545828753438/1361688145216929872/screenshot_2025-04-15_22.01.06.png?ex=67ffaa68&is=67fe58e8&hm=8668cc956390414e2bc42a3861ffd5c18ab98ac7b95f138d085bdd97dce1e38d&

Folks, a question: When I purchased two licences for Avo last year, theming was part of the roadmap for v3. If theme becomes available on v4 next week (for example), I will have to buy a new license? I know promises were not set in stone regarding specific features, but at the same time, the roadmap was clear, but features like theming kept being pushed to new releases and never came up. Can you clarify how things will be for v4 and if we can expect more clarity on the roadmap? Thank you 🙂