Hello, I have an issue I am stumbling on... I have...
# avo-2
m
Hello, I have an issue I am stumbling on... I have a project that works well locally, but has issues in production. I am deployed to Heroku, Stack 22. I am using Postgres 14. Rails 7, Ruby 3.1.0. In production, my tag fields in my resources do not save. They save in development, and they will save if I set them in the rails console in production, but not when I use the Avo interface. Additionally, my sidebar menu is ignoring my avo.rb initializer settings in production. I set the initializer to hide several resources, and it does so in development. But on my production machine it is showing all resources, including those not specified. I have been looking at my logs carefully, but I am not finding any clues as to why my initializer is being ignored or, more importantly, why my tag fields are not working. If anyone has any suggestions or insights I would grateful to hear them. Thank you!
l
Hey @miniature-eye-94502. The tags field and menu editor are Pro features. They are enabled in development so you can try them out, but disabled in production until you change the license type and add a valid license key.
You can get a trial key here 👆
And this is how you set up the license info
Regarding which feature is Pro and which is Community, in the docs, usually in the header section you’ll find the license requirements.
For some features like custom tools we have some notices in development mode.
m
Ah! That explains it. Thank you for the prompt help.
8 Views