Sam Pohlenz

I've been able to identify the line of code causing the difference in behavior: https://github.com/TrestleAdmin/trestle/blob/v0.9.9/frontend/js/components/form.js#L36-L37 Your data-remote link within the form triggers the `ajax:complete` events that were previously caught by...

The idea behind disabling that line when eager loading, is that the admin *reloading* should not be enabled. With eager loading enabled, the admin files are loaded via the Rails...

So that particular branch I actually am already running in production (currently preparing it to take over https://demo.trestle.io) and I haven't encountered any issues like this yet. However the spec...

There is now an open PR for rails that appears to fix this issue: * https://github.com/rails/rails/pull/53522

Closing as the fix has now been merged into the Rails [8-0-stable](https://github.com/rails/rails/tree/8-0-stable) branch.

I've been investigating some of these issues on the BirdWeather side of things and I have hopefully found the cause. A recent change last week meant that BirdNET probabilities weren't...

I'm not sure what could be happening, but it looks like your two network request screenshots are showing two different things -- the first on localhost shows the POST request...

Pausing the screencast at 0:15 I can see that there was a POST request, before it redirects to the show form action and does a GET request. Having said that,...

I'm glad you were able to find the solution, as I was running out of ideas. I am a little surprised that Trestle didn't show an error modal when the...

I've generally seen two main cases where this particular error happens `No route matches [GET] ...`: 1) When there is a syntax error in the `_admin.rb` file for the admin...