Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A administrate
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thoughtbot, inc.
  • administrate
  • Issues
  • #2221
Closed
Open
Issue created Jun 28, 2022 by Richard Watkins@smedrick

Weird caching behavior when editing entries?

I’m running Rails 6.1.4.4 with administrate 0.16.0 and a MySQL DB, and I don’t see it on every dashboard, but on a couple of my most active models I noticed that some fields will simply not display updates (I can see through the console that the database has been updated, but the dashboard doesn’t show the change). This is on basic string and Boolean attributes, nothing fancy with special relationships.

One in particular baffles me. Certain Posts, when the Description is updated, will change the field to blank on admin display, but the front end of the site shows the changes just fine. I’m fairly new to Rails 6 and I’m not sure if there’s some weird caching mechanism that was turned on by default.

Assignee
Assign to
Time tracking